Regressions on master at commit r15-7824 vs commit r15-7823 on Linux/x86_64
Regressions on master at commit r15-7824 vs commit r15-7823 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 releases/gcc-13 at commit r13-9412 vs commit r13-9401 on Linux/x86_64
Regressions on releases/gcc-13 at commit r13-9412 vs commit r13-9401 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/torture/convert-dfp.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors)
Regressions on native/releases/gcc-14 at commit r14-11384 vs commit r14-11382 on Linux/x86_64
Regressions on releases/gcc-14 at commit r14-11384 vs commit r14-11382 on Linux/x86_64 New failures: FAIL: c-c++-common/tsan/atomic_stack.c -O2 output pattern test FAIL: c-c++-common/tsan/fd_pipe_race.c -O0 output pattern test FAIL: c-c++-common/tsan/fd_pipe_race.c -O2 output pattern test FAIL: c-c++-common/tsan/free_race2.c -O0 output pattern test FAIL: c-c++-common/tsan/free_race2.c -O2 output pattern test FAIL: c-c++-common/tsan/free_race.c -O0 output pattern test FAIL: c-c++-common/tsan/free_race.c -O2 output pattern test FAIL: c-c++-common/tsan/pr65400-1.c -O0 output pattern test FAIL: c-c++-common/tsan/pr65400-1.c -O2 output pattern test FAIL: c-c++-common/tsan/pr65400-3.c -O2 output pattern test FAIL: c-c++-common/tsan/pr68260.c -O2 execution test FAIL: c-c++-common/tsan/race_on_barrier2.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_barrier.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_barrier.c -O2 output pattern test FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O0 execution test New passes: FAIL: c-c++-common/tsan/pr68260.c -O0 execution test FAIL: c-c++-common/tsan/race_on_barrier2.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_mutex2.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_mutex2.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_mutex2.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_mutex.c -O2 output pattern test FAIL: c-c++-common/tsan/simple_race.c -O2 output pattern test FAIL: c-c++-common/tsan/thread_leak1.c -O0 output pattern test FAIL: c-c++-common/tsan/thread_leak1.c -O2 output pattern test FAIL: c-c++-common/tsan/thread_leak.c -O0 execution test FAIL: c-c++-common/tsan/thread_leak.c -O2 execution test FAIL: c-c++-common/tsan/tiny_race.c -O0 output pattern test FAIL: c-c++-common/tsan/tiny_race.c -O2 output pattern test FAIL: g++.dg/tsan/fd_close_norace2.C -O2 execution test FAIL: g++.dg/tsan/pr64265.C -O2 output pattern test FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O2 execution test FAIL: g++.dg/tsan/vptr_benign_race.C -O0 execution test FAIL: g++.dg/tsan/vptr_harmful_race.C -O0 output pattern test
Regressions on master at commit r15-7838 vs commit r15-7833 on Linux/x86_64
Regressions on master at commit r15-7838 vs commit r15-7833 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 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
Regressions on master at commit r15-7839 vs commit r15-7838 on Linux/x86_64
Regressions on master at commit r15-7839 vs commit r15-7838 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 native/releases/gcc-14 at commit r14-11387 vs commit r14-11384 on Linux/x86_64
Regressions on releases/gcc-14 at commit r14-11387 vs commit r14-11384 on Linux/x86_64 New failures: FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O2 execution test New passes: FAIL: c-c++-common/tsan/atomic_stack.c -O2 output pattern test FAIL: c-c++-common/tsan/fd_pipe_race.c -O0 output pattern test FAIL: c-c++-common/tsan/fd_pipe_race.c -O2 output pattern test FAIL: c-c++-common/tsan/free_race2.c -O0 output pattern test FAIL: c-c++-common/tsan/free_race2.c -O2 output pattern test FAIL: c-c++-common/tsan/free_race.c -O0 output pattern test FAIL: c-c++-common/tsan/free_race.c -O2 output pattern test FAIL: c-c++-common/tsan/pr65400-1.c -O0 output pattern test FAIL: c-c++-common/tsan/pr65400-1.c -O2 output pattern test FAIL: c-c++-common/tsan/pr65400-3.c -O0 output pattern test FAIL: c-c++-common/tsan/pr65400-3.c -O2 output pattern test FAIL: c-c++-common/tsan/pr68260.c -O2 execution test FAIL: c-c++-common/tsan/race_on_barrier2.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_barrier.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_barrier.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_mutex2.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_mutex.c -O0 output pattern test
