- linaro-toolchain - lists.linaro.org

[Linaro-TCWG-CI] glibc-2.40.9000-213-gb300078d97a: FAIL: 4 regressions on aarch64

by ci_notify＠linaro.org

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. 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-1357 , please let us know if you are looking at the problem and/or when you have a fix. In master-aarch64 after: | commit glibc-2.40.9000-213-gb300078d97a | Author: Florian Weimer <fweimer(a)redhat.com> | Date: Sat Sep 28 09:44:25 2024 +0200 | | Linux: Block signals around _Fork (bug 32215) | | This hides the inconsistent TCB state (missing robust mutex list) from | signal handlers. | | ... 1 lines of the commit log omitted. FAIL: 4 regressions regressions.sum: | === gdb tests === | | Running gdb:gdb.base/step-over-syscall.exp ... | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: find syscall insn in fork (timeout) | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: syscall number matches | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: find syscall insn in fork (timeout) | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: syscall number matches | | # "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_native_check_gdb--master-aarch64-build/1… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… The configuration of this build is: CI config tcwg_gnu_native_check_gdb master-aarch64 -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=b300078d97a6892cb2fa…

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-3899-g819098dc71f2: FAIL: 1 regressions: 1 improvements on aarch64

by Sam James

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. > > 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-1356 , 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-15-3899-g819098dc71f2 > | Author: Sam James <sam(a)gentoo.org> > | Date: Thu Sep 26 15:43:33 2024 +0100 > | > | testsuite: XFAIL gfortran.dg/initialization_25.f90 properly > | > | The test was disabled/XFAIL'd informally in r0-100012-gcdc6637d7c78ec, > | but r15-3890-g34bf6aa41ba539 didn't realize this, causing a FAIL. > | > | ... 7 lines of the commit log omitted. > > FAIL: 1 regressions: 1 improvements > Thanks, this is PR116858 and I'll handle it today or tomorrow at the latest. > regressions.sum: > | === gfortran tests === > | > | Running gfortran:gfortran.dg/dg.exp ... > | FAIL: gfortran.dg/initialization_25.f90 -O xfail *-*-* (test for errors, line 11) > | > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > improvements.sum: > | === gfortran tests === > | > | Running gfortran:gfortran.dg/dg.exp ... > | FAIL: gfortran.dg/initialization_25.f90 -O (test for errors, line 11) > | > | # "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_gcc_check--master-aarch64-build/2668/artifac… > 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/2668/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2668/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/2668/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2667/artifac… > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://github.com/gcc-mirror/gcc/commit/819098dc71f2079aedc15a904ab5f17f07…

1 year, 7 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-15-3607-g9a94c8ffdc8b: FAIL: 23 regressions: 22 improvements on master-thumb_m23_soft_eabi

by Richard Earnshaw (lists)

On 21/09/2024 08:49, 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. > > 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-1349 , please let us know if you are looking at the problem and/or when you have a fix. > > In arm-eabi cortex-m23 soft after: > > | commit gcc-15-3607-g9a94c8ffdc8b > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Thu Sep 12 14:24:55 2024 +0100 > | > | arm: testsuite: make use of -mcpu=unset/-march=unset > | > | This patch makes use of the new ability to unset the CPU or > | architecture flags on the command line to enable several more tests on > | Arm. It doesn't cover every case and it does enable some tests that > | now fail for different reasons when the tests are no-longer skipped; > | these were failing anyway for other testsuite configurations, so it's > | ... 22 lines of the commit log omitted. > > FAIL: 23 regressions: 22 improvements > > regressions.sum: > === gcc tests === > > Running gcc:gcc.target/arm/arm.exp ... > FAIL: gcc.target/arm/scd42-2.c scan-assembler mov[ \t].*272 > > Running gcc:gcc.target/arm/cmse/cmse.exp ... > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > ... and 19 more entries > > improvements.sum: > === gcc tests === > > Running gcc:gcc.target/arm/cmse/cmse.exp ... > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-6.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-6.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsls\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-6.c -march=armv8.1-m.main+fp -mthumb -O3 -g scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 > ... and 16 more entries I can't make any sense of this at all. After hours wasted trying to find the configuration information from the logs (it's there, but to the inexperienced user of your reports, it is buried far too deep), I'm still none-the-wiser. All I can see is that things like FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 have changed to FAIL: gcc.target/arm/cmse/mainline/8_1m/bitfield-4.c -mcpu=unset -march=armv8.1-m.main+fp -mthumb -O2 scan-assembler lsrs\t(r[3-9]|r10|fp|ip), \\1, #1.*blxns\t\\1 (ie that -mcpu=unset has been added to the test name). That's not a regression, it's a simple FAIL->FAIL R. > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > 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_m23_soft_e… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -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_m23_soft_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > 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/9a94c8ffdc8b554a2d95e0101e96830efe… > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-thumb_m23_soft_eabi > *** FAIL: 23 regressions: 22 improvements > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…

1 year, 7 months

2
2
0 0

Re: [Linaro-TCWG-CI] gcc patch #97787: Failure on aarch64

by David Malcolm

On Sat, 2024-09-21 at 04:30 +0000, 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. > > 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. > > In gcc_build master-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/97787 > | Author: David Malcolm <dmalcolm(a)redhat.com> > | Date: Fri Sep 20 19:05:46 2024 -0400 > | > | diagnostics: convert text hooks to use > diagnostic_text_output_format [PR116613] > | > | The diagnostic_starter and diagnostic_finalizer callbacks and > most of > | their support subroutines are only used by the "text" output > format. > | > | Emphasize this and reduce the binding with diagnostic_context > | by renaming the callbacks to add "_text" in their names, and > converting > | ... 264 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 2484ba167e1c libstdc++: fix C header include guards > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe gcc: > # FAILED > # First few build errors in logs: > # 00:06:02 /home/tcwg- > build/workspace/tcwg_gnu_4/abe/snapshots/gcc.git~master/gcc/diagnosti > c-format-sarif.cc:3130:8: error: ‘void > sarif_output_format::after_diagnostic(const diagnostic_info&)’ cannot > be overloaded with ‘void sarif_output_format::after_diagnostic(const > diagnostic_info&)’ > # 00:06:03 make[2]: *** [Makefile:1195: diagnostic-format-sarif.o] > Error 1 > # 00:06:03 make[1]: *** [Makefile:4701: all-gcc] Error 2 > # 00:06:03 make: *** [Makefile:1062: all] Error 2 This works for me, and I've been staring at the code and can't see the issue. Any ideas what the problem is? What stage 0 compiler are you using? Thanks Dave

1 year, 7 months

2
4
0 0

Re: [Linaro-TCWG-CI] gdb patch #97698: FAIL: 1 regressions: 1 improvements on arm

by Guinevere Larsen

I think some issue has happened in the CI. Both this and 2 patches I've sent to the mailing list (one that changes no code, only the SECURITY.txt file) say that I've introduced regressions, yet the relevant test only has "no file ID for <hex number>". Can you double check what's going on? -- Cheers, Guinevere Larsen She/Her/Hers On 9/23/24 5:18 AM, 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. > > 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. > > In gdb_check master-arm after: > > | gdb patch https://patchwork.sourceware.org/patch/97698 > | Author: Guinevere Larsen <blarsen(a)redhat.com> > | Date: Thu Sep 19 09:42:04 2024 -0300 > | > | gdb/testsuite: rework bp-cond-failure to not depend on inlining > | > | The test gdb.base/bp-cond-failure is implicitly expecting that the > | function foo will be inlined twice and gdb will be able to find 2 > | locations to place a breakpoint. When clang is used, gdb only finds > | one location which causes the test to fail. Since the test is not > | worried about handling breakpoints on inlined functions, but rather on > | ... 11 lines of the commit log omitted. > | ... applied on top of baseline commit: > | d3acf3d759d Rename tui_suppress_output > > FAIL: 1 regressions: 1 improvements > > regressions.sum: > === gdb tests === > > Running gdb:gdb.base/return.exp ... > ERROR: no fileid for 5a8f76db3a07 > > > improvements.sum: > === gdb tests === > > Running gdb:gdb.base/return.exp ... > ERROR: no fileid for a55c644d3a50 > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3013/artifac… > The full lists of regressions and improvements as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3013/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/3013/artifac… > > The configuration of this build is: > CI config tcwg_gdb_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_gdb_check--master-arm-precommit/3013/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/1786/artifact/ar… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 7 months

2
3
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-6434-ga861ed411a35: Failure on aarch64

by Nathan Chancellor

On Sat, Sep 21, 2024 at 09:39:09AM +0000, ci_notify(a)linaro.org wrote: > We track this report status in https://linaro.atlassian.net/browse/LLVM-1362 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-lts-defconfig after: > > | commit llvmorg-20-init-6434-ga861ed411a35 > | Author: Florian Hahn <flo(a)fhahn.com> > | Date: Fri Sep 20 11:22:03 2024 +0100 > | > | [VPlan] Add initial loop-invariant code motion transform. (#107894) > | > | Add initial transform to move out loop-invariant recipes. > | > | This also helps to fix a divergence between legacy and VPlan-based cost > | model due to legacy using ScalarEvolution::isLoopInvariant in some > | cases. > | ... 4 lines of the commit log omitted. Thanks for the report. I suspect this should be fixed by https://github.com/llvm/llvm-project/commit/bd8fe9972e3f17776e4e05e69e13ab8…, based on the fact that there is a similar report on the pull request upstream. Cheers, Nathan

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-3608-gc5009eb88791: FAIL: 4 regressions on arm

by Jason Merrill

On 9/12/24 9:13 PM, 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. > > 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-1342 , 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-3608-gc5009eb88791 > | Author: Jason Merrill <jason(a)redhat.com> > | Date: Tue Aug 27 13:15:16 2024 -0400 > | > | libcpp: adjust pedwarn handling > | > | Using cpp_pedwarning (CPP_W_PEDANTIC instead of if (CPP_PEDANTIC cpp_error > | lets users suppress these diagnostics with > | #pragma GCC diagnostic ignored "-Wpedantic". > | > | This patch changes all instances of the cpp_error (CPP_DL_PEDWARN to > | ... 44 lines of the commit log omitted. > > FAIL: 4 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: c-c++-common/pragma-diag-17.c -std=gnu++14 (test for excess errors) > FAIL: c-c++-common/pragma-diag-17.c -std=gnu++17 (test for excess errors) > FAIL: c-c++-common/pragma-diag-17.c -std=gnu++98 (test for excess errors) > === gcc tests === > > Running gcc:gcc.dg/dg.exp ... > FAIL: c-c++-common/pragma-diag-17.c -Wc++-compat (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/2697/artifact/ar… > 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/2697/artifact/ar… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2697/artifact/ar… > > 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/2697/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2696/artifact/ar… > > 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/c5009eb887910271ea35a857aa68941c72… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** FAIL: 4 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2697/artifact/ar… Curious, does this resolve the problems?

1 year, 7 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-15-3617-g4308c343b8e: FAIL: 4 regressions: 4 improvements on arm

by Alexandre Oliva

On Sep 17, 2024, ci_notify(a)linaro.org wrote: > regressions.sum: > FAIL: c-c++-common/analyzer/out-of-bounds-diagram-8.c -std=c++<XX> expected multiline pattern lines 20-35 > improvements.sum: > FAIL: c-c++-common/analyzer/out-of-bounds-diagram-8.c -std=c++<XX> expected multiline pattern lines 19-34 It's the same set of FAILs, but the line ranges got offset by 1 in the patch, and this seems to have confused your regression tester. Please mark this as all clear. Thanks for the report, -- Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer More tolerance and less prejudice are key for inclusion and diversity Excluding neuro-others for not behaving ""normal"" is *not* inclusive

1 year, 7 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-15-3572-g2801a49d114: FAIL: 6 regressions on master-thumb_m55_hard_eabi

by Christophe Lyon

Hi, On Fri, 20 Sept 2024 at 15:24, <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. > > 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-1347 , please let us know if you are looking at the problem and/or when you have a fix. > > In arm-eabi cortex-m55 hard after: > > | commit gcc-15-3572-g2801a49d114 > | Author: Marek Polacek <polacek(a)redhat.com> > | Date: Thu Aug 29 15:13:03 2024 -0400 > | > | c++: mutable temps in rodata [PR116369] > | > | Here we wrongly mark the reference temporary for g TREE_READONLY, > | so it's put in .rodata and so we can't modify its subobject even > | when the subobject is marked mutable. This is so since r9-869. > | r14-1785 fixed a similar problem, but not in set_up_extended_ref_temp. > | > | ... 10 lines of the commit log omitted. > > FAIL: 6 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: g++.dg/tree-ssa/initlist-opt7.C -std=c++11 (test for excess errors) > UNRESOLVED: g++.dg/tree-ssa/initlist-opt7.C -std=c++11 compilation failed to produce executable > FAIL: g++.dg/tree-ssa/initlist-opt7.C -std=c++17 (test for excess errors) > UNRESOLVED: g++.dg/tree-ssa/initlist-opt7.C -std=c++17 compilation failed to produce executable > FAIL: g++.dg/tree-ssa/initlist-opt7.C -std=c++26 (test for excess errors) > UNRESOLVED: g++.dg/tree-ssa/initlist-opt7.C -std=c++26 compilation failed to produce executable > The new tests introduced by this patch fail to link due a linker bug which has now been fixed. You can ignore this notification. Thanks, Christophe > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > 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_m55_hard_e… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard -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_m55_hard_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > 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/2801a49d1144bce5568b527d1972952ad3… > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-thumb_m55_hard_eabi > *** FAIL: 6 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e…

1 year, 7 months

1
0
0 0

Lots of failing tests on arm-unknown-eabi

by Mark Wielaard

Hi, ci_notify(a)linaro.org is sending test results to gcc-restresults(a)gcc.gnu.org but recently starting to fail so many tests that they don't get accepted anymore: From: ci_notify(a)linaro.org on Tue Sep 10 02:17:32 2024 Subject: Results for 15.0.0 20240906 (experimental) [master revision gcc-15-3512-ge8378231bb8] (GCC) testsuite on arm-unknown-eabi Cause: Message body is too big: 6548864 bytes with a limit of 1000 KB From: ci_notify(a)linaro.org on Tue Sep 10 05:28:38 2024 Subject: Results for 15.0.0 20240906 (experimental) [master revision gcc-15-3512-ge8378231bb88] (GCC) testsuite on arm-unknown-eabi Cause: Message body is too big: 6559111 bytes with a limit of 1000 KB From: ci_notify(a)linaro.org on Tue Sep 10 10:55:10 2024 Subject: Results for 15.0.0 20240906 (experimental) [master revision gcc-15-3512-ge8378231bb88] (GCC) testsuite on arm-unknown-eabi Cause: Message body is too big: 6548861 bytes with a limit of 1000 KB So that is 6.5MB of results. Almost all look like: FAIL: 17_intro/freestanding.cc -std=gnu++17 (test for excess errors) UNRESOLVED: 17_intro/freestanding.cc -std=gnu++17 compilation failed to produce executable Could someone take a look? It seems that the compiler is just crashing on every test. Thanks, Mark

1 year, 7 months

4
8
0 0

LLVM community bot issues

by Aaron Ballman

Hello! It seems one of the Linaro bots has been down for the last few weeks: https://lab.llvm.org/buildbot/#/builders/124 https://lab.llvm.org/buildbot/#/workers/88 Can you investigate what's going on? Thank you! ~Aaron

1 year, 7 months

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-15-3614-g9fe57e4879de: FAIL: 12 regressions on aarch64

by Jonathan Wakely

On Fri, 13 Sept 2024 at 07:09, <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. > > 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 <jwakely(a)redhat.com> > | 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/artifac… > 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/artifac… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/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/2595/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2594/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/9fe57e4879de93b6e3c7b4c226f42d5f3a… > > 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/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2595/artifac…

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-3532-g7cebc6384a0a: FAIL: 6 regressions: 6 improvements on master-thumb_m7_eabi

by Christophe Lyon

Hi Jason, On Thu, 12 Sept 2024 at 00:15, <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. > > 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-1339 , please let us know if you are looking at the problem and/or when you have a fix. > > In arm-eabi cortex-m7 hard after: > > | commit gcc-15-3532-g7cebc6384a0a > | Author: Jason Merrill <jason(a)redhat.com> > | Date: Fri Sep 6 15:28:53 2024 -0400 > | > | c++: exception spec and stdlib specialization > | > | We were silently accepting the pr65923.C specialization of std::swap with > | the wrong exception specification; it should be declared noexcept. Let's > | limit ignoring mismatch with system headers to extern "C" functions so we > | get a diagnostic for the C++ library. > | > | ... 18 lines of the commit log omitted. > > FAIL: 6 regressions: 6 improvements > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: g++.dg/cpp1z/aligned-new3.C -std=gnu++17 (test for excess errors) > UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=gnu++17 compilation failed to produce executable > FAIL: g++.dg/cpp1z/aligned-new3.C -std=gnu++20 (test for excess errors) > UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=gnu++20 compilation failed to produce executable > FAIL: g++.dg/cpp1z/aligned-new3.C -std=gnu++26 (test for excess errors) > UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=gnu++26 compilation failed to produce executable > > > improvements.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=c++20 compilation failed to produce executable > UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=c++26 compilation failed to produce executable > FAIL: g++.dg/cpp1z/aligned-new3.C -std=c++26 (test for excess errors) > UNRESOLVED: g++.dg/cpp1z/aligned-new3.C -std=c++17 compilation failed to produce executable > FAIL: g++.dg/cpp1z/aligned-new3.C -std=c++20 (test for excess errors) > FAIL: g++.dg/cpp1z/aligned-new3.C -std=c++17 (test for excess errors) This is not a regression, these tests used to fail with -std=c++XX and now they still fail with -std=gnuXX. I guess this is the effect of adding 'dg-options ""' ? And... the reason they fail to produce an executable is a recent patch of mine in the linker, which should now be fixed. Thanks, Christophe > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu… > 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_m7_eabi-bu… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu… > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv7e-m+fp.dp -mtune=cortex-m7 -mfloat-abi=hard -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_m7_eabi-bu… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu… > > 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/7cebc6384a0ad63d444029472a8ed1afe9… > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-thumb_m7_eabi > *** FAIL: 6 regressions: 6 improvements > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m7_eabi-bu…

1 year, 7 months

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-4274-ga77ccc81295: FAIL: 1 regressions on master-thumb_m33_eabi

by ci_notify＠linaro.org

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. 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-1341 , please let us know if you are looking at the problem and/or when you have a fix. In arm-eabi cortex-m33 hard after: | commit binutils-2_41-release-4274-ga77ccc81295 | Author: Christophe Lyon <christophe.lyon(a)linaro.org> | Date: Fri Sep 6 17:10:02 2024 +0000 | | arm: Handle undefweak with ST_BRANCH_UNKNOWN | | A previous patch made ld fail early on Thumb-only where branch_type is | ST_BRANCH_UNKNOWN. | | However, this fails erroneously when the target is undefweak: in that | case the branch should be replaced by a branch to the next instruction | ... 9 lines of the commit log omitted. FAIL: 1 regressions regressions.sum: === binutils tests === Running binutils:binutils-all/objcopy.exp ... FAIL: simple objcopy of executable You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_embed_check_binutils--master-thumb_m33_e… 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_binutils--master-thumb_m33_e… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_embed_check_binutils--master-thumb_m33_e… The configuration of this build is: CI config tcwg_gnu_embed_check_binutils arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -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_binutils--master-thumb_m33_e… Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_binutils--master-thumb_m33_e… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=a77ccc81295f4… List of configurations that regressed due to this commit : * tcwg_gnu_embed_check_binutils ** master-thumb_m33_eabi *** FAIL: 1 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_gnu_embed_check_binutils--master-thumb_m33_e…

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-3513-g964577c31df2: FAIL: 12 regressions on master-thumb_m3_softfp_eabi

by Christophe Lyon

Hi Jakub, On Tue, 10 Sept 2024 at 05:17, <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. > > 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-1338 , please let us know if you are looking at the problem and/or when you have a fix. > > In arm-eabi cortex-m3 softfp after: > > | commit gcc-15-3513-g964577c31df2 > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Fri Sep 6 13:50:47 2024 +0200 > | > | c++: Partially implement CWG 2867 - Order of initialization for structured bindings [PR115769] > | > | The following patch partially implements CWG 2867 > | - Order of initialization for structured bindings. > | The DR requires that initialization of e is sequenced before r_i and > | that r_i initialization is sequenced before r_j for j > i, we already do it > | that way, the former ordering is a necessity so that the get calls are > | ... 78 lines of the commit log omitted. > > FAIL: 12 regressions > > regressions.sum: > === g++ tests === > > Running g++:g++.dg/dg.exp ... > FAIL: g++.dg/DRs/dr2867-1.C -std=gnu++11 (test for excess errors) > UNRESOLVED: g++.dg/DRs/dr2867-1.C -std=gnu++11 compilation failed to produce executable > FAIL: g++.dg/DRs/dr2867-1.C -std=gnu++14 (test for excess errors) > UNRESOLVED: g++.dg/DRs/dr2867-1.C -std=gnu++14 compilation failed to produce executable > FAIL: g++.dg/DRs/dr2867-1.C -std=gnu++17 (test for excess errors) > UNRESOLVED: g++.dg/DRs/dr2867-1.C -std=gnu++17 compilation failed to produce executable > FAIL: g++.dg/DRs/dr2867-2.C -std=gnu++11 (test for excess errors) > ... and 6 more entries These errors in the new tests added by your patch are caused by a recent patch of mine in binutils, for which I have sent a fix proposal: https://sourceware.org/pipermail/binutils/2024-September/136677.html Thanks, Christophe > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_… > 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_m3_softfp_… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_… > > The configuration of this build is: > CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv7-m -mtune=cortex-m3 -mfloat-abi=softfp -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_m3_softfp_… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_… > > 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/964577c31df206d780d5cc7bc07189d44d… > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-thumb_m3_softfp_eabi > *** FAIL: 12 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] v6.10-12615-g08c2182cf0b47: Failure on aarch64

by Nathan Chancellor

On Mon, Sep 09, 2024 at 12:37:30PM +0000, 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. > > 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/LLVM-1343 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-next-allmodconfig after: > > | commit v6.10-12615-g08c2182cf0b47 > | Author: Florian Westphal <fw(a)strlen.de> > | Date: Tue Aug 27 15:37:32 2024 +0200 > | > | xfrm: policy: use recently added helper in more places > | > | No logical change intended. > | > | Signed-off-by: Florian Westphal <fw(a)strlen.de> > | Signed-off-by: Steffen Klassert <steffen.klassert(a)secunet.com> Thanks for the report, I'll ping my fix for this now: https://lore.kernel.org/all/20240829-xfrm-restore-dir-assign-xfrm_hash_rebu… Cheers, Nathan

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] gdb-15-branchpoint-893-gdcaa85e58c4: FAIL: 1 regressions on aarch64

by Andrew Burgess

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. > > 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-1334 , please let us know if you are looking at the problem and/or when you have a fix. > > In master-aarch64 after: > > | commit gdb-15-branchpoint-893-gdcaa85e58c4 > | Author: Andrew Burgess <aburgess(a)redhat.com> > | Date: Wed May 1 10:47:47 2024 +0100 > | > | gdb: reject inserting breakpoints between functions > | > | When debugging ROCm code, you might have something like this: > | > | __global__ void kernel () > | { > | ... > | ... 153 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === gdb tests === > > Running gdb:gdb.go/max-depth.exp ... > FAIL: gdb.go/max-depth.exp: gdb_breakpoint: set breakpoint at 38 There's something a little weird going on here, in the log I see: (gdb) run Starting program: /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/gdb-gdb.git~master/gdb/testsuite/outputs/gdb.go/max-depth/max-depth /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/gdb-gdb.git~master/gdb/testsuite/outputs/gdb.go/max-depth/max-depth: error while loading shared libraries: libgo.so.23: cannot open shared object file: No such file or directory [Inferior 1 (process 908724) exited with code 0177] (gdb) FAIL: gdb.go/max-depth.exp: runto: run to main.main break 38 No compiled code for line 38 in the current file. Make breakpoint pending on future shared library load? (y or [n]) n (gdb) FAIL: gdb.go/max-depth.exp: gdb_breakpoint: set breakpoint at 38 So it looks like the libgo.so.23 is missing from the test machine which stop the inferior from running. That said, I'd still expect GDB to place a b/p on line 38, and indeed, when run on my local machine the b/p is placed correctly. But also, I have the correct libraries in place so the inferior starts correctly... Is it possible to see the gdb.log for the working world before this patch was applied? It would be nice to confirm that despite failing to start the inferior, GDB did manage to place the b/p correctly before this patch. > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… I did wonder if the log file I wanted was one of these, but without better descriptions it's hard to know what all these log files actually are. Thanks, Andrew > The full lists of regressions and improvements as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… > > The configuration of this build is: > CI config tcwg_gnu_native_check_gdb master-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > > Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=dcaa85e58c4ef… > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_check_gdb > ** master-aarch64 > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > *** https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1…

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-3526-g113a6da9bf91: FAIL: 1 regressions on arm

by Thomas König

I cannot reproduce the failure. Please open a PR according to the GCC bug submission guidelines.

1 year, 7 months

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-4187-g31ed3a9d691: FAIL: 72074 regressions: 94 improvements on master-thumb_m33_hard_eabi

by ci_notify＠linaro.org

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. 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-1329 , please let us know if you are looking at the problem and/or when you have a fix. In arm-eabi cortex-m33 hard after: | commit binutils-2_41-release-4187-g31ed3a9d691 | Author: Christophe Lyon <christophe.lyon(a)linaro.org> | Date: Wed Jun 19 12:35:30 2024 +0000 | | arm: Do not insert stubs needing Arm code on Thumb-only cores. | | We recently fixed a bug in libgcc | (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115360) | where a symbol was missing a %function .type decoration. | | This meant the linker would silently pick the wrong type of 'farcall | ... 48 lines of the commit log omitted. FAIL: 72074 regressions: 94 improvements regressions.sum: === g++ tests === Running g++:g++.dg/analyzer/analyzer.exp ... FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++17 (test for excess errors) FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++26 (test for excess errors) FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++98 (test for excess errors) Running g++:g++.dg/compat/compat.exp ... FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o link FAIL: g++.dg/compat/abi/bitfield2 cp_compat_x_tst.o-cp_compat_y_tst.o link ... and 72156 more entries improvements.sum: === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++98 execution test FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++17 execution test FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++26 execution test FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++98 execution test FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++26 execution test FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++17 execution test === gcc tests === ... and 104 more entries You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e… 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_m33_hard_e… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e… The configuration of this build is: CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -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_m33_hard_e… Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=31ed3a9d69149… List of configurations that regressed due to this commit : * tcwg_gnu_embed_check_gcc ** master-thumb_m33_hard_eabi *** FAIL: 72074 regressions: 94 improvements *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] v6.11-rc1-143-g4e7795eda4459: Failure on aarch64

by Nathan Chancellor

On Wed, Sep 04, 2024 at 10:36:41PM +0000, 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. > > 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/LLVM-1339 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-next-allyesconfig after: > > | commit v6.11-rc1-143-g4e7795eda4459 > | Author: Kent Overstreet <kent.overstreet(a)linux.dev> > | Date: Sun Sep 1 18:08:25 2024 -0400 > | > | bcachefs: bch2_sb_member_alloc() > | > | refactoring > | > | Signed-off-by: Kent Overstreet <kent.overstreet(a)linux.dev> Thanks for the report, this should be fixed now: https://git.kernel.org/next/linux-next/c/da6e6a70084d99d522058bbef00b9cbe48… Cheers, Nathan

1 year, 7 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-4622-g16900d3b98e6: FAIL: 1 regressions on aarch64

by Ramkumar Ramachandra

Hi, Can I get a reduced .ll showing the regression, or some reduced steps for reproducing the bug? I suspect the bug is elsewhere, and not in the commit itself. Warm regards, Ram On Thu, Sep 5, 2024 at 3:39 AM <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. > > 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/LLVM-1340 , please let us know if you > are looking at the problem and/or when you have a fix. > > In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vla after: > > | commit llvmorg-20-init-4622-g16900d3b98e6 > | Author: Ramkumar Ramachandra <ramkumar.ramachandra(a)codasip.com> > | Date: Wed Sep 4 22:01:04 2024 +0100 > | > | LICM: hoist BO assoc when BinOp is in RHS (#107072) > | > | Extend hoistBOAssociation smoothly to handle the case when the > inner > | BinaryOperator is in the RHS of the outer BinaryOperator. This > completes > | the generalization of hoistBOAssociation, and the only limitation > after > | this patch is the fact that only Add and Mul are hoisted. > > FAIL: 1 regressions > > regressions.sum: > === test-suite tests === > > Running test-suite:Fujitsu/Fortran/0354 ... > FAIL: test-suite :: Fujitsu/Fortran/0354/Fujitsu-Fortran-0354_0334.test > > > You can find the failure logs in *.log.1.xz files in > - > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and > make commands are in > - > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > - > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > The configuration of this build is: > CI config tcwg_flang_test/main-aarch64-Ofast-sve_vla > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Reproduce last good and first bad builds: > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : > https://github.com/llvm/llvm-project/commit/16900d3b98e6c8fbdad4411a054e356… > > List of configurations that regressed due to this commit : > * tcwg_flang_test > ** main-aarch64-Ofast-sve_vla > *** FAIL: 1 regressions > *** > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…

1 year, 7 months

2
2
0 0

[Linaro-TCWG-CI] gcc-15-3256-g1c4b9826bd0: Failure on aarch64

by ci_notify＠linaro.org

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. 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-1324 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig after: | commit gcc-15-3256-g1c4b9826bd0 | Author: Filip Kastl <fkastl(a)suse.cz> | Date: Wed Aug 28 15:47:44 2024 +0200 | | gimple ssa: switchconv: Use __builtin_popcount and support more types in exp transform [PR116355] | | The gen_pow2p function generates (a & -a) == a as a fallback for | POPCOUNT (a) == 1. Not only is the bitmagic not equivalent to | POPCOUNT (a) == 1 but it also introduces UB (consider signed | a = INT_MIN). | | ... 43 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 9328 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 9330 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui… 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/1c4b9826bd0d5ac471543c68f097d80b19… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-lts-defconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…

1 year, 7 months

3
2
0 0

Re: [Linaro-TCWG-CI] 4 patches in glibc: FAIL: 1 regressions on arm

by Florian Weimer

* ci notify: > 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. > > 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. > > In glibc_check master-arm after: > > | 4 patches in glibc > | Patchwork URL: https://patchwork.sourceware.org/patch/96984 > | 11d52d986b elf: Reorder audit events in dlcose to match _dl_fini (bug 32066) > | 7b2cd1e545 elf: Call la_objclose for proxy link maps in _dl_fini (bug 32065) > | 0f79eb4a6f elf: Signal la_objopen for the proxy link map in dlmopen (bug 31985) > | f26a9b6323 elf: Always write audit log to elf/tst-audit23.out > | ... applied on top of baseline commit: > | 96d0bf98ca Add support/ code for checking file contents > > FAIL: 1 regressions > > regressions.sum: > === glibc tests === > > Running glibc:elf ... > FAIL: elf/tst-audit23 Adhemerval, does elf/tst-audit23.out now show more details? Thanks, Florian

1 year, 7 months

2
3
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-4274-g9ccf82543d50: FAIL: 8 regressions: 2 improvements on aarch64

by David Spickett

We saw problems with this on the bots, and https://github.com/llvm/llvm-project/commit/50a02e7c68f964c5d8338369746c849… fixed the issue there.

1 year, 8 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-3083-gbcb33b12370: FAIL: 1 regressions on master-thumb_m0_soft_eabi

by Bernd Edlinger

Hi, Can you check if this patch fixes the regressions? https://gcc.gnu.org/pipermail/gcc-patches/2024-August/661245.html Thanks Bernd. On 8/23/24 01:57, 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. > > 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-1318 , 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-3083-gbcb33b12370 > | Author: Bernd Edlinger <bernd.edlinger(a)hotmail.de> > | Date: Fri Aug 16 12:26:27 2024 +0200 > | > | Do not emit a redundant DW_TAG_lexical_block for inlined subroutines > | > | While this already works correctly for the case when an inlined > | subroutine contains only one subrange, a redundant DW_TAG_lexical_block > | is still emitted when the subroutine has multiple blocks. > | > | Fixes: ac02e5b75451 ("re PR debug/37801 (DWARF output for inlined functions > | ... 11 lines of the commit log omitted. > > FAIL: 1 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/debug/dwarf2/dwarf2.exp ... > FAIL: gcc.dg/debug/dwarf2/inline7.c scan-assembler-times DW_AT_ranges 2 > > > 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_soft_ea… > 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_soft_ea… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_soft_ea… > > 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_soft_ea… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_soft_ea… > > 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/bcb33b1237042e9540a905d9de19219f87… > > List of configurations that regressed due to this commit : > * tcwg_gnu_embed_check_gcc > ** master-thumb_m0_soft_eabi > *** FAIL: 1 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_soft_ea…

1 year, 8 months

1
0
0 0

RE: [Linaro-TCWG-CI] gcc-15-3087-gb07f8a30115: FAIL: 2 regressions on aarch64

by Andrew Pinski (QUIC)

> -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: Thursday, August 22, 2024 10:30 AM > To: rguenth(a)gcc.gnu.org > Cc: gcc-regression(a)gcc.gnu.org; Andrew Pinski (QUIC) > <quic_apinski(a)quicinc.com> > Subject: [Linaro-TCWG-CI] gcc-15-3087-gb07f8a30115: FAIL: 2 > 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. > > 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-1317 , please let us > know if you are looking at the problem and/or when you have > a fix. I have filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116463 for the failure (which was a missed optimization even before the patch; the detection of vector complex multiply is very sensitive in changes to the IR differences). Thanks, Andrew Pinski > > In gcc_check master-aarch64 after: > > | commit gcc-15-3087-gb07f8a30115 > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Wed Aug 21 17:41:38 2024 -0700 > | > | fold: Fix `a * 1j` if a has side effects [PR116454] > | > | The problem here was a missing save_expr around arg0 > since > | it is used twice, once in REALPART_EXPR and once in > IMAGPART_EXPR. > | Thia adds the save_expr and reformats the code slightly > so it is a > | little easier to understand. It excludes the case when arg0 > is > | a COMPLEX_EXPR since in that case we'll end up with the > distinct > | ... 19 lines of the commit log omitted. > > FAIL: 2 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.dg/vect/complex/complex.exp ... > FAIL: gcc.dg/vect/complex/fast-math-complex-mls-double.c > scan-tree-dump vect "Found COMPLEX_FMA" > FAIL: gcc.dg/vect/complex/fast-math-complex-mls-float.c > scan-tree-dump vect "Found COMPLEX_FMA" > > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/2486/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/2486/artifact/artifacts/notify/ > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64- > build/2486/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/2486/artifact/artifacts > Reference build : https://ci.linaro.org/job/tcwg_gcc_check-- > master-aarch64-build/2485/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/b07f8a301158e53717b8688cc8ea > 430b6f02574c/tcwg_gcc_check/master- > aarch64/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/b07f8a301158e53717b8688cc8ea430b6f0 > 2574c > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-aarch64 > *** FAIL: 2 regressions > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/b07f8a301158e53717b8688cc8ea > 430b6f02574c/tcwg_gcc_check/master-aarch64/details.txt > *** https://ci.linaro.org/job/tcwg_gcc_check--master- > aarch64-build/2486/artifact/artifacts

1 year, 8 months

1
0
0 0

RE: [Linaro-TCWG-CI] gcc-15-2986-gcd2f394418b: Failure on aarch64

by Andrew Pinski (QUIC)

This is already recorded as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116409 . I am about to submit a v2 of the patch to fix this too. > -----Original Message----- > From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> > Sent: Tuesday, August 20, 2024 8:34 AM > To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com> > Cc: gcc-regression(a)gcc.gnu.org > Subject: [Linaro-TCWG-CI] gcc-15-2986-gcd2f394418b: Failure > 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. > > 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-1316 , please let us > know if you are looking at the problem and/or when you have > a fix. > > In master-aarch64 after: > > | commit gcc-15-2986-gcd2f394418b > | Author: Andrew Pinski <quic_apinski(a)quicinc.com> > | Date: Sat Apr 20 00:13:12 2024 -0700 > | > | PHIOPT: move factor_out_conditional_operation over to > use gimple_match_op > | > | To start working on more with expressions with more > than one operand, converting > | over to use gimple_match_op is needed. > | The added side-effect here is > factor_out_conditional_operation can now support > | builtins/internal calls that has one operand without any > extra code added. > | > | ... 20 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe binutils: > 1 > # build_abe gcc: > 2 > # build_abe linux: > 4 > # build_abe glibc: > # FAILED > # build_abe gdb: > # First few build errors in logs: > # 00:02:13 ../sysdeps/ieee754/dbl-64/e_hypot.c:146:1: > internal compiler error: in factor_out_conditional_operation, > at tree-ssa-phiopt.cc:407 # 00:02:13 make[2]: *** > [/home/tcwg- > buildslave/workspace/tcwg_gnu_2/abe/builds/aarch64- > unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc- > glibc.git~master/sysd-rules:553: /home/tcwg- > buildslave/workspace/tcwg_gnu_2/abe/builds/aarch64- > unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc- > glibc.git~master/math/e_hypot.o] Error 1 # 00:02:13 make[1]: > *** [Makefile:484: math/others] Error 2 # 00:02:13 make: *** > [Makefile:9: all] Error 2 > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe binutils: > 1 > # build_abe gcc: > 2 > # build_abe linux: > 4 > # build_abe glibc: > 5 > # build_abe gdb: > 6 > > The configuration of this build is: > CI config tcwg_gnu_native_build master-aarch64 > > -----------------8<--------------------------8<--------------------------8<--- > ----------------------- > The information below can be used to reproduce a debug > environment: > > Current build : > https://ci.linaro.org/job/tcwg_gnu_native_build--master- > aarch64-build/747/artifact/artifacts > Reference build : > https://ci.linaro.org/job/tcwg_gnu_native_build--master- > aarch64-build/746/artifact/artifacts > > Reproduce last good and first bad builds: https://git- > us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/cd2f394418be0cc15d05c97ed725 > 67f2f5e15172/tcwg_gnu_native_build/master- > aarch64/reproduction_instructions.txt > > Full commit : https://github.com/gcc- > mirror/gcc/commit/cd2f394418be0cc15d05c97ed72567f2f5e1 > 5172 > > List of configurations that regressed due to this commit : > * tcwg_gnu_native_build > ** master-aarch64 > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting- > commits.git/plain/gcc/sha1/cd2f394418be0cc15d05c97ed725 > 67f2f5e15172/tcwg_gnu_native_build/master- > aarch64/details.txt > *** https://ci.linaro.org/job/tcwg_gnu_native_build--master- > aarch64-build/747/artifact/artifacts

1 year, 8 months

1
0
0 0

Fwd: ☠ Buildbot (LLVM Buildbot): clang-aarch64-sve-vls-2stage - failed test (failure) (main)

by David Blaikie

---------- Forwarded message --------- From: David Blaikie <dblaikie(a)gmail.com> Date: Thu, Jul 25, 2024 at 6:43 PM Subject: Re: ☠ Buildbot (LLVM Buildbot): clang-aarch64-sve-vls-2stage - failed test (failure) (main) To: <llvm.buildmaster(a)lab.llvm.org> Cc: <llvm.buildmaster(a)lab.llvm.org> This bot seems to be sending fail-mail when it's already red. My understanding was that fail mail only went out on green->red transitions. Is that understanding incorrect? Should this be reconfigured to match that understanding/not send fail mail when it's already red? On Thu, Jul 25, 2024 at 4:10 PM <llvm.buildmaster(a)lab.llvm.org> wrote: > The Buildbot has detected a failed build on builder > clang-aarch64-sve-vls-2stage while building clang. > > Full details are available at: > https://lab.llvm.org/buildbot/#/builders/4/builds/943 > > Worker for this Build: linaro-g3-02 > Blamelist: > David Blaikie <dblaikie(a)gmail.com> > > BUILD FAILED: failed test (failure) > > Step 18 (test-suite) failure: test (failure) > ... > [ 24%] Built target > gfortran-regression-execute-regression__internal_readwrite_1_f90 > cd > /home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Fortran/gfortran/regression > && > /home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/stage2.install/bin/llvm-size > --format=sysv > /home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Fortran/gfortran/regression/gfortran-regression-execute-regression__internal_readwrite_4_f90 > > > /home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Fortran/gfortran/regression/gfortran-regression-execute-regression__internal_readwrite_4_f90.size > make[2]: Leaving directory > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build' > [ 24%] Built target > gfortran-regression-execute-regression__internal_readwrite_4_f90 > make[1]: Leaving directory > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build' > make: *** [Makefile:136: all] Error 2 > 2024-07-25 23:09:27 INFO: Testing... > 2024-07-25 23:09:27 INFO: Execute: > /home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/stage1/bin/llvm-lit > -v -j 32 > /home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build > -o > /home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/outputqee5waec.json > -- Testing: 9770 tests, 32 workers -- > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_1026.test (1 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_1026.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_1026' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_1028.test (2 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_1028.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_1028' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_367.test (3 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_367.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_367' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_40.test (4 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_40.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_40' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_366.test (5 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_366.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_366' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_add_1030.test (6 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_add_1030.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_add_1030' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_699.test (7 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_699.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_699' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_368.test (8 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_368.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_368' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_add_1031.test (9 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_add_1031.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_add_1031' > is missing > ******************** > NOEXE: test-suite :: Bitcode/simd_ops/simd_ops_test_op_abs_39.test (10 of > 9770) > ******************** TEST 'test-suite :: > Bitcode/simd_ops/simd_ops_test_op_abs_39.test' FAILED ******************** > Executable > '/home/tcwg-buildbot/worker/clang-aarch64-sve-vls-2stage/test/sandbox/build/Bitcode/simd_ops/simd_ops_test_op_abs_39' > is missing > ******************** > > Sincerely, > LLVM Buildbot > >

1 year, 8 months

2
6
0 0

[Linaro-TCWG-CI] binutils-2_41-release-3996-g6ae8a30d44f: Failure on aarch64

by ci_notify＠linaro.org

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. 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-1312 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig after: | commit binutils-2_41-release-3996-g6ae8a30d44f | Author: Jan Beulich <jbeulich(a)suse.com> | Date: Fri Aug 9 11:59:31 2024 +0200 | | gas: have scrubber retain more whitespace | | According to the description of the state machine, the expectation | appears to be that (leaving aside labels) any insn mnemonic or | directive would be followed by a comma separated list of operands. That | may have been true very long ago, but the latest with the advent of more | elaborate macros this isn't rhe case anymore. Neither macro parameters | ... 26 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 8104 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 9328 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=6ae8a30d44f01… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-lts-defconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…

1 year, 8 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.40.9000-60-g07972839108: FAIL: 18 regressions on arm

by ci_notify＠linaro.org

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. 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-1309 , please let us know if you are looking at the problem and/or when you have a fix. In master-arm after: | commit glibc-2.40.9000-60-g07972839108 | Author: Paul Zimmermann <Paul.Zimmermann(a)inria.fr> | Date: Thu Jul 25 16:38:08 2024 +0200 | | added inputs giving large errors on x86_64 for new C23 functions | | These functions are exp10m1, exp2m1, log10p1, log2p1. | Also regenerated ulps on x86_64. | | For each format, there are 4 values, one for each rounding mode. | (For the intel96 format, there are 8 values, 4 for Intel hardware, | ... 3 lines of the commit log omitted. FAIL: 18 regressions regressions.sum: === glibc tests === Running glibc:math ... FAIL: math/test-double-exp10m1 FAIL: math/test-double-exp2m1 FAIL: math/test-double-log10p1 FAIL: math/test-float-exp10m1 FAIL: math/test-float-exp2m1 FAIL: math/test-float-log10p1 FAIL: math/test-float32-exp10m1 ... and 12 more entries You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/799… The full lists of regressions and improvements as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/799… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/799… The configuration of this build is: CI config tcwg_gnu_native_check_glibc master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/799… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/797… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=07972839108495245d8b… List of configurations that regressed due to this commit : * tcwg_gnu_native_check_glibc ** master-arm *** FAIL: 18 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/799…

1 year, 8 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-1360-ga42e515e3a9f: Failure on aarch64

by Maxim Kuvyrkov

Hi Julian, Your patch below breaks Flang build [on aarch64]. Would you please investigate? The interesting log is at https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/174/artifact… . Thanks! -- Maxim Kuvyrkov https://www.linaro.org > On Aug 5, 2024, at 16:56, 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. > > 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/LLVM-1306 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_flang_build/main-aarch64 after: > > | commit llvmorg-20-init-1360-ga42e515e3a9f > | Author: Julian Brown <julian.brown(a)amd.com> > | Date: Mon Aug 5 12:37:07 2024 +0100 > | > | [OpenMP] OpenMP 5.1 "assume" directive parsing support (#92731) > | > | This is a minimal patch to support parsing for "omp assume" directives. > | These are meant to be hints to a compiler's optimisers: as such, it is > | legitimate (if not very useful) to ignore them. The patch builds on top > | of the existing support for "omp assumes" directives (note spelling!). > | > | ... 8 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_llvm -- clang;lld;flang;openmp;clang-tools-extra : > # FAILED > > From > # reset_artifacts: > -10 > # true: > 0 > # build_llvm -- clang;lld;flang;openmp;clang-tools-extra : > 1 > > The configuration of this build is: > CI config tcwg_flang_build/main-aarch64 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/174/artifact… > Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/172/artifact… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/a42e515e3a9f3bb4e44389c097b8910… > > List of configurations that regressed due to this commit : > * tcwg_flang_build > ** main-aarch64 > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/174/artifact…

1 year, 8 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-2414-g2d105efd6f60: FAIL: 3 regressions on aarch64

by Sam James

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. > > 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-1305 , 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-15-2414-g2d105efd6f60 > | Author: Sam James <sam(a)gentoo.org> > | Date: Tue Jul 30 17:10:01 2024 +0100 > | > | testsuite: fix whitespace in dg-do assemble directive > | > | * gcc.target/aarch64/simd/vmmla.c: Fix whitespace in dg directive. > > FAIL: 3 regressions > > regressions.sum: > === gcc tests === > > Running gcc:gcc.target/aarch64/simd/simd.exp ... > UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\tsmmla\\tv[0-9]+.4s, v[0-9]+.16b, v[0-9]+.16b 1 > UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\tummla\\tv[0-9]+.4s, v[0-9]+.16b, v[0-9]+.16b 1 > UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\tusmmla\\tv[0-9]+.4s, v[0-9]+.16b, v[0-9]+.16b 1 > [...] Thanks. The test has been broken since it was added. Filed https://gcc.gnu.org/PR116207.

1 year, 8 months

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-943-g366eade911b5: FAIL: 7 regressions: 7 improvements on aarch64

by Maxim Kuvyrkov

Hi Leandro, Our Flang CI is running in test mode, and it already catches regressions! > On Aug 1, 2024, at 01:27, 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. > > 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/LLVM-1300 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld after: > > | commit llvmorg-20-init-943-g366eade911b5 > | Author: Leandro Lupori <leandro.lupori(a)linaro.org> > | Date: Wed Jul 31 14:39:06 2024 -0300 > | > | [flang][OpenMP] Reland Fix copyprivate semantic checks (#95799) (#101009) > | > | There are some cases in which variables used in OpenMP constructs > | are predetermined as private. The semantic checks for copyprivate > | were not handling those cases. > | > | Besides that, shared symbols were not being properly represented > | ... 9 lines of the commit log omitted. > > FAIL: 7 regressions: 7 improvements > > regressions.sum: > === test-suite tests === > > Running test-suite:Fujitsu/Fortran/0141 ... > FAIL: test-suite :: Fujitsu/Fortran/0141/Fujitsu-Fortran-0141_0019.test This means that after your patch the test that could not compile before, now compiles, but fails to run correctly. This is an improvement. > > Running test-suite:Fujitsu/Fortran/0153 ... > NOEXE: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0234.test > NOEXE: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0235.test > NOEXE: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0237.test These tests go the other way -- they used to fail at runtime before, but now they fail to compile. > > ... and 5 more entries > > improvements.sum: > === test-suite tests === > > Running test-suite:Fujitsu/Fortran/0141 ... > NOEXE: test-suite :: Fujitsu/Fortran/0141/Fujitsu-Fortran-0141_0019.test > > Running test-suite:Fujitsu/Fortran/0153 ... > FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0237.test > FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0234.test > FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0235.test > > ... and 5 more entries Please investigate, and let me know if you need any help in reproducing or troubleshooting these. Thanks! -- Maxim Kuvyrkov https://www.linaro.org > > You can find the failure logs in *.log.1.xz files in > - https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The full lists of regressions and improvements as well as configure and make commands are in > - https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The list of [ignored] baseline and flaky failures are in > - https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > The configuration of this build is: > CI config tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/366eade911b54878c9cc1835d2544fb… > > List of configurations that regressed due to this commit : > * tcwg_flang_test > ** main-aarch64-Ofast-sve_vls-lto-lld > *** FAIL: 7 regressions: 7 improvements > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…

1 year, 9 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #94612: Failure on aarch64

by Tobias Burnus

Hi all, what should I do with this – I have no idea what artifacts are nor is it clear to me when looking at the webpage. Tobias 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. > > 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. > > In gcc_check master-aarch64 after: > > | gcc patch https://patchwork.sourceware.org/patch/94612 > | Author: Tobias Burnus <tburnus(a)baylibre.com> > | Date: Fri Jul 26 20:05:43 2024 +0200 > | > | libgomp: Fix declare target link with offset array-section mapping [PR116107] > | > | The main idea of 'link' is to permit putting only a subset of a > | huge array on the device. Well, in order to make this work properly, > | it requires that one can map an array section, which does not > | start with the first element. > | > | ... 28 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 6d79d53eed8 Match: Support .SAT_SUB with IMM op for form 1-4 > > Results changed to > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > # 2 regressions > > From > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > > 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-precommit/7257/art… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2370/artifac… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 year, 9 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-15-2233-g8d1af8f904a: Failure on arm

by Maxim Kuvyrkov

Hi Andi, The regression is ... === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: c-c++-common/musttail12.c -std=c++14 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++17 (test for excess errors) FAIL: c-c++-common/musttail12.c -std=c++20 (test for excess errors) FAIL: g++.dg/musttail6.C (test for excess errors) It wasn't included in the report due to typo in the scripts. Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > On Jul 26, 2024, at 19:38, 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. > > 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-1299 , 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-2233-g8d1af8f904a > | Author: Andi Kleen <ak(a)linux.intel.com> > | Date: Tue Jan 23 23:54:56 2024 -0800 > | > | Add tests for C/C++ musttail attributes > | > | Some adopted from the existing C musttail plugin tests. > | Also extends the ability to query the sibcall capabilities of the > | target. > | > | gcc/testsuite/ChangeLog: > | ... 16 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > # 4 regressions > > From > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > > 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/2460/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2459/artifact/ar… > > 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/8d1af8f904a0c08656d976cbf8ca56dba3… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2460/artifact/ar…

1 year, 9 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-15-2362-ga9e9f772c748: Failure on arm

by Maxim Kuvyrkov

Hi Jason, For this one the regressions are: === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++20 (test for excess errors) FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++23 (test for excess errors) FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++26 (test for excess errors) -- Maxim Kuvyrkov https://www.linaro.org > On Jul 28, 2024, at 09:28, 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. > > 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-1301 , 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-2362-ga9e9f772c748 > | Author: Jason Merrill <jason(a)redhat.com> > | Date: Fri Jul 26 17:20:18 2024 -0400 > | > | c++: consteval propagation and templates [PR115986] > | > | Here the call to e() makes us decide to check d() for escalation at EOF, but > | while checking it we try to fold_immediate 0_c, and get confused by the > | template trees. Let's not mess with escalation for function templates. > | > | PR c++/115986 > | ... 9 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > # 3 regressions > > From > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > > 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/2472/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2471/artifact/ar… > > 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/a9e9f772c7488ac0c09dd92f28890bdab9… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2472/artifact/ar…

1 year, 9 months

1
0
0 0

[Linaro-TCWG-CI] llvmorg-20-init-488-g65361ff80c18: FAIL: 2 regressions on aarch64

by ci_notify＠linaro.org

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. 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/LLVM-1291 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_flang_test/main-aarch64-O3-sve_vla after: | commit llvmorg-20-init-488-g65361ff80c18 | Author: Christudasan Devadasan <christudasan.devadasan(a)amd.com> | Date: Fri Jul 26 20:03:45 2024 +0530 | | [AMDGPU] Use SubtargetPredicate instead of OtherPredicates for subtarget predication. (#100715) FAIL: 2 regressions regressions.sum: === test-suite tests === Running test-suite:Fujitsu/Fortran/0291 ... FAIL: test-suite :: Fujitsu/Fortran/0291/Fujitsu-Fortran-0291_0008.test Running test-suite:Fujitsu/Fortran/0338 ... FAIL: test-suite :: Fujitsu/Fortran/0338/Fujitsu-Fortran-0338_0061.test You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-sve_vla-build/8/… The full lists of regressions and improvements as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-sve_vla-build/8/… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-sve_vla-build/8/… The configuration of this build is: CI config tcwg_flang_test/main-aarch64-O3-sve_vla -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-sve_vla-build/8/… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-sve_vla-build/5/… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/65361ff80c18b5920eb45091ff39c1d… List of configurations that regressed due to this commit : * tcwg_flang_test ** main-aarch64-O3-sve_vla *** FAIL: 2 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… *** https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-sve_vla-build/8/…

1 year, 9 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-15-2360-gdab0f35fcb4d: Failure on arm

by Maxim Kuvyrkov

Hi Jason, The regression is ... === g++ tests === Running g++:g++.dg/dg.exp ... FAIL: g++.dg/abi/arm_rtti1.C -std=gnu++26 scan-assembler _ZNKSt9type_infoeqERKS_ It wasn't included in the report due to typo in the scripts. Kind regards, -- Maxim Kuvyrkov https://www.linaro.org > On Jul 28, 2024, at 05:55, 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. > > 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-1300 , 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-2360-gdab0f35fcb4d > | Author: Jason Merrill <jason(a)redhat.com> > | Date: Fri Jul 26 15:10:50 2024 -0400 > | > | c++: improve C++ testsuite default versions > | > | I wanted to add more cases to the setting of std_list in g++-dg.exp, but > | didn't want to do a full scan through the file for each case. So this patch > | improves that in two ways: first, by extracting all interesting lines on a > | single pass; second, by generating the list more flexibly: now we test every > | version mentioned explicitly in the testcase, plus a few more if fewer than > | ... 12 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > # 1 regressions > > From > # reset_artifacts: > -10 > # build_abe gcc: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gcc --: > 0 > > 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/2468/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2466/artifact/ar… > > 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/dab0f35fcb4dd3ba584422013096c4ebc6… > > List of configurations that regressed due to this commit : > * tcwg_gcc_check > ** master-arm > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2468/artifact/ar…

1 year, 9 months

1
0
0 0

Re: [Linaro-TCWG-CI] 2 patches in gdb: Failure on aarch64

by Simon Marchi

On 2024-07-27 03:34, 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. > > 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. > > In gdb_check master-aarch64 after: > > | 2 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/94605 > | 9aca4cc6ec5 gdb: pass inferior to gdbarch_update_p > | f3b21ad781e gdb: pass inferior to target_current_description > | ... applied on top of baseline commit: > | ced7ecee432 Automatic date update in version.in > > Results changed to > # reset_artifacts: > -10 > # build_abe gdb -- --prefix /usr --disable install: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1: > 0 > # 1 regressions > > From > # reset_artifacts: > -10 > # build_abe gdb -- --prefix /usr --disable install: > -2 > # build_abe dejagnu: > -1 > # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1: > 0 > > The configuration of this build is: > CI config tcwg_gdb_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_gdb_check--master-aarch64-precommit/2974/art… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/1474/artifac… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. Hello, Could you help me understand what failed? Simon

1 year, 9 months

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-19-init-18145-g1f6f97e2b64a: Failure on aarch64

by Nathan Chancellor

On Mon, Jul 22, 2024 at 02:12:58PM +0000, 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. > > 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/LLVM-1287 , please let us know if you are looking at the problem and/or when you have a fix. > > In CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig after: > > | commit llvmorg-19-init-18145-g1f6f97e2b64a > | Author: Bill Wendling <5993918+bwendling(a)users.noreply.github.com> > | Date: Thu Jul 18 22:11:56 2024 +0000 > | > | [Clang] Loop over FieldDecls instead of all Decls (#99574) > | > | Only FieldDecls are important when determining GEP indices. A struct > | defined within another struct has the same semantics as if it were > | defined outside of the struct. So there's no need to look into > | RecordDecls that aren't a field. > | > | ... 4 lines of the commit log omitted. > > Results changed to > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22903 > > From > # reset_artifacts: > -10 > # build_abe binutils: > -9 > # build_kernel_llvm: > -5 > # build_abe qemu: > -2 > # linux_n_obj: > 22904 > > The configuration of this build is: > CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig > > -----------------8<--------------------------8<--------------------------8<-------------------------- > The information below can be used to reproduce a debug environment: > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon… > > Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/1f6f97e2b64a9c4c51712d32b53e07d… > > List of configurations that regressed due to this commit : > * tcwg_kernel > ** llvm-master-aarch64-stable-allyesconfig > *** Failure > *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon… This should be fixed with https://github.com/llvm/llvm-project/commit/6db5f4fd2a287de9d20adc7a44cfcc6…. Cheers, Nathan

1 year, 9 months

1
0
0 0

[Linaro-TCWG-CI] gcc-15-2192-g0c5c0c959c2e: Failure on aarch64

by ci_notify＠linaro.org

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. 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-1297 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-aarch64-mainline-allnoconfig after: | commit gcc-15-2192-g0c5c0c959c2e | Author: Tamar Christina <tamar.christina(a)arm.com> | Date: Mon Jul 22 10:28:19 2024 +0100 | | AArch64: implement TARGET_VECTORIZE_CONDITIONAL_OPERATION_IS_EXPENSIVE [PR115531]. | | This implements the new target hook indicating that for AArch64 when possible | we prefer masked operations for any type vs doing LOAD + SELECT or | SELECT + STORE. | | Thanks, | ... 16 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 662 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 669 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-mainline-allnoconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon… 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/0c5c0c959c2e592b84739f19ca771fa69e… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-mainline-allnoconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…

1 year, 9 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.40.9000-2-g4dc22baa84b: FAIL: 6 regressions on arm

by ci_notify＠linaro.org

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. 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-1295 , please let us know if you are looking at the problem and/or when you have a fix. In glibc_check master-arm after: | commit glibc-2.40.9000-2-g4dc22baa84b | Author: Paul Zimmermann <Paul.Zimmermann(a)inria.fr> | Date: Mon Jul 22 08:54:23 2024 +0200 | | This patch adds larger ulp errors for the log2p1 function. | | Changes in v2: | - added larger error for long double on AMD reported by Adhemerval | (https://sourceware.org/pipermail/libc-alpha/2024-June/157755.html) | | Reviewed-by: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> FAIL: 6 regressions regressions.sum: === glibc tests === Running glibc:math ... FAIL: math/test-double-log2p1 FAIL: math/test-float-log2p1 FAIL: math/test-float32-log2p1 FAIL: math/test-float32x-log2p1 FAIL: math/test-float64-log2p1 FAIL: math/test-ldouble-log2p1 You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1585/artifact/… The full lists of regressions and improvements as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1585/artifact/… The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1585/artifact/… The configuration of this build is: CI config tcwg_glibc_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_glibc_check--master-arm-build/1585/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1583/artifact/… Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=4dc22baa84bdb4111c0a… List of configurations that regressed due to this commit : * tcwg_glibc_check ** master-arm *** FAIL: 6 regressions *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… *** https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/1585/artifact/…

1 year, 9 months

1
0
0 0

[Linaro-TCWG-CI] gcc-15-2110-g71b31690a7c5: Failure on arm

by ci_notify＠linaro.org

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. 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-1294 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-arm-next-defconfig after: | commit gcc-15-2110-g71b31690a7c5 | Author: Richard Sandiford <richard.sandiford(a)arm.com> | Date: Wed Jul 17 19:38:11 2024 +0100 | | rtl-ssa: Fix split_clobber_group [PR115928] | | One of the goals of the rtl-ssa representation was to allow a | group of consecutive clobbers to be skipped in constant time, | with amortised sublinear insertion and deletion. This involves | putting consecutive clobbers in groups. Splitting or joining | groups would be linear if we had to update every clobber on | ... 21 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 0 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 7865 # linux build successful: all # linux boot successful: boot The configuration of this build is: CI config tcwg_kernel/gnu-master-arm-next-defconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/… 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/71b31690a7c52413496e91bcc5ee4c68af… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-arm-next-defconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/…

1 year, 9 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-2165-g01c095ab77f8: FAIL: 1 regressions on arm

by Sam James

FAIL: gcc.dg/pr116003.c (test for excess errors) Excess errors: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:4:1: sorry, unimplemented: '_BitInt(5)' is not supported on this target /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:8:1: sorry, unimplemented: '_BitInt(129)' is not supported on this target /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:11:5: sorry, unimplemented: '_BitInt(128)' is not supported on this target I think it needs dg-do compile { target bitint }.

1 year, 9 months

1
0
0 0

[Linaro-TCWG-CI] gcc-15-2026-g44c9403ed183: Failure on aarch64

by ci_notify＠linaro.org

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. 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-1282 , please let us know if you are looking at the problem and/or when you have a fix. In CI config tcwg_kernel/gnu-master-aarch64-lts-allmodconfig after: | commit gcc-15-2026-g44c9403ed183 | Author: Alejandro Colomar <alx(a)kernel.org> | Date: Sat Jun 29 15:10:43 2024 +0200 | | c, objc: Add -Wunterminated-string-initialization | | Warn about the following: | | char s[3] = "foo"; | | Initializing a char array with a string literal of the same length as | ... 63 lines of the commit log omitted. Results changed to # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 24546 From # reset_artifacts: -10 # build_abe binutils: -9 # build_abe stage1: -5 # build_abe qemu: -2 # linux_n_obj: 24548 The configuration of this build is: CI config tcwg_kernel/gnu-master-aarch64-lts-allmodconfig -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-… 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/44c9403ed1833ae71a59e84f9e37af3182… List of configurations that regressed due to this commit : * tcwg_kernel ** gnu-master-aarch64-lts-allmodconfig *** Failure *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… *** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-…

1 year, 9 months

1
0
0 0

[Linaro-TCWG-CI] gcc patch #93154: FAIL: 1 regressions on arm

by Paul Richard Thomas

Hi there, You detected a failure in gfortran.dg/class_transformational_2.f90: PASS: gfortran.dg/class_transformational_2.f90 -O0 (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -O0 execution test PASS: gfortran.dg/class_transformational_2.f90 -O1 (test for excess errors) FAIL: gfortran.dg/class_transformational_2.f90 -O1 execution test PASS: gfortran.dg/class_transformational_2.f90 -O2 (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -O2 execution test PASS: gfortran.dg/class_transformational_2.f90 -O3 -fomit-frame-pointer ...snip... PASS: gfortran.dg/class_transformational_2.f90 -O3 -fomit-frame-pointer ...snip... PASS: gfortran.dg/class_transformational_2.f90 -O3 -g (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -O3 -g execution test PASS: gfortran.dg/class_transformational_2.f90 -Os (test for excess errors) PASS: gfortran.dg/class_transformational_2.f90 -Os execution test The stop message in the full log indicates a numeric error in the first test. I am unable to reproduce the error. Adding deallocation of all the allocated variables (which I should have done in the first place) and running valgrind with -s shows no errors and no memory loss. I find it odd that it should fail once at -O1 and not at -O2 and higher. Can you provide me with any insights; eg, by rerunning the testcase outside of the dejagnu framework? Thank you for doing this testing, by the way, even if the failure is a bit obscure at the moment. Best regards Paul

1 year, 9 months

2
6
0 0

Re: [Linaro-TCWG-CI] 2 patches in binutils: Failure on arm

by Ulf Samuelsson

I get this problem when the CI is building a patchset for the binutils with my patches. The patchset consists of 7 patches, and I suspect that this error message is generated when only part of the 7 patches are applied. Could this be true? They are interdependent, so there is no way to reorder the patches to make this work if not all the patches are applied. Den 2024-07-07 kl. 02:47, skrev ci_notify(a)linaro.org: > 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. > > 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. > > In binutils_build master-arm after: > > | 2 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/93436 > | dd57e0ed6f6 ldgram.y: Add ASCII parsing > | 304119944bb ldlex.l: Add ASCII token > | ... applied on top of baseline commit: > | 85a67d0a39a Automatic date update in version.in > > Results changed to > # reset_artifacts: > -10 > # true: > 0 > # build_abe binutils: > # FAILED > # First few build errors in logs: > # 00:01:58 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/binutils.git~master/ld/ldgram.y:711:21: error: too many arguments to function ‘lang_add_string’ > # 00:01:58 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/binutils.git~master/ld/ldgram.y:717:19: error: too many arguments to function ‘lang_add_string’ > # 00:01:58 make[4]: *** [Makefile:2290: ldgram.o] Error 1 > # 00:01:58 make[3]: *** [Makefile:1903: all-recursive] Error 1 > # 00:01:58 make[2]: *** [Makefile:1092: all] Error 2 > # 00:01:58 make[1]: *** [Makefile:8044: all-ld] Error 2 > # 00:01:58 make: *** [Makefile:1028: all] Error 2 > > From > # reset_artifacts: > -10 > # true: > 0 > # build_abe binutils: > 1 > > The configuration of this build is: > CI config tcwg_binutils_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_binutils_build--master-arm-precommit/2298/ar… > Reference build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/1304/artifa… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. -- Best Regards Ulf Samuelsson

1 year, 9 months

2
1
0 0

C++ standard library for build bot clang-armv8-lld-2stage

by mingmingl

Greetings! This is Mingming and I'm an LLVM contributor. I have received a lot of useful code review feedback from aarch64 experts. Thank you for all of that! I'm writing to report a failure ( https://lab.llvm.org/buildbot/#/builders/122/builds/150) on buildbot clang-armv8-lld-2stage triggered by my recent patch. The issue seems to stem from the C++ standard libraries not being configured in the buildbot environment. While using a c-style header is a workaround (which pr 97245 <https://github.com/llvm/llvm-project/pull/97245> did), @petrhosek reminded me that it would be good to inform maintainers so they can take a look, which makes sense to me. Could someone please assist in resolving this configuration problem? Thank you in advance and let me know if I miss anything. Thanks, Mingming

1 year, 10 months

3
4
0 0

[ACTIVITY] report week ending 28 Jun

by Peter Maydell

Progress: * UM-2 [QEMU upstream maintainership] - patch-review queue has filled up again; reviewed at least some patches ready for an arm pullreq - another KVM Forum PC meeting * QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG] - realized that FEAT_AFP means we need to refactor our FPCR/FPSR implementation, because it adds new AArch64-only bits that aren't visible in the AArch32 FPSCR format. (QEMU for historical reasons implemented FPCR and FPSR as masked views of FPSCR; now we need to switch to having FPSCR be a view of the FPCR/FPSR data.) Wrote the necessary refactoring and sent patchseries out for review. -- PMM

1 year, 10 months

1
0
0 0

Re: [PATCH 1/3] Release structures on function return

by Jørgen Kvalsvik

I think we need to revert this. I got this email from linaro/gcc-regressions: [Linaro-TCWG-CI] gcc-15-1649-g19f630e6ae8d: FAIL: 2 regressions on aarch64 regressions.sum: === gcc tests === Running gcc:gcc.misc-tests/gcov.exp ... FAIL: gcc.misc-tests/gcov-23.c (internal compiler error: in operator[], at vec.h:910) FAIL: gcc.misc-tests/gcov-23.c (test for excess errors) This did not reproduce on my machine, but I took a quick look at the hash-map implementation. hash_map.put calls hash_table.find_slot_with_hash, which calls hash_table.expand, which does move+destroy. auto_vec is not really move-aware which leads to a double-free. The fix is either to make auto_vec move-aware (and more like C++'s std::vector) or revert this patch and apply the original version with an explicit release. OK? Thanks, Jørgen On 6/25/24 12:23, Jan Hubicka wrote: >> The value vec objects are destroyed on exit, but release still needs to >> be called explicitly. >> >> gcc/ChangeLog: >> >> * tree-profile.cc (find_conditions): Release vectors before >> return. > I wonder if you turn > hash_map<int_hash<unsigned, 0>, vec<basic_block>> exprs; > to > hash_map<int_hash<unsigned, 0>, auto_vec<basic_block>> exprs; > Won't hash_map destructor take care of this by itself? > > Honza >> --- >> gcc/tree-profile.cc | 3 +++ >> 1 file changed, 3 insertions(+) >> >> diff --git a/gcc/tree-profile.cc b/gcc/tree-profile.cc >> index e4bb689cef5..18f48e8d04e 100644 >> --- a/gcc/tree-profile.cc >> +++ b/gcc/tree-profile.cc >> @@ -919,6 +919,9 @@ find_conditions (struct function *fn) >> if (!have_post_dom) >> free_dominance_info (fn, CDI_POST_DOMINATORS); >> >> + for (auto expr : exprs) >> + expr.second.release (); >> + >> cov->m_masks.safe_grow_cleared (2 * cov->m_index.last ()); >> const size_t length = cov_length (cov); >> for (size_t i = 0; i != length; i++) >> -- >> 2.39.2 >>

1 year, 10 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain