[Linaro-TCWG-CI] gcc-15-7878-ge1c49f413c8: 3 regressions on aarch64
Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In gcc_check master-aarch64, after: | commit gcc-15-7878-ge1c49f413c8 | Author: Richard Biener | Date: Mon Feb 10 10:23:45 2025 +0100 | | middle-end/118801 - excessive redundant DEBUG BEGIN_STMT | | The following addresses the fact that we keep an excessive amount of | redundant DEBUG BEGIN_STMTs - in the testcase it sums up to 99.999% | of all stmts, sucking up compile-time in IL walks. The patch amends | ... 8 lines of the commit log omitted. Produces 3 regressions: | | regressions.sum: | Running gcc:gcc.dg/guality/guality.exp ... | XPASS: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 c + 1 == 2 | XPASS: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 i + 1 == 8 | XPASS: gcc.dg/guality/pr90716.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 23 j + 1 == 9 Used configuration : *CI config* tcwg_gcc_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1531. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolch...@lists.linaro.org mailing list. -8<--8<--8<-- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3410/artifact/artifacts/00-sumfiles/ The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3410/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3410/artifact/artifacts/sumfiles/xfails.xfail Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3410/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3409/artifact/artifacts Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/e1c49f413c8c892a61612b3b89de0607ff7ba893/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e1c49f413c8c892a61612b3b89de0607ff7ba893
Regressions on master at commit r15-7894 vs commit r15-7891 on Linux/x86_64
Regressions on master at commit r15-7894 vs commit r15-7891 on Linux/x86_64 New failures: FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) New passes:
[r15-7894 Regression] FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) on Linux/x86_64
On Linux/x86_64,
cf65235e03d2eb1667624943eae8f7fc355bceaf is the first bad commit
commit cf65235e03d2eb1667624943eae8f7fc355bceaf
Author: Andrew Pinski
Date: Thu Mar 6 16:07:02 2025 -0800
c: Fix warning after an error on a return statment [PR60440]
caused
FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40)
FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40)
with GCC configured with
../../gcc/configure
--prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-7894/usr
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
--with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl
--enable-libmpx x86_64-linux --disable-bootstrap
To reproduce:
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m32\
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m64\
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m32\
-march=cascadelake}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check
RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m64\
-march=cascadelake}'"
(Please do not reply to this email, for question about this report, contact me
at haochen dot jiang at intel.com.)
(If you met problems with cascadelake related, disabling AVX512F in command
line might save that.)
(However, please make sure that there is no potential problems with AVX512.)
Re: [r15-7894 Regression] FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) on Linux/x86_64
On Fri, Mar 7, 2025 at 2:39 PM haochen.jiang wrote:
>
> On Linux/x86_64,
>
> cf65235e03d2eb1667624943eae8f7fc355bceaf is the first bad commit
> commit cf65235e03d2eb1667624943eae8f7fc355bceaf
> Author: Andrew Pinski
> Date: Thu Mar 6 16:07:02 2025 -0800
>
> c: Fix warning after an error on a return statment [PR60440]
>
> caused
>
> FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40)
> FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40)
This is already fixed with
r15-7898-gd71139982a364c5c9646737a7b9a407967ecd88c . Sorry for
forgetting to update these testcases too.
Thanks,
Andrew
>
> with GCC configured with
>
> ../../gcc/configure
> --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r15-7894/usr
> --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
> --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl
> --enable-libmpx x86_64-linux --disable-bootstrap
>
> To reproduce:
>
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m32\
> -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-2a.c --target_board='unix{-m64\
> -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m32\
> -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gcc.dg/Wreturn-mismatch-6.c --target_board='unix{-m64\
> -march=cascadelake}'"
>
> (Please do not reply to this email, for question about this report, contact
> me at haochen dot jiang at intel.com.)
> (If you met problems with cascadelake related, disabling AVX512F in command
> line might save that.)
> (However, please make sure that there is no potential problems with AVX512.)
Regressions on master at commit r15-7878 vs commit r15-7876 on Linux/x86_64
Regressions on master at commit r15-7878 vs commit r15-7876 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 c + 1 == 2 FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 c + 1 == 2 FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 i + 1 == 8 FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 i + 1 == 8 FAIL: gcc.dg/guality/pr90716.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 23 j + 1 == 9 FAIL: gcc.dg/guality/pr90716.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 23 j + 1 == 9
Re: [Linaro-TCWG-CI] gcc-15-7853-gde231924b73: 1 regressions on aarch64
On Thu, 6 Mar 2025 at 23:55, Giuseppe D'Angelo via Gcc-regression wrote: > > On 06/03/2025 20:29, ci_not...@linaro.org wrote: > > Dear contributor, > > > > Our automatic CI has detected problems related to your patch(es). Please > > find some details below. > > This has been fixed on trunk by r15-7863-gd2b022e38a778d. > Indeed I can see the test now passes. Thanks, Christophe > Thank you, > -- > Giuseppe D'Angelo
Re: [Linaro-TCWG-CI] gcc-15-7765-g3866ca796d5: 8 regressions on master-thumb_m7_hard_eabi
On Wed, 5 Mar 2025 at 23:32, Jonathan Wakely wrote:
>
> On Mon, 3 Mar 2025 at 09:27, Jonathan Wakely wrote:
> >
> > On Mon, 3 Mar 2025 at 09:10, Christophe Lyon
> > wrote:
> > >
> > > Hi Jonathan,
> > >
> > > On Sun, 2 Mar 2025 at 23:28, Jonathan Wakely via Gcc-regression
> > > wrote:
> > > >
> > > > On Sun, 2 Mar 2025 at 02:42, wrote:
> > > > >
> > > > > Dear contributor,
> > > > >
> > > > > Our automatic CI has detected problems related to your patch(es).
> > > > > Please find some details below.
> > > > >
> > > > > In arm-eabi cortex-m7 hard, after:
> > > > > | commit gcc-15-7765-g3866ca796d5
> > > > > | Author: Jonathan Wakely
> > > > > | Date: Thu Feb 27 13:27:17 2025 +
> > > > > |
> > > > > | libstdc++: Fix ranges::move and ranges::move_backward to use
> > > > > iter_move [PR105609]
> > > > > |
> > > > > | The ranges::move and ranges::move_backward algorithms are
> > > > > supposed to
> > > > > | use ranges::iter_move(iter) instead of std::move(*iter),
> > > > > which matters
> > > > > | for an iterator type with an iter_move overload findable by
> > > > > ADL.
> > > > > | ... 16 lines of the commit log omitted.
> > > > >
> > > > > Produces 8 regressions:
> > > > > |
> > > > > | regressions.sum:
> > > > > | Running libstdc++:libstdc++-dg/conformance.exp ...
> > > > > | FAIL: 25_algorithms/move/constrained.cc -std=gnu++20 (test for
> > > > > excess errors)
> > > > > | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++20
> > > > > compilation failed to produce executable
> > > > > | FAIL: 25_algorithms/move/constrained.cc -std=gnu++26 (test for
> > > > > excess errors)
> > > > > | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++26
> > > > > compilation failed to produce executable
> > > > > | ... and 4 more
> > > >
> > > > It looks like thumb has some unusual linking requirements that I'm not
> > > > familiar with, so undefined functions (which are never actually called
> > > > in the test) cause linker errors:
> > > >
> > > > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
> > > > undefined reference to `pr105609::iter_move(pr105609::I const&)'
> > > > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
> > > > (_ZN8pr1056099iter_moveERKNS_1IE): Unknown destination type
> > > > (ARM/Thumb) in /tmp/ccqKQGzN.o
> > >
> > > This is a "recent" linker warning, which I added sometime during last
> > > year (so you need recent binutils if you want to try to reproduce the
> > > problem).
> > > It means that for some reason the destination symbol lacks a tag (asm
> > > directive) saying whether it's a thumb or an arm function. This is
> > > used by the linker when deciding which type of stub to insert (if
> > > any).
> > > For instance: ".type myfunc, %function"
> > > but normally the compiler adds this for you.
> > >
> > > But you mention "undefined functions", so that would probably be the
> > > reason, but how can the link succeed? Are you linking with "-z undefs"
> > > ?
> >
> > See e.g. libstdc++-v3/testsuite/25_algorithms/move/constrained.cc
> > The test06 function uses undefined member functions such as
> > I::operator== but because test06 is never called, it shouldn't matter.
> >
> > I can move test06 to a separate { dg-do compile } test, where the
> > linker isn't involved at all.
>
> I hope this is fixed at
>
> r15-7842-gc21d5a3591fd761872e18278e1cd8ec18e36d4cb
>
Indeed, the tests now pass.
I still haven't understood why the original version passed on some
targets? (I assume so, I suppose you tested the patch before
committing ;-) )
Even if not called, test06 would still have references I::operator==
whatever the target?
Thanks,
Christophe
Regressions on master at commit r15-7886 vs commit r15-7883 on Linux/x86_64
Regressions on master at commit r15-7886 vs commit r15-7883 on Linux/x86_64 New failures: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps New passes:
Re: [Linaro-TCWG-CI] gcc-15-7765-g3866ca796d5: 8 regressions on master-thumb_m7_hard_eabi
On Fri, 7 Mar 2025 at 12:53, Christophe Lyon
wrote:
> On Wed, 5 Mar 2025 at 23:32, Jonathan Wakely wrote:
> >
> > On Mon, 3 Mar 2025 at 09:27, Jonathan Wakely wrote:
> > >
> > > On Mon, 3 Mar 2025 at 09:10, Christophe Lyon <
> christophe.l...@linaro.org> wrote:
> > > >
> > > > Hi Jonathan,
> > > >
> > > > On Sun, 2 Mar 2025 at 23:28, Jonathan Wakely via Gcc-regression
> > > > wrote:
> > > > >
> > > > > On Sun, 2 Mar 2025 at 02:42, wrote:
> > > > > >
> > > > > > Dear contributor,
> > > > > >
> > > > > > Our automatic CI has detected problems related to your
> patch(es). Please find some details below.
> > > > > >
> > > > > > In arm-eabi cortex-m7 hard, after:
> > > > > > | commit gcc-15-7765-g3866ca796d5
> > > > > > | Author: Jonathan Wakely
> > > > > > | Date: Thu Feb 27 13:27:17 2025 +
> > > > > > |
> > > > > > | libstdc++: Fix ranges::move and ranges::move_backward to
> use iter_move [PR105609]
> > > > > > |
> > > > > > | The ranges::move and ranges::move_backward algorithms
> are supposed to
> > > > > > | use ranges::iter_move(iter) instead of std::move(*iter),
> which matters
> > > > > > | for an iterator type with an iter_move overload findable
> by ADL.
> > > > > > | ... 16 lines of the commit log omitted.
> > > > > >
> > > > > > Produces 8 regressions:
> > > > > > |
> > > > > > | regressions.sum:
> > > > > > | Running libstdc++:libstdc++-dg/conformance.exp ...
> > > > > > | FAIL: 25_algorithms/move/constrained.cc -std=gnu++20 (test
> for excess errors)
> > > > > > | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++20
> compilation failed to produce executable
> > > > > > | FAIL: 25_algorithms/move/constrained.cc -std=gnu++26 (test
> for excess errors)
> > > > > > | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++26
> compilation failed to produce executable
> > > > > > | ... and 4 more
> > > > >
> > > > > It looks like thumb has some unusual linking requirements that I'm
> not
> > > > > familiar with, so undefined functions (which are never actually
> called
> > > > > in the test) cause linker errors:
> > > > >
> > > > >
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
> > > > > undefined reference to `pr105609::iter_move(pr105609::I const&)'
> > > > >
> /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
> > > > > (_ZN8pr1056099iter_moveERKNS_1IE): Unknown destination type
> > > > > (ARM/Thumb) in /tmp/ccqKQGzN.o
> > > >
> > > > This is a "recent" linker warning, which I added sometime during last
> > > > year (so you need recent binutils if you want to try to reproduce the
> > > > problem).
> > > > It means that for some reason the destination symbol lacks a tag (asm
> > > > directive) saying whether it's a thumb or an arm function. This is
> > > > used by the linker when deciding which type of stub to insert (if
> > > > any).
> > > > For instance: ".type myfunc, %function"
> > > > but normally the compiler adds this for you.
> > > >
> > > > But you mention "undefined functions", so that would probably be the
> > > > reason, but how can the link succeed? Are you linking with "-z
> undefs"
> > > > ?
> > >
> > > See e.g. libstdc++-v3/testsuite/25_algorithms/move/constrained.cc
> > > The test06 function uses undefined member functions such as
> > > I::operator== but because test06 is never called, it shouldn't matter.
> > >
> > > I can move test06 to a separate { dg-do compile } test, where the
> > > linker isn't involved at all.
> >
> > I hope this is fixed at
> >
> > r15-7842-gc21d5a3591fd761872e18278e1cd8ec18e36d4cb
> >
>
> Indeed, the tests now pass.
>
Great, thanks for confirming it.
>
> I still haven't understood why the original version passed on some
> targets? (I assume so, I suppose you tested the patch before
> committing ;-) )
>
I did! :-)
> Even if not called, test06 would still have references I::operator==
> whatever the target?
>
Maybe the whole of test06 was optimized away as dead code.
Regressions on native/master at commit r15-7878 vs commit r15-7876 on Linux/x86_64
Regressions on master at commit r15-7878 vs commit r15-7876 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 c + 1 == 2 FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 c + 1 == 2 FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 i + 1 == 8 FAIL: gcc.dg/guality/pr90074.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 28 i + 1 == 8 FAIL: gcc.dg/guality/pr90716.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 23 j + 1 == 9 FAIL: gcc.dg/guality/pr90716.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 23 j + 1 == 9
Regressions on master at commit r15-7887 vs commit r15-7886 on Linux/x86_64
Regressions on master at commit r15-7887 vs commit r15-7886 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps
Regressions on master at commit r15-7898 vs commit r15-7895 on Linux/x86_64
Regressions on master at commit r15-7898 vs commit r15-7895 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40)
Regressions on native/master at commit r15-7894 vs commit r15-7890 on Linux/x86_64
Regressions on master at commit r15-7894 vs commit r15-7890 on Linux/x86_64 New failures: FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) New passes:
Regressions on native/master at commit r15-7898 vs commit r15-7894 on Linux/x86_64
Regressions on master at commit r15-7898 vs commit r15-7894 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-2a.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40) FAIL: gcc.dg/Wreturn-mismatch-6.c (test for warnings, line 40)
