Results for 13.0.0 20221102 (experimental) [master r13-3604-gb65e391da94] (Debian 20221102-1) testsuite on powerpc64le-unknown-linux-gnu

LAST_UPDATED: Wed Nov 2 09:53:24 UTC 2022 (revision r13-3604-gb65e391da94) === acats tests === === acats Summary === # of expected passes2328 # of unexpected failures0 Native configuration is powerpc64le-unknown-linux-gnu === g

Results for 13.0.0 20221102 (experimental) [master r13-3604-gb65e391da94] (Debian 20221102-1) testsuite on i686-pc-linux-gnu

LAST_UPDATED: Wed Nov 2 09:53:24 UTC 2022 (revision r13-3604-gb65e391da94) === acats tests === === acats Summary === # of expected passes2328 # of unexpected failures0 Native configuration is i686-pc-linux-gnu === g++ tests ===

Results for 9.5.0 (Debian 9.5.0-2+b2) testsuite on arm-unknown-linux-gnueabihf

LAST_UPDATED: Obtained from git: releases/gcc-9.5.0 revision 7a15b5060a83ea8282323d92043c6152e6a3e22d Native configuration is arm-unknown-linux-gnueabihf === libatomic tests === Running target unix === libatomic Summary for unix === # of expected passes

Re: rebootstrap status update for Loongarch

On Thu, Nov 03, 2022 at 12:31:10PM +0100, Johannes Schauer Marin Rodrigues wrote: > Quoting Zhang Ning (2022-11-03 11:45:17) > > 6, gcc, binutils: need help, I don't know how to submit a patch to Debian > > toolchain-team, don't accept a poll request. > > > > 7, m4, diffutils: need help, I don't

rebootstrap status update for Loongarch

Hi, Helmut as you mentioned, missing upstream status, I want to update below, and my fork[0] is updated. another purpose of this email is asking for help. status update: 1, Linux: I will send patch to debian-kernel once dpkg name is settled. 2, glibc: https://salsa.debian.org/glibc-team/glibc/

Processed: Fwd:

Processing control commands: > found 1016903 12.2.0-7 Bug #1016903 [g++-12] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) Marked as found in versions gcc-12/12.2.0-7. -- 1016903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016903 Debian Bug Tracking System Conta

Bug#1016903: Fwd:

Control: found 1016903 12.2.0-7 For example ppc64: * https://buildd.debian.org/status/fetch.php?pkg=highway&arch=ppc64&ver=1.0.3%7Egit20221102.4899d11-1&stamp=1667470496&raw=0

gcc-12_12.2.0-9_source.changes ACCEPTED into unstable

1023324 Changes: gcc-12 (12.2.0-9) unstable; urgency=medium . * Update to git 20221103 from the gcc-12 branch. - Fix PR c++/107358, PR c++/105774, PR tree-optimization/107121, PR c/107001, PR c/106981, PR c++/106829. * Fix PR ada/107475, proposed patch. * gm2-12-doc: Add missing

Processing of gcc-12_12.2.0-9_source.changes

gcc-12_12.2.0-9_source.changes uploaded successfully to localhost along with the files: gcc-12_12.2.0-9.dsc gcc-12_12.2.0-9.debian.tar.xz gcc-12_12.2.0-9_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1023324: marked as done (gm2-12-doc: missing Breaks+Replaces: gm2-12 (<< 12.2.0-8))

P SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 03 Nov 2022 09:40:42 +0100 Source: gcc-12 Architecture: source Version: 12.2.0-9 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 1009286 1022935 1023324 Changes: gcc-12 (12

Bug#1022935: marked as done (gcc-12: libstd++6.symbols.armel is missing GLIBCXX_3.4.30)

Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 1009286 1022935 1023324 Changes: gcc-12 (12.2.0-9) unstable; urgency=medium . * Update to git 20221103 from the gcc-12 branch. - Fix PR c++/107358, PR c++/105774, PR tree-optimization/107121, PR c

Bug#1009286: marked as done (gcc-12: DEB_STAGE=rtlibs should include libatomic)

Changed-By: Matthias Klose Closes: 1009286 1022935 1023324 Changes: gcc-12 (12.2.0-9) unstable; urgency=medium . * Update to git 20221103 from the gcc-12 branch. - Fix PR c++/107358, PR c++/105774, PR tree-optimization/107121, PR c/107001, PR c/106981, PR c++/106829. * Fix PR ada

Processed: your mail

Processing commands for cont...@bugs.debian.org: > notfixed 1016903 12.2.0-2 Bug #1016903 [g++-12] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) Ignoring request to alter fixed versions of bug #1016903 to the same values previously set > found 1016903 12.2.0-3 Bug #1016

Processed: Re: Bug#1016903 closed by Matthias Klose (Fixed in 12.2.0-2 and later.)

Processing control commands: > reopen -1 Bug #1016903 {Done: Matthias Klose } [g++-12] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add th

Bug#1016903: closed by Matthias Klose (Fixed in 12.2.0-2 and later.)

Control: reopen -1 > -- Forwarded message -- > From: Matthias Klose > To: 1016903-d...@bugs.debian.org, 1016...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 3 Nov 2022 09:28:54 +0100 > Subject: Fixed in 12.2.0-2 and later. > Version: 12.2.0-2 > > Fixed in 12.2.0-2 and later. Nope. A

Bug#1016903: marked as done (tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working))

Your message dated Thu, 3 Nov 2022 09:28:54 +0100 with message-id and subject line Fixed in 12.2.0-2 and later. has caused the Debian Bug report #1016903, regarding tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) to be marked as done. This means that you claim that the pr

Bug#1016903: Fixed in 12.2.0-2 and later.

Version: 12.2.0-2 Fixed in 12.2.0-2 and later.