Re: [Linaro-TCWG-CI] gcc-15-3614-g9fe57e4879de: FAIL: 12 regressions on aarch64
On Fri, 13 Sept 2024 at 07:09, wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We understand that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1344 , > please let us know if you are looking at the problem and/or when you have a > fix. This should be fixed by https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662945.html > > In gcc_check master-aarch64 after: > > | commit gcc-15-3614-g9fe57e4879de > | Author: Jonathan Wakely > | Date: Wed Sep 11 11:47:44 2024 +0100 > | > | c++: Make __builtin_launder reject invalid types [PR116673] > | > | The standard says that std::launder is ill-formed for function > pointers > | and cv void pointers, so there's no reason for __builtin_launder to > | accept them. This change allows implementations of std::launder to > defer > | to the built-in for error checking, although libstdc++ will continue > to > | diagnose it directly for more user-friendly diagnostics. > | ... 12 lines of the commit log omitted. > > FAIL: 12 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++11 (test for errors, line 304) > FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++11 (test for excess errors) > FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++17 (test for errors, line 304) > FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++17 (test for excess errors) > FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++98 (test for errors, line 304) > FAIL: g++.dg/ext/sve-sizeless-1.C -std=gnu++98 (test for excess errors) > FAIL: g++.dg/ext/sve-sizeless-2.C -std=gnu++11 (test for errors, line 304) > ... and 6 more entries > > You can find the failure logs in *.log.1.xz files in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/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/2595/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifact/artifacts/sumfiles/xfails.xfail > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -8<--8<--8<-- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2594/artifact/artifacts > > Reproduce last good and first bad builds: > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/9fe57e4879de93b6e3c7b4c226f42d5f3a48474f/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt > > Full commit : > https://github.com/gcc-mirror/gcc/commit/9fe57e4879de93b6e3c7b4c226f42d5f3a48474f > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 12 regressions > *** > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/9fe57e4879de93b6e3c7b4c226f42d5f3a48474f/tcwg_gcc_check/master-aarch64/details.txt > *** > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifact/artifacts
Re: [Linaro-TCWG-CI] gcc-14-9478-gdf483ebd246: FAIL: 7 regressions on aarch64
Oops. Jakub has fixed this now. On Thu, 14 Mar 2024 at 23:45, wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We appreciate that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1177 , > please let us know if you are looking at the problem and/or when you have a > fix. > > In gcc_check master-aarch64 after: > > | commit gcc-14-9478-gdf483ebd246 > | Author: Jonathan Wakely > | Date: Mon Feb 26 13:17:13 2024 + > | > | libstdc++: Add nodiscard in > | > | Add the [[nodiscard]] attribute to several functions in . > | These all have no side effects and are only called for their return > | value (e.g. std::count) or produce a result that must not be discarded > | for correctness (e.g. std::remove). > | > | ... 49 lines of the commit log omitted. > > FAIL: 7 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/torture/dg-torture.exp ... > FAIL: g++.dg/torture/pr104601.C -O0 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O1 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 -flto -fno-use-linker-plugin > -flto-partition=none (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O2 -flto -fuse-linker-plugin > -fno-fat-lto-objects (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -O3 -g (test for excess errors) > FAIL: g++.dg/torture/pr104601.C -Os (test for excess errors) > ... and 1 more entries > > You can find the failure logs in *.log.1.xz files in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifact/artifacts/00-sumfiles/ > The full lists of regressions and progressions as well as configure and make > commands are in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > - > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifact/artifacts/sumfiles/xfails.xfail > > The configuration of this build is: > CI config tcwg_gcc_check master-aarch64 > > -8<--8<--8<-- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1714/artifact/artifacts > > Reproduce last good and first bad builds: > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/df483ebd24689a3bebfae2089637a00eca0e5a12/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt > > Full commit : > https://github.com/gcc-mirror/gcc/commit/df483ebd24689a3bebfae2089637a00eca0e5a12 > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 7 regressions > *** > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/df483ebd24689a3bebfae2089637a00eca0e5a12/tcwg_gcc_check/master-aarch64/details.txt > *** > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1715/artifact/artifacts
Re: [Linaro-TCWG-CI] gcc-15-3575-gc07cf418fdde: FAIL: 2 regressions on master-thumb_m0_eabi
On Mon, 30 Sept 2024 at 07:22, wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We understand that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1358 , > please let us know if you are looking at the problem and/or when you have a > fix. > > In arm-eabi cortex-m0 soft after: > > | commit gcc-15-3575-gc07cf418fdde > | Author: Jonathan Wakely > | Date: Tue Sep 10 14:25:41 2024 +0100 > | > | libstdc++: std::string move assignment should not use POCCA trait > [PR116641] > | > | The changes to implement LWG 2579 (r10-327-gdb33efde17932f) made > | std::string::assign use the propagate_on_container_copy_assignment > | (POCCA) trait, for consistency with operator=(const basic_string&). > | ... 18 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > | === libstdc++ tests === > | > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 (test for > excess errors) > | UNRESOLVED: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 > compilation failed to produce executable > | > | # "FAIL" means : the execution of the compiled binary failed / output of > the binary differs from the expected one > > You can find the failure logs in *.log.1.xz files in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/00-sumfiles/ === libstdc++ Summary === # of expected passes6036 # of unexpected failures4689 <<< !!! Is that normal for this configuration?! The new testcase fails for the same reason as the 4000 other tests: /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: (__deregister_frame_info): Unknown destination type (ARM/Thumb) in /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/./gcc/crtbegin.o crtstuff.c:(.text+0x5e): dangerous relocation: unsupported relocation So I don't think this is a problem in the commit, I think it's just a configuration that isn't well supported. > The full lists of regressions and improvements as well as configure and make > commands are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/sumfiles/xfails.xfail > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m > -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto > > -8<--8<--8<-- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/546/artifact/artifacts > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/c07cf418fdde0c192e370a8d76a991cc7215e9c4/tcwg_gnu_embed_check_gcc/master-thumb_m0_eabi/reproduction_instructions.txt > > Full commit : > https://github.com/gcc-mirror/gcc/commit/c07cf418fdde0c192e370a8d76a991cc7215e9c4
Re: [Linaro-TCWG-CI] gcc-15-4016-gc534e37facc: FAIL: 1 regressions on arm
On Thu, 10 Oct 2024 at 06:33, wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We understand that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1370 , > please let us know if you are looking at the problem and/or when you have a > fix. I'm not sure what the problem is here. It looks like the build uses --enable-clocale=gnu and so I would expect the test to PASS on this target, like it does on x86_64-pc-linux-gnu. Maybe it's a newlib vs glibc difference. Looking into it ... > > In arm-eabi v7-a softfp after: > > | commit gcc-15-4016-gc534e37facc > | Author: Jonathan Wakely > | Date: Tue Sep 24 23:20:56 2024 +0100 > | > | libstdc++: Populate std::time_get::get's %c format for C locale > | > | We were using the empty string "" for D_T_FMT and ERA_D_T_FMT in the C > | locale, instead of "%a %b %e %T %Y" as the C standard requires. Set it > | correctly for each locale implementation that defines time_members.cc. > | ... 18 lines of the commit log omitted. > > FAIL: 1 regressions > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a > -mfpu=vfpv3-d16 -mfloat-abi=softfp > configure and test flags: --target arm-eabi --disable-multilib > --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp > --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp > qemu_cpu=cortex-a9 > > regressions.sum: > | === libstdc++ tests === > | > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 22_locale/time_get/get/wchar_t/5.cc -std=gnu++17 execution test > | > > You can find the failure logs in *.log.1.xz files in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_eabi-build/628/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_gnu_embed_check_gcc--master-arm_v7a_softfp_eabi-build/628/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_eabi-build/628/artifact/artifacts/sumfiles/xfails.xfail > > -8<--8<--8<-- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_eabi-build/628/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_eabi-build/627/artifact/artifacts > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/c534e37faccf481afa9bc28f0605ca0ec3846c89/tcwg_gnu_embed_check_gcc/master-arm_v7a_softfp_eabi/reproduction_instructions.txt > > Full commit : > https://github.com/gcc-mirror/gcc/commit/c534e37faccf481afa9bc28f0605ca0ec3846c89
Re: [Linaro-TCWG-CI] gcc-15-4709-gb281e13ecad1: FAIL: 2 regressions on arm
Fixed at r15-4720-ge320846fec00aa On Mon, 28 Oct 2024 at 01:20, wrote: > > Dear contributor, our automatic CI has detected problems related to your > patch(es). Please find some details below. If you have any questions, > please follow up on linaro-toolch...@lists.linaro.org mailing list, Libera's > #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on > the usual project channel. > > We understand that it might be difficult to find the necessary logs or > reproduce the issue locally. If you can't get what you need from our CI > within minutes, let us know and we will be happy to help. > > We track this report status in https://linaro.atlassian.net/browse/GNU-1390 , > please let us know if you are looking at the problem and/or when you have a > fix. > > In gcc_check master-arm after: > > | commit gcc-15-4709-gb281e13ecad1 > | Author: Jonathan Wakely > | Date: Tue Oct 8 21:15:18 2024 +0100 > | > | libstdc++: Add P1206R7 from_range members to std::vector [PR111055] > | > | This is another piece of P1206R7, adding new members to std::vector > and > | std::vector. > | > | ... 40 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > | === libstdc++ tests === > | > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++23 (test for > excess errors) > | FAIL: 23_containers/vector/cons/from_range.cc -std=gnu++26 (test for > excess errors) > | > The configuration of this build is: > CI config tcwg_gcc_check master-arm > configure and test flags: --target arm-linux-gnueabihf > > You can find the failure logs in *.log.1.xz files in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/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-arm-build/2927/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/artifacts/sumfiles/xfails.xfail > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > configure and test flags: --target arm-linux-gnueabihf > > -8<--8<--8<-- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2927/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2926/artifact/artifacts > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/b281e13ecad12d07209924a7282c53be3a1c3774/tcwg_gcc_check/master-arm/reproduction_instructions.txt > > Full commit : > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b281e13ecad12d07209924a7282c53be3a1c3774
Re: [Linaro-TCWG-CI] gcc-15-3575-gc07cf418fdde: FAIL: 2 regressions on master-thumb_m0_eabi
On Mon, 30 Sept 2024 at 15:36, Christophe Lyon wrote: > > On Mon, 30 Sept 2024 at 10:49, Jonathan Wakely via Gcc-regression > wrote: > > > > On Mon, 30 Sept 2024 at 07:22, wrote: > > > > > > Dear contributor, our automatic CI has detected problems related to your > > > patch(es). Please find some details below. If you have any questions, > > > please follow up on linaro-toolch...@lists.linaro.org mailing list, > > > Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain > > > developer on the usual project channel. > > > > > > We understand that it might be difficult to find the necessary logs or > > > reproduce the issue locally. If you can't get what you need from our CI > > > within minutes, let us know and we will be happy to help. > > > > > > We track this report status in > > > https://linaro.atlassian.net/browse/GNU-1358 , please let us know if you > > > are looking at the problem and/or when you have a fix. > > > > > > In arm-eabi cortex-m0 soft after: > > > > > > | commit gcc-15-3575-gc07cf418fdde > > > | Author: Jonathan Wakely > > > | Date: Tue Sep 10 14:25:41 2024 +0100 > > > | > > > | libstdc++: std::string move assignment should not use POCCA trait > > > [PR116641] > > > | > > > | The changes to implement LWG 2579 (r10-327-gdb33efde17932f) made > > > | std::string::assign use the propagate_on_container_copy_assignment > > > | (POCCA) trait, for consistency with operator=(const > > > basic_string&). > > > | ... 18 lines of the commit log omitted. > > > > > > FAIL: 2 regressions > > > > > > regressions.sum: > > > | === libstdc++ tests === > > > | > > > | Running libstdc++:libstdc++-dg/conformance.exp ... > > > | FAIL: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 (test > > > for excess errors) > > > | UNRESOLVED: 21_strings/basic_string/allocator/116641.cc -std=gnu++17 > > > compilation failed to produce executable > > > | > > > | # "FAIL" means : the execution of the compiled binary failed / output > > > of the binary differs from the expected one > > > > > > You can find the failure logs in *.log.1.xz files in > > > * > > > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/00-sumfiles/ > > > > === libstdc++ Summary === > > > > # of expected passes6036 > > # of unexpected failures4689 <<< !!! > > > > Is that normal for this configuration?! > > > > The new testcase fails for the same reason as the 4000 other tests: > > > > /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: > > (__deregister_frame_info): Unknown destination type (ARM/Thumb) in > > /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/./gcc/crtbegin.o > > crtstuff.c:(.text+0x5e): dangerous relocation: unsupported relocation > > > > So I don't think this is a problem in the commit, I think it's just a > > configuration that isn't well supported. > > > Indeed. > This error was caused by a linker patch of mine, which I've now fixed. Aha, I didn't know if they were longstanding failures or just recent ones. > The CI detected the problem before I pushed my fixed and saw the new > test failing, and reported it as a regression (it has no way of > guessing it's actually a problem with the linker). Gotcha - it's a new failure caused by my patch, so identifying it as a separate regression is of course "correct" in general. > > That being said, we normally start bisection with "new" master branch > (instead of "current" master as of when the regression was detected), > in case it has been fixed between when it was detected and when bisect > actually starts. In this case, I think we had a huge backlog of > regressions to bisect because of my incorrect linker patch, which took > time to recover. Ouch :-) Thanks for the explanations. > Thanks for checking! > > Christophe > > > > > > The full lists of regressions and improvements as well as configure and > > > make commands are in > > > * > > > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-build/547/artifact/artifacts/notify/ > > > The l
Re: [Linaro-TCWG-CI] gcc-15-6060-ge4a0157c2397: 3 regressions on arm
On Tue, 10 Dec 2024 at 08:48, wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find > some details below. > > In gcc_check master-arm, after: > | commit gcc-15-6060-ge4a0157c2397 > | Author: Giuseppe D'Angelo > | Date: Mon Dec 9 02:11:19 2024 +0100 > | > | libstdc++: port bitwise relocatable away from is_trivial > | > | In preparation for the deprecation of is_trivial (P3247R2). > | "bitwise relocation" (or "trivial relocation" à la P1144/P2786) > | doesn't need the full-fledged notion of triviality, just checking for > a > | ... 8 lines of the commit log omitted. > > Produces 3 regressions: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++11 (test for excess errors) > | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++17 (test for excess errors) > | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++26 (test for excess errors) > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* --target arm-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1456. > Please let us know if you have a fix. Fixed at r15-6073-g4b9e1db1a14dbf > > 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-arm-build/3141/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-arm-build/3141/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3141/artifact/artifacts/sumfiles/xfails.xfail > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3141/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3140/artifact/artifacts > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/e4a0157c2397c9b582cff71d114240a6b083a3dc/tcwg_gcc_check/master-arm/reproduction_instructions.txt > > Full commit : > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e4a0157c2397c9b582cff71d114240a6b083a3dc
Re: [Linaro-TCWG-CI] gcc-15-6063-g6c41a912f5e: 1 regressions on arm
On Tue, 10 Dec 2024 at 14:21, wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find > some details below. > > In gcc_check master-arm, after: > | commit gcc-15-6063-g6c41a912f5e > | Author: Giuseppe D'Angelo > | Date: Mon Dec 9 01:28:08 2024 +0100 > | > | libstdc++: deprecate is_trivial for C++26 (P3247R2) > | > | This actually implements P3247R2 by deprecating the is_trivial type > | trait. > | > | ... 17 lines of the commit log omitted. > > Produces 1 regressions: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/cpp0x/trivial1.C -std=c++26 (test for excess errors) > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* --target arm-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1457. > Please let us know if you have a fix. Fixed at r15-6080-g7aab1271b4afb6 > > 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-arm-build/3145/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-arm-build/3145/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3145/artifact/artifacts/sumfiles/xfails.xfail > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3145/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3144/artifact/artifacts > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/6c41a912f5e654a1b6f7cf8d6b23f00d8612988c/tcwg_gcc_check/master-arm/reproduction_instructions.txt > > Full commit : > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=6c41a912f5e654a1b6f7cf8d6b23f00d8612988c
Re: [Linaro-TCWG-CI] gcc-15-8035-g7ee31bc9276: 2 regressions on master-thumb_m23_soft_eabi
On Mon, 17 Mar 2025 at 14:54, Jonathan Wakely wrote: > > On Mon, 17 Mar 2025 at 09:53, Jonathan Wakely wrote: > > > > > > > > On Monday, 17 March 2025, Christophe Lyon > > wrote: > > > On Sun, 16 Mar 2025 at 21:54, Jonathan Wakely wrote: > > >> > > >> On Sun, 16 Mar 2025 at 13:16, wrote: > > >> > > > >> > Dear contributor, > > >> > > > >> > Our automatic CI has detected problems related to your patch(es). > > >> > Please find some details below. > > >> > > > >> > In arm-eabi cortex-m23 soft, after: > > >> > | commit gcc-15-8035-g7ee31bc9276 > > >> > | Author: Jonathan Wakely > > >> > | Date: Thu Mar 13 13:34:55 2025 + > > >> > | > > >> > | libstdc++: Implement for C++26 (P3370R1) > > >> > | > > >> > | This is the first part of the P3370R1 proposal just approved > > >> > by the > > >> > | committee in Wrocław. This adds C++ equivalents of the > > >> > functions added > > >> > | to C23 by WG14 N3022. > > >> > | ... 16 lines of the commit log omitted. > > >> > > > >> > Produces 2 regressions: > > >> > | > > >> > | regressions.sum: > > >> > | Running libstdc++:libstdc++-dg/conformance.exp ... > > >> > | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors) > > >> > | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to > > >> > produce executable > > >> > > > >> > Used configuration : > > >> > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb > > >> > -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto > > >> > *configure and test flags:* --target arm-eabi --disable-multilib > > >> > --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft > > >> > --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto > > >> > qemu_cpu=cortex-m33 > > >> > > > >> > We track this bug report under > > >> > https://linaro.atlassian.net/browse/GNU-1543. Please let us know if > > >> > you have a fix. > > >> > > >> All the errors are of the form: > > >> error: 'ULLONG_MAX' was not declared in this scope > > >> but the test includes . > > >> > > >> So this target doesn't support long long? Or just doesn't define > > >> ULLONG_MAX? > > >> > > > > > > It does... > > > > > > I've manually reproduced it, and ISTM the problem is __STDC_VERSION__ > > > is not defined, > > > as gcc/glimits.h expects: > > > https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/glimits.h;h=d5877602bf741383cfddb13236fbba1cf0b5b520;hb=HEAD#l102 > > > > > > Aha! Thanks. > > > > > Compiling > > > == > > > #include > > > unsigned long long var = ULLONG_MAX; > > > > > > works with the same compiler, in C mode. > > > > > > But why would that work on arm-linux-gnueabihf and not on arm-none-eabi? > > > > I think glimits.h use only used if libc doesn't provide one, and I guess > > glibc's limits.h is used for gnueabihf > > > > The C++ standard says it's implementation-defined whether __STDC_VERSION__ > > is defined by a C++ compiler, and if defined, it's implementation-defined > > what is value is > > > > GCC/glimits.h should check || (defined(__cplusplus) && __cplusplus >= > > 201103L)) > > > > i.e. long long should be supported for C++11 and later. > > > > Libstdc++ actually assumes long long is always supported even for C++98 so > > I'm surprised we've never noticed this before! I think we probably use the > > type without using the LLONG_MAX macro, so it just happens to work. > > > > I can adjust the test to be agnostic to that macro, but I'll also propose a > > patch to check __cplusplus in glimits.h > > > > Thanks again for finding the cause here. > > Hmm, except that libstdc++ provides which should add > ULLONG_MAX if it's not defined by libc: > https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/include/c_global/climits > And should find the libstdc++ version which includes > ., but we're not installing the libstdc++ version of > . > That's a libstdc++ bug. The FAIL for arm-none-eabi should be fixed at r15-8450-g562416d8131dc9 I'll deal with the libstdc++ bug in stage 1.
Re: [Linaro-TCWG-CI] gcc-15-8035-g7ee31bc9276: 2 regressions on master-thumb_m23_soft_eabi
On Monday, 17 March 2025, Christophe Lyon wrote: > On Sun, 16 Mar 2025 at 21:54, Jonathan Wakely wrote: >> >> On Sun, 16 Mar 2025 at 13:16, wrote: >> > >> > Dear contributor, >> > >> > Our automatic CI has detected problems related to your patch(es). Please find some details below. >> > >> > In arm-eabi cortex-m23 soft, after: >> > | commit gcc-15-8035-g7ee31bc9276 >> > | Author: Jonathan Wakely >> > | Date: Thu Mar 13 13:34:55 2025 + >> > | >> > | libstdc++: Implement for C++26 (P3370R1) >> > | >> > | This is the first part of the P3370R1 proposal just approved by the >> > | committee in Wrocław. This adds C++ equivalents of the functions added >> > | to C23 by WG14 N3022. >> > | ... 16 lines of the commit log omitted. >> > >> > Produces 2 regressions: >> > | >> > | regressions.sum: >> > | Running libstdc++:libstdc++-dg/conformance.exp ... >> > | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors) >> > | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to produce executable >> > >> > Used configuration : >> > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto >> > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33 >> > >> > We track this bug report under https://linaro.atlassian.net/browse/GNU-1543. Please let us know if you have a fix. >> >> All the errors are of the form: >> error: 'ULLONG_MAX' was not declared in this scope >> but the test includes . >> >> So this target doesn't support long long? Or just doesn't define ULLONG_MAX? >> > > It does... > > I've manually reproduced it, and ISTM the problem is __STDC_VERSION__ > is not defined, > as gcc/glimits.h expects: > https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/glimits.h;h=d5877602bf741383cfddb13236fbba1cf0b5b520;hb=HEAD#l102 Aha! Thanks. > Compiling > == > #include > unsigned long long var = ULLONG_MAX; > > works with the same compiler, in C mode. > > But why would that work on arm-linux-gnueabihf and not on arm-none-eabi? I think glimits.h use only used if libc doesn't provide one, and I guess glibc's limits.h is used for gnueabihf The C++ standard says it's implementation-defined whether __STDC_VERSION__ is defined by a C++ compiler, and if defined, it's implementation-defined what is value is GCC/glimits.h should check || (defined(__cplusplus) && __cplusplus >= 201103L)) i.e. long long should be supported for C++11 and later. Libstdc++ actually assumes long long is always supported even for C++98 so I'm surprised we've never noticed this before! I think we probably use the type without using the LLONG_MAX macro, so it just happens to work. I can adjust the test to be agnostic to that macro, but I'll also propose a patch to check __cplusplus in glimits.h Thanks again for finding the cause here. > > Christophe > >> ___ >> linaro-toolchain mailing list -- linaro-toolch...@lists.linaro.org >> To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org > >
Re: [Linaro-TCWG-CI] gcc-15-8035-g7ee31bc9276: 2 regressions on master-thumb_m23_soft_eabi
On Mon, 17 Mar 2025 at 09:53, Jonathan Wakely wrote: > > > > On Monday, 17 March 2025, Christophe Lyon wrote: > > On Sun, 16 Mar 2025 at 21:54, Jonathan Wakely wrote: > >> > >> On Sun, 16 Mar 2025 at 13:16, wrote: > >> > > >> > Dear contributor, > >> > > >> > Our automatic CI has detected problems related to your patch(es). Please > >> > find some details below. > >> > > >> > In arm-eabi cortex-m23 soft, after: > >> > | commit gcc-15-8035-g7ee31bc9276 > >> > | Author: Jonathan Wakely > >> > | Date: Thu Mar 13 13:34:55 2025 + > >> > | > >> > | libstdc++: Implement for C++26 (P3370R1) > >> > | > >> > | This is the first part of the P3370R1 proposal just approved by > >> > the > >> > | committee in Wrocław. This adds C++ equivalents of the functions > >> > added > >> > | to C23 by WG14 N3022. > >> > | ... 16 lines of the commit log omitted. > >> > > >> > Produces 2 regressions: > >> > | > >> > | regressions.sum: > >> > | Running libstdc++:libstdc++-dg/conformance.exp ... > >> > | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors) > >> > | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to > >> > produce executable > >> > > >> > Used configuration : > >> > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb > >> > -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto > >> > *configure and test flags:* --target arm-eabi --disable-multilib > >> > --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft > >> > --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto > >> > qemu_cpu=cortex-m33 > >> > > >> > We track this bug report under > >> > https://linaro.atlassian.net/browse/GNU-1543. Please let us know if you > >> > have a fix. > >> > >> All the errors are of the form: > >> error: 'ULLONG_MAX' was not declared in this scope > >> but the test includes . > >> > >> So this target doesn't support long long? Or just doesn't define > >> ULLONG_MAX? > >> > > > > It does... > > > > I've manually reproduced it, and ISTM the problem is __STDC_VERSION__ > > is not defined, > > as gcc/glimits.h expects: > > https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/glimits.h;h=d5877602bf741383cfddb13236fbba1cf0b5b520;hb=HEAD#l102 > > > Aha! Thanks. > > > Compiling > > == > > #include > > unsigned long long var = ULLONG_MAX; > > > > works with the same compiler, in C mode. > > > > But why would that work on arm-linux-gnueabihf and not on arm-none-eabi? > > I think glimits.h use only used if libc doesn't provide one, and I guess > glibc's limits.h is used for gnueabihf > > The C++ standard says it's implementation-defined whether __STDC_VERSION__ is > defined by a C++ compiler, and if defined, it's implementation-defined what > is value is > > GCC/glimits.h should check || (defined(__cplusplus) && __cplusplus >= > 201103L)) > > i.e. long long should be supported for C++11 and later. > > Libstdc++ actually assumes long long is always supported even for C++98 so > I'm surprised we've never noticed this before! I think we probably use the > type without using the LLONG_MAX macro, so it just happens to work. > > I can adjust the test to be agnostic to that macro, but I'll also propose a > patch to check __cplusplus in glimits.h > > Thanks again for finding the cause here. Hmm, except that libstdc++ provides which should add ULLONG_MAX if it's not defined by libc: https://gcc.gnu.org/cgit/gcc/tree/libstdc++-v3/include/c_global/climits And should find the libstdc++ version which includes ., but we're not installing the libstdc++ version of . That's a libstdc++ bug.
Re: [Linaro-TCWG-CI] gcc-15-8035-g7ee31bc9276: 2 regressions on master-thumb_m23_soft_eabi
On Sun, 16 Mar 2025 at 13:16, wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find > some details below. > > In arm-eabi cortex-m23 soft, after: > | commit gcc-15-8035-g7ee31bc9276 > | Author: Jonathan Wakely > | Date: Thu Mar 13 13:34:55 2025 + > | > | libstdc++: Implement for C++26 (P3370R1) > | > | This is the first part of the P3370R1 proposal just approved by the > | committee in Wrocław. This adds C++ equivalents of the functions added > | to C23 by WG14 N3022. > | ... 16 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors) > | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to > produce executable > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base > -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib > --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft > --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto > qemu_cpu=cortex-m33 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1543. > Please let us know if you have a fix. All the errors are of the form: error: 'ULLONG_MAX' was not declared in this scope but the test includes . So this target doesn't support long long? Or just doesn't define ULLONG_MAX?
Re: [Linaro-TCWG-CI] gcc-15-8904-ge200f53a555: 2 regressions on aarch64
On Wed, 26 Mar 2025 at 10:17, Jonathan Wakely wrote:
>
> On Wed, 26 Mar 2025 at 09:55, Jonathan Wakely wrote:
> >
> > On Wed, 26 Mar 2025 at 00:55, wrote:
> > >
> > > 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-8904-ge200f53a555
> > > | Author: Jonathan Wakely
> > > | Date: Tue Mar 25 13:24:08 2025 +
> > > |
> > > | libstdc++: Optimize std::vector construction from input iterators
> > > [PR108487]
> > > |
> > > | LWG 3291 make std::ranges::iota_view's iterator have
> > > input_iterator_tag
> > > | as its iterator_category, even though it satisfies the C++20
> > > | std::forward_iterator concept. This means that the traditional
> > > | ... 41 lines of the commit log omitted.
> > >
> > > Produces 2 regressions:
> > > |
> > > | regressions.sum:
> > > | Running g++:g++.dg/dg.exp ...
> > > | FAIL: g++.dg/tree-ssa/initlist-opt1.C -std=c++26 scan-tree-dump
> > > gimple "_M_range_initialize"
> > > | FAIL: g++.dg/tree-ssa/initlist-opt2.C -std=c++26 scan-tree-dump
> > > gimple "_M_range_initialize"
> > >
> > > 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-1548. Please let us know if you
> > > have a fix.
> >
> > I have a fix:
> >
> > --- a/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
> > +++ b/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
> > @@ -4,7 +4,7 @@
> > // { dg-skip-if "requires hosted libstdc++ for string" { ! hostedlib } }
> >
> > // Test that we do range-initialization from const char *.
> > -// { dg-final { scan-tree-dump {_M_range_initialize > const\*>} "gimple" } }
> > +// { dg-final { scan-tree-dump {_M_range_initialize_n > const\*} "gimple" } }
> > // { dg-final { scan-tree-dump {static const char.*72} "gimple" } }
> >
> > #include
> >
>
> Now posted as https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679317.html
A slightly simpler version of the patch has now been pushed as
r15-8934-g101f302363e877
>
>
> >
> >
> > >
> > > 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/3491/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/3491/artifact/artifacts/notify/
> > > The list of [ignored] baseline and flaky failures are in
> > > *
> > > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifact/artifacts/sumfiles/xfails.xfail
> > >
> > > Current build :
> > > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifact/artifacts
> > > Reference build :
> > > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3490/artifact/artifacts
> > >
> > > Instruction to reproduce the build :
> > > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/e200f53a5556516ec831e6b7a34aaa0f10a4ab0a/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt
> > >
> > > Full commit :
> > > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e200f53a5556516ec831e6b7a34aaa0f10a4ab0a
Re: [Linaro-TCWG-CI] gcc-15-8904-ge200f53a555: 2 regressions on aarch64
On Wed, 26 Mar 2025 at 09:55, Jonathan Wakely wrote:
>
> On Wed, 26 Mar 2025 at 00:55, wrote:
> >
> > 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-8904-ge200f53a555
> > | Author: Jonathan Wakely
> > | Date: Tue Mar 25 13:24:08 2025 +
> > |
> > | libstdc++: Optimize std::vector construction from input iterators
> > [PR108487]
> > |
> > | LWG 3291 make std::ranges::iota_view's iterator have
> > input_iterator_tag
> > | as its iterator_category, even though it satisfies the C++20
> > | std::forward_iterator concept. This means that the traditional
> > | ... 41 lines of the commit log omitted.
> >
> > Produces 2 regressions:
> > |
> > | regressions.sum:
> > | Running g++:g++.dg/dg.exp ...
> > | FAIL: g++.dg/tree-ssa/initlist-opt1.C -std=c++26 scan-tree-dump gimple
> > "_M_range_initialize"
> > | FAIL: g++.dg/tree-ssa/initlist-opt2.C -std=c++26 scan-tree-dump gimple
> > "_M_range_initialize"
> >
> > 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-1548. Please let us know if you
> > have a fix.
>
> I have a fix:
>
> --- a/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
> +++ b/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
> @@ -4,7 +4,7 @@
> // { dg-skip-if "requires hosted libstdc++ for string" { ! hostedlib } }
>
> // Test that we do range-initialization from const char *.
> -// { dg-final { scan-tree-dump {_M_range_initialize const\*>} "gimple" } }
> +// { dg-final { scan-tree-dump {_M_range_initialize_n const\*} "gimple" } }
> // { dg-final { scan-tree-dump {static const char.*72} "gimple" } }
>
> #include
>
Now posted as https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679317.html
>
>
> >
> > 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/3491/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/3491/artifact/artifacts/notify/
> > The list of [ignored] baseline and flaky failures are in
> > *
> > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifact/artifacts/sumfiles/xfails.xfail
> >
> > Current build :
> > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifact/artifacts
> > Reference build :
> > https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3490/artifact/artifacts
> >
> > Instruction to reproduce the build :
> > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/e200f53a5556516ec831e6b7a34aaa0f10a4ab0a/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt
> >
> > Full commit :
> > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e200f53a5556516ec831e6b7a34aaa0f10a4ab0a
Re: [Linaro-TCWG-CI] gcc-15-8904-ge200f53a555: 2 regressions on aarch64
On Wed, 26 Mar 2025 at 00:55, wrote:
>
> 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-8904-ge200f53a555
> | Author: Jonathan Wakely
> | Date: Tue Mar 25 13:24:08 2025 +
> |
> | libstdc++: Optimize std::vector construction from input iterators
> [PR108487]
> |
> | LWG 3291 make std::ranges::iota_view's iterator have
> input_iterator_tag
> | as its iterator_category, even though it satisfies the C++20
> | std::forward_iterator concept. This means that the traditional
> | ... 41 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/tree-ssa/initlist-opt1.C -std=c++26 scan-tree-dump gimple
> "_M_range_initialize"
> | FAIL: g++.dg/tree-ssa/initlist-opt2.C -std=c++26 scan-tree-dump gimple
> "_M_range_initialize"
>
> 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-1548.
> Please let us know if you have a fix.
I have a fix:
--- a/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
+++ b/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
@@ -4,7 +4,7 @@
// { dg-skip-if "requires hosted libstdc++ for string" { ! hostedlib } }
// Test that we do range-initialization from const char *.
-// { dg-final { scan-tree-dump {_M_range_initialize} "gimple" } }
+// { dg-final { scan-tree-dump {_M_range_initialize_n
>
> 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/3491/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/3491/artifact/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
> *
> https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifact/artifacts/sumfiles/xfails.xfail
>
> Current build :
> https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifact/artifacts
> Reference build :
> https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3490/artifact/artifacts
>
> Instruction to reproduce the build :
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/e200f53a5556516ec831e6b7a34aaa0f10a4ab0a/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt
>
> Full commit :
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e200f53a5556516ec831e6b7a34aaa0f10a4ab0a
Re: [Linaro-TCWG-CI] gcc-15-7765-g3866ca796d5: 8 regressions on master-thumb_m7_hard_eabi
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.
>
> Thanks,
>
> Christophe
>
> > /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):
> > dangerous relocation: unsupported relocation
> > /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/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
> > undefined reference to `pr105609::I::operator++()'
> > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
> > (_ZN8pr1056091IppEv): Unknown destination type (ARM/Thumb) in
> > /tmp/ccqKQGzN.o
> > /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/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
> > dangerous relocation: unsupported relocation
> > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
> > /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/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
> > undefined reference to `pr105609::I::operator==(pr105609::I) const'
> > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
> > (_ZNK8pr1056091IeqES0_): Unknown destination type (ARM/Thumb) in
> > /tmp/ccqKQGzN.o
> > /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/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
> > dangerous relocation: unsupported relocation
> >
> > I think I should be able to workaround this.
> >
>
Re: [Linaro-TCWG-CI] gcc-15-7765-g3866ca796d5: 8 regressions on master-thumb_m7_hard_eabi
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 /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): dangerous relocation: unsupported relocation /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/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc): undefined reference to `pr105609::I::operator++()' /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: (_ZN8pr1056091IppEv): Unknown destination type (ARM/Thumb) in /tmp/ccqKQGzN.o /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/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc): dangerous relocation: unsupported relocation /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: /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/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16): undefined reference to `pr105609::I::operator==(pr105609::I) const' /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: (_ZNK8pr1056091IeqES0_): Unknown destination type (ARM/Thumb) in /tmp/ccqKQGzN.o /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/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16): dangerous relocation: unsupported relocation I think I should be able to workaround this.
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.
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
Re: [Linaro-TCWG-CI] gcc-16-427-g86627faec10d: 11 regressions on arm
On Wed, 4 Jun 2025 at 02:50, wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find > some details below. > > In master-arm_eabi, after: > | commit gcc-16-427-g86627faec10d > | Author: Jonathan Wakely > | Date: Fri Apr 25 21:09:18 2025 +0100 > | > | libstdc++: Rewrite atomic builtin checks [PR70560] > | > | Currently the GLIBCXX_ENABLE_ATOMIC_BUILTINS macro checks for a > variety > | of __atomic built-ins for bool, short and int. If all those checks > pass, > | then it defines _GLIBCXX_ATOMIC_BUILTINS and uses the definitions from > | ... 80 lines of the commit log omitted. > > Produces 11 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 (test for excess > errors) > | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++26 (test for excess > errors) > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 (test for excess > errors) > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 (test for excess > errors) > | ... and 7 more > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc master-arm_eabi > *configure and test flags:* --target arm-eabi > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1595. > Please let us know if you have a fix. I've opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120567 for this. > > 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_gnu_embed_check_gcc--master-arm_eabi-build/1014/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_gnu_embed_check_gcc--master-arm_eabi-build/1014/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1014/artifact/artifacts/sumfiles/xfails.xfail > > Current build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1014/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1013/artifact/artifacts > > Instruction to reproduce the build : > https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1/86627faec10da53d7532805019e5296fcf15ac09/tcwg_gnu_embed_check_gcc/master-arm_eabi/reproduction_instructions.txt > > Full commit : > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=86627faec10da53d7532805019e5296fcf15ac09
Re: [Linaro-TCWG-CI] gcc-16-1247-gbdae7824cd9: 7 regressions on arm
On Fri, 6 Jun 2025 at 18:17, wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find > some details below. > > In gcc_check master-arm, after: > | commit gcc-16-1247-gbdae7824cd9 > | Author: Jonathan Wakely > | Date: Wed Jun 4 15:53:20 2025 +0100 > | > | libstdc++: Optimize std::counting_semaphore for futex path > | > | Rename __semaphore_base to __semaphore_impl, because it's not used as > a > | base class. Replace the three identical lambda expressions with a > named > | class, __semaphore_impl::_Available, which stores the most recent > | ... 27 lines of the commit log omitted. > > Produces 7 regressions: > | > | regressions.sum: > | Running g++:g++.dg/modules/modules.exp ... > | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess > errors) > | FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess > errors) > | FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess > errors) > | FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess > errors) > | ... and 3 more > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* none, autodetected on > armv8l-unknown-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1598. > Please let us know if you have a fix. It should be fixed at r16-1270-g7407891a3d7c17 > > 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-arm-build/3946/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-arm-build/3946/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/artifacts/sumfiles/xfails.xfail > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3945/artifact/artifacts > > Instruction to reproduce the build : > https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1/bdae7824cd9a9d27665bf1b82f60a761a9745a6a/tcwg_gcc_check/master-arm/reproduction_instructions.txt > > Full commit : See in git+ssh://linar...@gcc.gnu.org/git/gcc.git
