linaro-toolchain November 2023

linaro-toolchain@lists.linaro.org

15 participants
27 discussions

by Iain Sandoe

Hi So, I have a ci fail email, and it seems likely to be a valid complaint - but the reproduce instructions do not work on my platform (bash is not new enough) and also do not work on cfarm186 (../jenkins-scripts/jenkins-helpers.sh: line 1762: ts: command not found) For the record, the patch that is flagged as failing *was* tested on aarch64-linux-gnu (cfarm185) So, I am trying to figure out if the target is different, or some other configure argument. .. but I cannot work out the failing configure line at present - nor can I see a place to download the console log from the actual failing GCC build (which would presumably have that configure line). any help much appreciated. Iain

10 months, 1 week

Re: [Linaro-TCWG-CI] 7 patches in gcc: Failure on arm

by Lehua Ding

Hi, I received an error reported by CI for my patchs, I would like to ask how I have to reproduce it locally? I looked at the logs and didn't find the way how it compiles. Thanks in advance. On 2023/11/8 16:59, ci_notify(a)linaro.org 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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > In gcc_build master-arm after: > > | 7 patches in gcc > | Patchwork URL: https://patchwork.sourceware.org/patch/79366 > | ef64c12c9f0 lra: Support subreg live range track and conflict detect > | a871f544e2b lra: Apply live_subreg df_problem to lra pass > | 6437747d6f3 ira: Add all nregs >= 2 pseudos to tracke subreg list > | 1a2da1ad5f0 ira: Support subreg copy > | 4f8d8e764e0 ira: Support subreg live range track > | ... and 2 more patches in gcc > | ... applied on top of baseline commit: > | ca281a7b971 [i386] APX: Fix ICE due to movti postreload splitter [PR112394] > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:03:49 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2700:1: internal compiler error: Aborted > # 00:03:49 make[2]: *** [Makefile:505: _muldc3.o] Error 1 > # 00:03:49 make[1]: *** [Makefile:14486: all-target-libgcc] Error 2 > # 00:03:49 make: *** [Makefile:1056: all] Error 2 > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2700:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:41 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:72:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/libgcc2.c:2865:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > # 00:03:42 /home/tcwg-build/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libgcc/fixed-bit.c:143:1: internal compiler error: Aborted > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_build/master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/4076/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/1364/artifact/ar… -- Best, Lehua (RiVAI) lehua.ding(a)rivai.ai

10 months, 1 week

Re: [Linaro-TCWG-CI] gcc patch #80969: Failure on arm

by Rainer Orth

ci_notify(a)linaro.org writes: > 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-toolchain(a)lists.linaro.org mailing list, > Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain > developer on the usual project channel. > > In gcc_build master-arm after: > > | gcc patch https://patchwork.sourceware.org/patch/80969 > | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE> > | Date: Wed Nov 29 15:10:00 2023 +0100 > | > | libiberty: Disable hwcaps for sha1.o > | > | This patch > | > | commit bf4f40cc3195eb7b900bf5535cdba1ee51fdbb8e > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Nov 28 13:14:05 2023 +0100 > | ... 26 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 4c909c6ee38 In 'libgomp.c/target-simd-clone-{1,2,3}.c', restrict > | 'scan-offload-ipa-dump's to 'only_for_offload_target amdgcn-amdhsa' > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:02:15 gccgo: fatal error: Killed signal terminated program go1 > # 00:02:23 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:23 make[2]: *** [Makefile:1219: regex.o] Error 1 > # 00:02:23 make[1]: *** [Makefile:8370: all-libiberty] Error 2 > # 00:02:23 make: *** [Makefile:1057: all] Error 2 > # 00:01:06 gccgo: fatal error: Killed signal terminated program go1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:776: fdmatch.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:805: filedescriptor.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:837: fnmatch.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > # 00:02:10 make[2]: *** [Makefile:817: filename_cmp.o] Error 1 > # 00:02:10 gcc: error: @HWCAP_CFLAGS@: linker input file not found: No such > file or directory > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > 1 > > The configuration of this build is: > CI config tcwg_gcc_build master-arm > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/4887/artifac… > Reference build : > https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/1444/artifact/ar… > As is customary for gcc patches, this patch didn't include the generated files to simplify review. Thus, to test it in any meaningful way, one needs to run aclocal and autoconf before configuring/building. Not doing so just produces meaningless mails from the CI. Rainer

10 months, 1 week

Re: [Linaro-TCWG-CI] gcc-14-5810-gcff1fa6625d: FAIL: 3 regressions: 3 progressions on aarch64

by Christophe Lyon

Hi! On Fri, 24 Nov 2023 at 11:41, <ci_notify(a)linaro.org> 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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. > > In gcc_check master-aarch64 after: > > | commit gcc-14-5810-gcff1fa6625d > | Author: Nathaniel Shead <nathanieloshead(a)gmail.com> > | Date: Mon Nov 13 20:11:15 2023 +1100 > | > | c++: Support lambdas in static template member initialisers [PR107398] > | > | The testcase noted in the PR fails because the context of the lambda is > | not in namespace scope, but rather in class scope. This patch removes > | the assertion that the context must be a namespace and ensures that > | lambdas in class scope still get the correct merge_kind. > | > | ... 14 lines of the commit log omitted. > > FAIL: 3 regressions: 3 progressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18659) > FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18659) > FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18659) > > === Results Summary === > > progressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18649) > FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18649) > FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (internal compiler error: tree check: expected class 'type', have 'declaration' (template_decl) in get_originating_module_decl, at cp/module.cc:18649) > I think you can ignore this notification as a false positive: the error was already present before your patch, but at a different line location. Thanks, Christophe > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1245/artifac… . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1245/artifac… . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1245/artifac… . > > 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/1245/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1244/artifac… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/cff1fa6625d1273fcfaf473e436ba91826… > > Latest bug report status : https://linaro.atlassian.net/browse/GNU-1037 > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 3 regressions: 3 progressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1245/

12 months

[ACTIVITY] report week ending 24 Nov

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - Usual amount of code review and upstream pull request wrangling * QEMU-623 [Nested Virtualization Emulation] - Since the kernel side of KVM has decided that FEAT_NV alone is not worth supporting, I'm moving on to implementing FEAT_NV2 rather than trying to debug whether the behaviour I've been seeing is a bug in the kernel patchset's not-really-tested FEAT_NV handling. - I have a code-complete implementation of FEAT_NV2. Debugging next... -- PMM

1 year

RE: [Linaro-TCWG-CI] gcc-14-5794-g7a6a29c455e: FAIL: 1 regressions on aarch64

by Jiang, Haochen

Hi Jonathan, It also caused same regression on x86_64: https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078617.html Could you help verify that? Thx, Haochen > -----Original Message----- > From: Gcc-regression <gcc-regression- > bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via > Gcc-regression > Sent: Friday, November 24, 2023 6:31 AM > To: jwakely(a)redhat.com > Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org > Subject: [Linaro-TCWG-CI] gcc-14-5794-g7a6a29c455e: FAIL: 1 regressions on > aarch64 > > 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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg > channel, or ping your favourite Linaro toolchain developer on the usual project > channel. > > In gcc_check master-aarch64 after: > > | commit gcc-14-5794-g7a6a29c455e > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Tue Sep 19 13:23:13 2023 +0100 > | > | libstdc++: Define std::ranges::to for C++23 (P1206R7) [PR111055] > | > | This adds the std::ranges::to functions for C++23. The rest of P1206R7 > | is not yet implemented, i.e. the new constructors taking the > | std::from_range tag, and the new insert_range, assign_range, etc. > member > | functions. std::ranges::to works with the standard containers even > | without the new constructors, so this is useful immediately. > | ... 18 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++2b (test for excess > errors) > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/1240/artifact/artifacts/00-sumfiles/ . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/1240/artifact/artifacts/notify/ . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/1240/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/1240/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/1239/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/7a6a29c455e7755b501c0006e39beb4e56ec27 > 29/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/7a6a29c455e7755b501c0006e39beb4e56ec2729 > > Latest bug report status : https://linaro.atlassian.net/browse/GNU-1036 > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/7a6a29c455e7755b501c0006e39beb4e56ec27 > 29/tcwg_gcc_check/master-aarch64/details.txt > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1240/

1 year

RE: [Linaro-TCWG-CI] gcc-14-5628-g53ba8d66955: FAIL: 2 regressions on arm

by Jiang, Haochen

Hi Jan, The commit also caused similar regressions on x86_64: https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078575.html The ERROR part has been resolved on the current trunk while others haven't. Could you help verify that? Thx, Haochen > -----Original Message----- > From: Gcc-regression <gcc-regression- > bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via > Gcc-regression > Sent: Tuesday, November 21, 2023 8:01 AM > To: jh(a)suse.cz > Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org > Subject: [Linaro-TCWG-CI] gcc-14-5628-g53ba8d66955: FAIL: 2 regressions > on arm > > 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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg > channel, or ping your favourite Linaro toolchain developer on the usual project > channel. > > In gcc_check master-arm after: > > | commit gcc-14-5628-g53ba8d66955 > | Author: Jan Hubicka <jh(a)suse.cz> > | Date: Mon Nov 20 19:35:53 2023 +0100 > | > | inter-procedural value range propagation > | > | implement very basic propapgation of return value ranges from VRP > | pass. This helps std::vector's push_back since we work out value range of > | allocated block. This propagates only within single translation unit. I > hoped > | we will also do the propagation at WPA stage, but that needs more work > on > | ipa-cp side. > | ... 52 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/dg.exp ... > FAIL: gcc.dg/vla-1.c scan-tree-dump-times optimized " s=> i" 2 > > Running gcc:gcc.dg/tree-ssa/tree-ssa.exp ... > ERROR: gcc.dg/tree-ssa/return-value-range-1.c: 1: syntax error for " dg-do 1 > ling " > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1307/artifact/artifacts/00-sumfiles/ . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1307/artifact/artifacts/notify/ . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1307/artifact/artifacts/sumfiles/xfails.xfail . > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------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/1307/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1305/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/53ba8d669550d3a1f809048428b97ca607f95cf > 5/tcwg_gcc_check/master-arm/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/53ba8d669550d3a1f809048428b97ca607f95cf5 > > Latest bug report status : https://linaro.atlassian.net/browse/GNU-1025 > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 2 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/53ba8d669550d3a1f809048428b97ca607f95cf > 5/tcwg_gcc_check/master-arm/details.txt > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1307/

1 year

RE: [Linaro-TCWG-CI] gcc-14-5524-gc7f6537db94: FAIL: 6 regressions on arm

by Jiang, Haochen

Hi Jonathon, This patch also caused same regression on x86_64. https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078559.html (Not all the regressions are caused by this commit, don't be worried) Could you help verify that? Thx, Haochen > -----Original Message----- > From: Gcc-regression <gcc-regression- > bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via > Gcc-regression > Sent: Thursday, November 16, 2023 7:44 PM > To: jwakely(a)redhat.com > Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org > Subject: [Linaro-TCWG-CI] gcc-14-5524-gc7f6537db94: FAIL: 6 regressions on > arm > > 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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg > channel, or ping your favourite Linaro toolchain developer on the usual project > channel. > > In gcc_check master-arm after: > > | commit gcc-14-5524-gc7f6537db94 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Nov 15 23:02:34 2023 +0000 > | > | libstdc++: Implement std::out_ptr and std::inout_ptr for C++23 > [PR111667] > | > | This implements that changes from P1132R8, including optimized paths > for > | std::shared_ptr and std::unique_ptr. > | > | For std::shared_ptr we pre-allocate a new control block in the > | std::out_ptr_t constructor so that the destructor is non-throwing. This > | ... 47 lines of the commit log omitted. > > FAIL: 6 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (internal compiler > error: tree check: expected class 'type', have 'declaration' (template_decl) in > get_originating_module_decl, at cp/module.cc:18649) > FAIL: g++.dg/modules/xtreme-header-4_b.C -std=c++2b (test for excess > errors) > FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (internal compiler > error: tree check: expected class 'type', have 'declaration' (template_decl) in > get_originating_module_decl, at cp/module.cc:18649) > FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++2b (test for excess > errors) > FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (internal compiler > error: tree check: expected class 'type', have 'declaration' (template_decl) in > get_originating_module_decl, at cp/module.cc:18649) > FAIL: g++.dg/modules/xtreme-header_b.C -std=c++2b (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-arm- > build/1273/artifact/artifacts/00-sumfiles/ . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1273/artifact/artifacts/notify/ . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1273/artifact/artifacts/sumfiles/xfails.xfail . > > The configuration of this build is: > CI config tcwg_gcc_check/master-arm > > -----------------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/1273/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1272/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/c7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac/ > tcwg_gcc_check/master-arm/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/c7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac > > Latest bug report status : https://linaro.atlassian.net/browse/GNU-1014 > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 6 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/c7f6537db94f7c6320a5a8ecaa387c9b9ce1f0ac/ > tcwg_gcc_check/master-arm/details.txt > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1273/

1 year

RE: [Linaro-TCWG-CI] gcc-14-5310-g879cf9ff45d: FAIL: 6 regressions on aarch64

by Jiang, Haochen

Hi Brendan, This patch also caused same regression on x86_64. https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078479.html Could you help verify that? Thx, Haochen > -----Original Message----- > From: Gcc-regression <gcc-regression- > bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via > Gcc-regression > Sent: Friday, November 10, 2023 6:11 PM > To: jlaw(a)ventanamicro.com > Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org; > bshanks(a)codeweavers.com > Subject: [Linaro-TCWG-CI] gcc-14-5310-g879cf9ff45d: FAIL: 6 regressions on > aarch64 > > 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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg > channel, or ping your favourite Linaro toolchain developer on the usual project > channel. > > In gcc_check master-aarch64 after: > > | commit gcc-14-5310-g879cf9ff45d > | Author: Brendan Shanks <bshanks(a)codeweavers.com> > | Date: Thu Nov 9 21:01:07 2023 -0700 > | > | [PATCH v3] libiberty: Use posix_spawn in pex-unix when available. > | > | Hi, > | > | This patch implements pex_unix_exec_child using posix_spawn when > | available. > | > | ... 20 lines of the commit log omitted. > > FAIL: 6 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/modules/modules.exp ... > FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 at line 3 (test for errors, > line ) > FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test for excess errors) > FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2a at line 3 (test for errors, > line ) > FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2a (test for excess errors) > FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2b at line 3 (test for errors, > line ) > FAIL: g++.dg/modules/bad-mapper-1.C -std=c++2b (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/1159/artifact/artifacts/00-sumfiles/ . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/1159/artifact/artifacts/notify/ . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/1159/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/1159/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/1158/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/879cf9ff45d94065d89e24b71c6b27c7076ac51 > 8/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/879cf9ff45d94065d89e24b71c6b27c7076ac518 > > Latest bug report status : https://linaro.atlassian.net/browse/GNU-1000 > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 6 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/879cf9ff45d94065d89e24b71c6b27c7076ac51 > 8/tcwg_gcc_check/master-aarch64/details.txt > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1159/

1 year

RE: [Linaro-TCWG-CI] gcc-14-5679-g1d82fc2e682: FAIL: 1 regressions on arm

by Jiang, Haochen

Hi Jan, This patch also caused same issue on i386. https://gcc.gnu.org/pipermail/gcc-regression/2023-November/078590.html Could you help verify that? Thx, Haochen > -----Original Message----- > From: Gcc-regression <gcc-regression- > bounces+haochen.jiang=intel.com(a)gcc.gnu.org> On Behalf Of ci_notify--- via > Gcc-regression > Sent: Wednesday, November 22, 2023 4:20 PM > To: jh(a)suse.cz > Cc: ci_notify(a)linaro.org; gcc-regression(a)gcc.gnu.org > Subject: [Linaro-TCWG-CI] gcc-14-5679-g1d82fc2e682: FAIL: 1 regressions on > arm > > 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-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg > channel, or ping your favourite Linaro toolchain developer on the usual project > channel. > > In gcc_check master-arm after: > > | commit gcc-14-5679-g1d82fc2e682 > | Author: Jan Hubicka <jh(a)suse.cz> > | Date: Tue Nov 21 15:17:16 2023 +0100 > | > | optimize std::vector::push_back > | > | this patch speeds up the push_back at -O3 significantly by making the > | reallocation to be inlined by default. _M_realloc_insert is general > | insertion that takes iterator pointing to location where the value > | should be inserted. As such it contains code to move other entries > around > | that is quite large. > | ... 23 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: g++.dg/opt/pr110879.C -std=gnu++98 scan-tree-dump-not optimized > "=\\s*\\S*res_(?!\\S*_M_end_of_storage;)" > > === Results Summary === > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1318/artifact/artifacts/00-sumfiles/ . > The full lists of regressions and progressions are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1318/artifact/artifacts/notify/ . > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1318/artifact/artifacts/sumfiles/xfails.xfail . > > The configuration of this build is: > CI config tcwg_gcc_check master-arm > > -----------------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/1318/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm- > build/1317/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/1d82fc2e6824bf83159389729c31a942f7b91b0 > 4/tcwg_gcc_check/master-arm/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/1d82fc2e6824bf83159389729c31a942f7b91b04 > > Latest bug report status : https://linaro.atlassian.net/browse/GNU-1032 > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/1d82fc2e6824bf83159389729c31a942f7b91b0 > 4/tcwg_gcc_check/master-arm/details.txt > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1318/

1 year

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain November 2023