- linaro-toolchain - lists.linaro.org

Re: [Linaro-TCWG-CI] gcc-16-3093-gc7de7ddbfae: 1 regression on aarch64

by Sam James

-> PR121494

1 year, 1 month

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-556-g620f0730f31: 8 regressions 1564 fixes on aarch64

by Maxim Kuvyrkov

[This is a CI regression report that wasn't sent due to infra problem.] Hi Florian, Your glibc patch fixes a lot of failures in GDB testsuite, but also creates a few new FAILs -- are these expected? Thanks! === Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-aarch64, after: | commit glibc-2.41.9000-556-g620f0730f31 | Author: Florian Weimer <fweimer(a)redhat.com> | Date: Mon Jul 28 14:16:52 2025 +0200 | | elf: Compile _dl_debug_state separately (bug 33224) | | This ensures that the compiler will not inline it, so that | debuggers which do not use the Systemtap probes can reliably | set a breakpoint on it. | ... 3 lines of the commit log omitted. Produces 8 regressions 1564 fixes: | | regressions.sum: | Running gdb:gdb.dap/cxx-exception.exp ... | FAIL: gdb.dap/cxx-exception.exp: exceptions in log file | Running gdb:gdb.dap/ptrref.exp ... | FAIL: gdb.dap/ptrref.exp: exceptions in log file | Running gdb:gdb.threads/process-dies-while-detaching.exp ... | ... and 7 more | | fixes.sum: | Running gdb:gdb.arch/aarch64-sve-sigunwind.exp ... | FAIL: gdb.arch/aarch64-sve-sigunwind.exp: $\z2.b.u contents were correctly unwound | FAIL: gdb.arch/aarch64-sve-sigunwind.exp: size of $\z3.b.u was correctly unwound | FAIL: gdb.arch/aarch64-sve-sigunwind.exp: $\z12.b.u contents were correctly unwound | FAIL: gdb.arch/aarch64-sve-sigunwind.exp: $\z22.b.u contents were correctly unwound | ... and 1676 more Used configuration : *CI config* tcwg_gnu_native_check_gdb master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-692. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_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… 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://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=620f0730f311635cd0e1… -- Maxim Kuvyrkov https://www.linaro.org

1 year, 1 month

3
2
0 0

[Linaro-TCWG-CI] llvmorg-22-init-2744-ga15b629527a9: 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. In tcwg_flang_build/main-aarch64, after: | commit llvmorg-22-init-2744-ga15b629527a9 | Author: Jon Roelofs <jonathan_roelofs(a)apple.com> | Date: Tue Aug 5 17:08:00 2025 -0700 | | Revert "Strip the full path from __FILE__ in the LDBG macro and keep only the filename (#150677)" | | This reverts commit 5d26e3c227f4b4a1761a8b0001b3165198def479. | | It breaks the modules build of clang, since every source file has a different | ... 9 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : | # FAILED | # First few build errors in logs: | # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:71:12: error: a type specifier is required for all declarations | # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:77:4: error: identifier 'raw_ldbg_ostream' after '~' in destructor name does not name a type | # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:54:9: error: member initializer 'os' does not name a non-static data member or base class | # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:59:23: error: use of undeclared identifier 'os' | # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:61:12: error: use of undeclared identifier 'os' | # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:73:7: error: only constructors take base initializers | # 00:03:30 ../llvm/llvm/include/llvm/Support/DebugLog.h:75:5: error: use of undeclared identifier 'SetUnbuffered' | # 00:03:30 ../llvm/mlir/lib/IR/PatternLoggingListener.cpp:10:3: error: use of undeclared identifier '_GET_LDBG_MACRO' | # 00:03:30 ../llvm/mlir/lib/IR/PatternLoggingListener.cpp:17:3: error: use of undeclared identifier '_GET_LDBG_MACRO' | # 00:03:30 ../llvm/mlir/lib/IR/PatternLoggingListener.cpp:24:3: error: use of undeclared identifier '_GET_LDBG_MACRO' | | From | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;clang-tools-extra openmp : | 1 Used configuration : tcwg_flang_build/main-aarch64 We track this bug report under https://linaro.atlassian.net/browse/LLVM-1738. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in * https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5111/artifac… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5111/artifac… Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5111/artifac… Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/5108/artifac… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… Full commit : https://github.com/llvm/llvm-project/commit/a15b629527a975ec592c95d69d04ef3…

1 year, 1 month

1
0
0 0

How can I reproduce a flang-arm64-windows-msvc LLVM buildbot error?

by tobias.gysi＠nextsilicon.com

Dear Linaro Community, I am looking for advice on how to reproduce a flang-arm64-windows-msvc LLVM build bot failure (hopefully I ended up in the right place here). I had to revert an LLVM PR (https://github.com/llvm/llvm-project/pull/150783) that broke the flang-arm64-windows-msvc LLVM buildbot yesterday due to some tablegen-related problem. I did prepare a reland PR (https://github.com/llvm/llvm-project/pull/151125) that addresses a potential issue. However, since I did not see any other buildbot failures and since I was not able to reproduce the problem locally, I wonder if there is a way to run the flang-arm64-windows-msvc buildbot on my reland PR? Alternatively, hints on how to reproduce the problem locally on a x86 Linux machine would be appreciated. Best, Tobias

1 year, 1 month

3
6
2 0

Re: [Linaro-TCWG-CI] 9 patches in gdb: 23 regressions 3 fixes on arm

by Thiago Jung Bauermann

Hello Tom, ci_notify(a)linaro.org writes: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details > below. > > In gdb_check master-arm, after: > | 9 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/117104 > | 02107b8252d [PATCH 9/9] [gdb/testsuite] Add gdb.tui/tui-mode-switch.exp > | 74b2f1eb572 [PATCH 8/9] [gdb/testsuite] Add Term::with_term > | 6f3e219e902 [PATCH 7/9] [gdb/testsuite] Add Term::_esc_0x3d and Term::_esc_0x3e > | 9d1466d5f3f [PATCH 6/9] [gdb/testsuite] Add Term::_esc_0x28_B and Term::_esc_0x28_0 > | 2c51f81639a [PATCH 5/9] [gdb/testsuite] Add Term::_csi_r > | ... and 4 more patches in gdb > | ... applied on top of baseline commit: > | 0937ed3f050 Add forgotten ChangeLog entry for commit > | 7c1c13e896c76879bcf3fb29332e0a59918bc9e0. > > Produces 23 regressions 3 fixes: <snip> > Current build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/5001/artifac… > Reference build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3017/artifact/ar… This is a false positive. We're currently moving our CI jobs to another machine (of a different kind, even) and the reference build ran on the new machine while the build with the patches ran on the old one. Sorry for the noise. -- Thiago

1 year, 1 month

2
2
0 0

Re: [Linaro-TCWG-CI] 3 patches in gdb: 23 regressions 3 fixes on arm

by Thiago Jung Bauermann

Hello Tom, ci_notify(a)linaro.org writes: > In gdb_check master-arm, after: > | 3 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/117137 > | a05322508b7 [PATCH 3/3] Require Tcl 8.6.2 > | 2b7dc482e23 [PATCH 2/3] Rewrite tcl_version_at_least > | a88c3d9f501 [PATCH 1/3] Require Tcl 8.5 > | ... applied on top of baseline commit: > | 0937ed3f050 Add forgotten ChangeLog entry for commit > | 7c1c13e896c76879bcf3fb29332e0a59918bc9e0. > > Produces 23 regressions 3 fixes: <snip> > Current build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/5004/artifac… > Reference build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3017/artifact/ar… This is a false positive. We're currently moving our CI jobs to another machine (of a different kind, even) and the reference build ran on the new machine while the build with the patches ran on the old one. The same happened with the other patch about which we notified you today. Sorry for the noise. -- Thiago

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gdb patch #117052: 23 regressions 3 fixes on arm

by Thiago Jung Bauermann

Hello, ci_notify(a)linaro.org writes: > In gdb_check master-arm, after: > | gdb patch https://patchwork.sourceware.org/patch/117052 > | Author: Aria Nolan <aria(a)chytrid.org> > | Date: Sat Jul 26 18:44:40 2025 -0600 > | > | [PATCH] gdb: turn off completions for the inferior command > | > | The inferior command takes an inferior ID as an argument. The current > | completer for the command offers symbols. This patch removes the completion, > | since the IDs are sequential so it makes little sense to offer that. > | ... 2 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 0937ed3f050 Add forgotten ChangeLog entry for commit > | 7c1c13e896c76879bcf3fb29332e0a59918bc9e0. > > Produces 23 regressions 3 fixes: <snip> > Current build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/5000/artifac… > Reference build : > https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/3017/artifact/ar… This is a false positive. We're currently moving our CI jobs to another machine (of a different kind, even) and the reference build ran on the new machine while the build with the patch ran on the old one. Sorry for the noise. -- Thiago

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #117089: 84 regressions 2 fixes on aarch64

by Christophe Lyon

Hi Nathan, Sorry this report is incorrect because we are in the process of moving to new machines. Please ignore it. Sorry for the noise. Thanks, Christophe On Tue, 29 Jul 2025 at 04: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. > > In gcc_check master-aarch64, after: > | gcc patch https://patchwork.sourceware.org/patch/117089 > | Author: Nathan Myers <ncm(a)cantrip.org> > | Date: Mon Jul 28 05:25:55 2025 -0400 > | > | [PATCHv5] libstdc++: Add NTTP bind_front, -back, not_fn (P2714) [PR119744] > | > | Stabilizing. > | > | Changes in v5: > | ... 39 lines of the commit log omitted. > | ... applied on top of baseline commit: > | a51bf9e10182 ifcvt: Fix ifcvt for multiple phi nodes after factoring operator [PR121236] > > Produces 84 regressions 2 fixes: > | > | regressions.sum: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/cpp1z/pr85569.C -std=c++20 (test for excess errors) > | Running g++:g++.dg/modules/modules.exp ... > | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (internal compiler error: canonical types differ for identical types 'auto' and 'auto') > | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors) > | ... and 83 more > | > | fixes.sum: > | Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ... > | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test > | Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ... > | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test > > Used configuration : > *CI config* tcwg_gcc_check master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/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-aarch64-precommit/11852/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4055/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, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #117090: 6976 regressions 2 fixes on aarch64

by Christophe Lyon

Hi Richard, Sorry this report is incorrect because we are in the process of moving to new machines. Please ignore it. Sorry for the noise. Thanks, Christophe On Tue, 29 Jul 2025 at 04:11, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_check master-aarch64, after: > | gcc patch https://patchwork.sourceware.org/patch/117090 > | Author: Richard Biener <rguenther(a)suse.de> > | Date: Mon Jul 28 11:36:06 2025 +0200 > | > | [PATCH] Remove STMT_VINFO_MEMORY_ACCESS_TYPE > | > | This should be present only on SLP nodes now. The RISC-V changes > | are mechanical along the line of the SLP_TREE_TYPE changes. > | > | ... 19 lines of the commit log omitted. > | ... applied on top of baseline commit: > | a51bf9e1018 ifcvt: Fix ifcvt for multiple phi nodes after factoring operator [PR121236] > > Produces 6976 regressions 2 fixes: > | > | regressions.sum: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/opt/pr112374.C -std=gnu++11 (internal compiler error: Segmentation fault) > | FAIL: g++.dg/opt/pr112374.C -std=gnu++11 (test for excess errors) > | FAIL: g++.dg/opt/pr112374.C -std=gnu++17 (internal compiler error: Segmentation fault) > | FAIL: g++.dg/opt/pr112374.C -std=gnu++17 (test for excess errors) > | ... and 6984 more > | > | fixes.sum: > | Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ... > | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test > | Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ... > | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test > > Used configuration : > *CI config* tcwg_gcc_check master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/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-aarch64-precommit/11853/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4055/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, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-2319-gb5ffc8e75a8: 2 regressions on aarch64

by Yury Khrustalev

On Thu, Jul 24, 2025 at 10:42:41AM +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. It appears that this build was running tests on qemu that doesn't seem to support the same signal handling behaviour for SME as would the kernel that supports SME. On a system that supports SME with kernel 6.16 these tests work as expected provided that their dependencies are resolved by dynamic loader to the new version of libgcc. So, no issue in the patch or in the tests. Thanks, Yury IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

1 year, 1 month

2
1
0 0

Re: [Linaro-TCWG-CI] gcc-16-2319-gb5ffc8e75a8: 2 regressions on aarch64

by Yury Khrustalev

> Our automatic CI has detected problems related to your patch(es). Thanks, I'm looking into it. Kind regards, Yury IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

1 year, 1 month

1
0
0 0

[ARM EABI] Adjust 'libgomp.c++/target-cdtor-{1,2}.C' for 'targetm.cxx.use_aeabi_atexit' [PR119853, PR119854] (was: [Linaro-TCWG-CI] gcc-16-130-gaafe942227b: 10 regressions on arm)

by Thomas Schwinge

Hi! On 2025-04-26T00:09:21+0000, ci_notify--- via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_check master-arm, after: > | commit gcc-16-130-gaafe942227b > | Author: Thomas Schwinge <tschwinge(a)baylibre.com> > | Date: Wed Apr 23 10:51:48 2025 +0200 > | > | GCN, nvptx offloading: Host/device compatibility: Itanium C++ ABI, DSO Object Destruction API [PR119853, PR119854] > | > | '__dso_handle' for '__cxa_atexit', '__cxa_finalize'. See > | <https://itanium-cxx-abi.github.io/cxx-abi/abi.html#dso-dtor>. > | > | ... 13 lines of the commit log omitted. > > Produces 10 regressions: > | > | regressions.sum: > | Running libgomp:libgomp.c++/c++.exp ... > | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, " 4 > | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sH1, \\&__dso_handle>" 1 > | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sH2, \\&__dso_handle>" 1 > | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sHD1, \\&__dso_handle>" 1 > | ... and 6 more > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1568. Is it expected that I'm not able to log into the Jira instance, and that most of the links in there are either: | Secure Connection Failed | | An error occurred during a connection to git-us.linaro.org. Cannot communicate securely with peer: no common encryption algorithm(s). ..., or: | Oops! | | Not Found | | This page may not exist, or you may not have permission to see it. > Please let us know if you have a fix. I should have a fix: the attached "Adjust 'libgomp.c++/target-cdtor-{1,2}.C' for 'targetm.cxx.use_aeabi_atexit' [PR119853, PR119854]" ought to address this. I've "mock-tested" this locally; is there a way for me to run this through the Linaro "pre-commit" CI? Grüße Thomas > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/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/3752/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/artifact/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3751/artifact/ar… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=aafe942227baf8c2bcd4cac2c…

1 year, 1 month

2
2
0 0

Re: [Linaro-TCWG-CI] llvmorg-22-init-340-ge8a891b0f9d2: 4 regressions on aarch64

by Jonathan Cohen

I have pushed the following PR to address issues in my patch: https://github.com/llvm/llvm-project/pull/149703 I haven’t verified that it fixes your regression, will do that shortly. Jonathan > On 18 Jul 2025, at 20:40, ci_notify(a)linaro.org wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after: > | commit llvmorg-22-init-340-ge8a891b0f9d2 > | Author: Jonathan Cohen <joncoh(a)apple.com> > | Date: Thu Jul 17 19:21:57 2025 +0300 > | > | [AArch64][Machine-Combiner] Split gather patterns into neon regs to multiple vectors (#142941) > | > | This changes optimizes gather-like sequences, where we load values > | separately into lanes of a neon vector. Since each load has serial > | dependency, when performing multiple i32 loads into a 128 bit vector for example, it > | ... 3 lines of the commit log omitted. > > Produces 4 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0631 ... > | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0110.test > | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0111.test > | Running test-suite:Fujitsu/Fortran/0640 ... > | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0074.test > | ... and 2 more > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld > * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} > cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1731. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_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… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > 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… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… > > Full commit : https://github.com/llvm/llvm-project/commit/e8a891b0f9d2a742ac3904116aaec2c…

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-2334-g9e330977385: 2 regressions on arm

by Jonathan Wakely

Tomasz, The new __any_input_iterator type should only be declared for C++20 and higher, so guarded by __cpp_lib_concepts Just checking __cpp_concepts isn't enough, because that's true for -std=c++17 -fconcepts but std::input_iterator isn't defined in that case. On Fri, 18 Jul 2025 at 17:18, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In arm-eabi v7-a softfp, after: > | commit gcc-16-2334-g9e330977385 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Jun 5 12:05:19 2025 +0100 > | > | libstdc++: Add std::inplace_vector for C++26 (P0843R14) [PR119137] > | > | Implement std::inplace_vector as specified in P0843R14, without follow > | up papers, in particular P3074R7 (trivial unions). In consequence > | inplace_vector<T, N> can be used inside constant evaluations only > | ... 62 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/concepts/expression.C -std=gnu++17 (test for excess errors) > | UNRESOLVED: g++.dg/concepts/expression.C -std=gnu++17 compilation failed to produce executable > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1636. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_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-arm_v7a_softfp_e… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

1 year, 1 month

1
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-18750-gdd60663b9bfa: 2 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, Probably this failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. We'll update the test. Sorry for the noise. > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: > | commit llvmorg-21-init-18750-gdd60663b9bfa > | Author: Alexey Bataev <a.bataev(a)outlook.com> > | Date: Wed Jul 9 19:52:09 2025 -0400 > | > | [SLP] Emit reduction instead of 2 extracts + scalar op, when vectorizing operands (#147583) > | > | Added emission of the 2-element reduction instead of 2 extracts + scalar > | op, when trying to vectorize operands of the instruction, if it is more > | profitable. > > Produces 2 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/C/0030 ... > | FAIL: test-suite :: Fujitsu/C/0030/Fujitsu-C-0030_0056.test > | Running test-suite:Fujitsu/Fortran/0334 ... > | FAIL: test-suite :: Fujitsu/Fortran/0334/Fujitsu-Fortran-0334_0012.test > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld > * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} > cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1728. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_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… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > 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… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… > > Full commit : https://github.com/llvm/llvm-project/commit/dd60663b9bfaab15362a850ba7f63ba…

1 year, 1 month

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-509-g3d3572f590: 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. In master-arm, after: | commit glibc-2.41.9000-509-g3d3572f590 | Author: Florian Weimer <fweimer(a)redhat.com> | Date: Fri Jul 11 16:04:07 2025 +0200 | | Linux: Keep termios ioctl constants strictly internal | | Undefine TCGETS, TCGETS2, and related ioctl constants in the installed | headers. Extract the correct constants (using the kernel type | definitions) automatically from the UAPI headers. The kernel | ... 11 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | # FAILED | # build_abe gdb: | # build_abe qemu: | # First few build errors in logs: | # 00:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:766:27: error: ‘TCGETS’ was not declared in this scope; did you mean ‘TCGETX’? | # 00:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:772:27: error: ‘TCSETS’ was not declared in this scope; did you mean ‘TCSETA’? | # 00:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:773:28: error: ‘TCSETSF’ was not declared in this scope; did you mean ‘TCSETAF’? | # 00:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:774:28: error: ‘TCSETSW’ was not declared in this scope; did you mean ‘TCSETAW’? | # 00:07:05 make[4]: *** [Makefile:627: sanitizer_platform_limits_posix.lo] Error 1 | # 00:07:05 make[3]: *** [Makefile:533: all-recursive] Error 1 | # 00:07:05 make[2]: *** [Makefile:420: all] Error 2 | # 00:07:05 make[1]: *** [Makefile:12804: all-target-libsanitizer] Error 2 | # 00:07:05 make: *** [Makefile:1068: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | 5 | # build_abe gdb: | 6 | # build_abe qemu: | 7 Used configuration : *CI config* tcwg_gnu_cross_build master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1632. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in * https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1136/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1136/artif… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1136/artif… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1135/artif… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=3d3572f59059e2b19b85…

1 year, 1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-2112-gac2fb60a67d6: Failure on master-thumb_m7_hard_eabi

by Jonathan Wakely

On Wed, 9 Jul 2025, 08:22 , <ci_notify(a)linaro.org> wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In arm-eabi cortex-m7 hard, after: > | commit gcc-16-2112-gac2fb60a67d6 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Fri Jul 4 16:44:13 2025 +0100 > | > | libstdc++: Ensure pool resources meet alignment requirements > [PR118681] > | > | For allocations with size > alignment and size % alignment != 0 we > were > | sometimes returning pointers that did not meet the requested > aligment. > | For example, allocate(24, 16) would select the pool for 24-byte > objects > | ... 23 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe binutils: > | 1 > | # build_abe stage1 -- --set gcc_override_configure=--disable-multilib > --set gcc_override_configure=--with-mode=thumb --set > gcc_override_configure=--with-cpu=cortex-m7 --set > gcc_override_configure=--with-float=hard: > | 2 > | # build_abe newlib: > | 4 > | # build_abe stage2 -- --set gcc_override_configure=--disable-multilib > --set gcc_override_configure=--with-mode=thumb --set > gcc_override_configure=--with-cpu=cortex-m7 --set > gcc_override_configure=--with-float=hard: > | # FAILED > | # build_abe gdb: > | # build_abe qemu: > | # First few build errors in logs: > | # 00:06:32 > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/memory_resource.cc:1474:29: > error: ‘choose_block_size’ was not declared in this scope > | # 00:06:32 > /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/memory_resource.cc:1491:25: > error: ‘choose_block_size’ was not declared in this scope > | # 00:06:32 make[5]: *** [Makefile:587: memory_resource.lo] Error 1 > | # 00:06:32 make[4]: *** [Makefile:797: all-recursive] Error 1 > | # 00:06:32 make[3]: *** [Makefile:577: all-recursive] Error 1 > | # 00:06:32 make[2]: *** [Makefile:502: all] Error 2 > | # 00:06:32 make[1]: *** [Makefile:12269: all-target-libstdc++-v3] > Error 2 > | # 00:06:32 make: *** [Makefile:1062: all] Error 2 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe binutils: > | 1 > | # build_abe stage1 -- --set gcc_override_configure=--disable-multilib > --set gcc_override_configure=--with-mode=thumb --set > gcc_override_configure=--with-cpu=cortex-m7 --set > gcc_override_configure=--with-float=hard: > | 2 > | # build_abe newlib: > | 4 > | # build_abe stage2 -- --set gcc_override_configure=--disable-multilib > --set gcc_override_configure=--with-mode=thumb --set > gcc_override_configure=--with-cpu=cortex-m7 --set > gcc_override_configure=--with-float=hard: > | 5 > | # build_abe gdb: > | 6 > | # build_abe qemu: > | 7 > > Used configuration : > *CI config* tcwg_gnu_embed_build arm-eabi -mthumb -march=armv7e-m+fp.dp > -mtune=cortex-m7 -mfloat-abi=hard -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib > --with-mode=thumb --with-cpu=cortex-m7 --with-float=hard > --target_board=-mthumb/-march=armv7e-m+fp.dp/-mtune=cortex-m7/-mfloat-abi=hard/-mfpu=auto > qemu_cpu=cortex-m7 > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1625. Please let us know if you > have a fix. > I know what's wrong, will fix in a couple of hours. The definition of choose_pool_size needs to be moved outside the preprocessor group guarded by #ifdef _GLIBCXX_HAS_GTHREADS > If you have any questions regarding this report, please ask on > linaro-toolchain(a)lists.linaro.org mailing list. > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways > to reproduce a debug environment: > > You can find the failure logs in > * > https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m7_hard_eabi-b… > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m7_hard_eabi-b… > > Current build : > https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m7_hard_eabi-b… > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m7_hard_eabi-b… > > Instruction to reproduce the build : > https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

1 year, 2 months

2
1
0 0

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

by H.J. Lu

I am testing this. On Tue, Jul 8, 2025 at 7:10 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. > > In simplebootstrap_build master-aarch64-bootstrap, after: > | gcc patch https://patchwork.sourceware.org/patch/115820 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Sat Jun 28 06:27:25 2025 +0800 > | > | [PATCH] Check backend when setting DECL_ALIGN for PARM_DECL > | > | Since a backend may ignore type alignment for arguments passed on stack, > | call targetm.calls.function_arg_boundary to set DECL_ALIGN for PARM_DECL > | and change __alignof to return DECL_ALIGN, instead of TYPE_ALIGN, for > | ... 21 lines of the commit log omitted. > | ... applied on top of baseline commit: > | ed912b1ee5a libstdc++: Fix attribute order on __normal_iterator friends [PR120949] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | # FAILED > | # First few build errors in logs: > | # 00:04:46 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/gcc.git~master/libgcc/config/aarch64/lse-init.c:44:1: internal compiler error: Segmentation fault > | # 00:04:47 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/gcc.git~master/libgcc/config/aarch64/t-lse:41: lse-init.o] Error 1 > | # 00:04:47 make[2]: *** [Makefile:19575: all-stage1-target-libgcc] Error 2 > | # 00:04:47 make[1]: *** [Makefile:25557: stage1-bubble] Error 2 > | # 00:04:47 make: *** [Makefile:1106: all] Error 2 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | 1 > > Used configuration : > *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. -- H.J.

1 year, 2 months

1
0
0 0

[Linaro-TCWG-CI] v10.0.0-1793-g932522a9ddc: 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. In master-arm, after: | commit v10.0.0-1793-g932522a9ddc | Author: Richard Henderson <richard.henderson(a)linaro.org> | Date: Mon Oct 23 14:29:46 2023 -0700 | | tcg/optimize: Fold and to extract during optimize | | Reviewed-by: Pierrick Bouvier <pierrick.bouvier(a)linaro.org> | Signed-off-by: Richard Henderson <richard.henderson(a)linaro.org> Produces 6 regressions: | | regressions.sum: | Running gcc:gcc.target/aarch64/advsimd-intrinsics/advsimd-intrinsics.exp ... | FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O1 execution test | FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O2 execution test | FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test | FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test | ... and 2 more Used configuration : *CI config* tcwg_gnu_cross_check_gcc master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1617. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2154/a… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2154/a… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2154/a… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2154/a… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2153/a… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/qemu/sha… Full commit : https://gitlab.com/qemu-project/qemu/commit/932522a9ddc1f7c7866009cd73eaf79…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-15039-gea9046699eae: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. We'll update the test. Sorry for the noise. > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: > | commit llvmorg-21-init-15039-gea9046699eae > | Author: Paul Walker <paul.walker(a)arm.com> > | Date: Wed Jun 11 11:02:32 2025 +0100 > | > | [LLVM][SROA] Teach SROA how to "bitcast" between fixed and scalable vectors. (#130973) > | > | For function whose vscale_range is limited to a single value we can size > | scalable vectors. This aids SROA by allowing scalable vector load and > | store operations to be considered for replacement whereby bitcasts > | ... 1 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0136 ... > | FAIL: test-suite :: Fujitsu/Fortran/0136/Fujitsu-Fortran-0136_0012.test > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld > * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} > cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1716. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_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… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > 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… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… > > Full commit : https://github.com/llvm/llvm-project/commit/ea9046699eae04ac5159a1666f19b5b…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-1905-g7165ca43caf: Failure on arm

by Sam James

Thanks. See https://gcc.gnu.org/PR120929. Qing, you may be able to reproduce it on x86-64 with ./configure --with-build-config="bootstrap-ubsan" && make -j$(nproc) -l$(nproc) too.

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-16543-g7d2293d1d953: 2 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. We'll update the test. Sorry for the noise. > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after: > | commit llvmorg-21-init-16543-g7d2293d1d953 > | Author: Ross Kirsling <ross.kirsling(a)sony.com> > | Date: Tue Jun 24 09:51:49 2025 -0700 > | > | [InstCombine] KnownBits::isNonNegative should recognize `b - a` after `a <= b` (#145105) > | > | Alive2: https://alive2.llvm.org/ce/z/an9npN > | Fixes #142283. > > Produces 2 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0117 ... > | FAIL: test-suite :: Fujitsu/Fortran/0117/Fujitsu-Fortran-0117_0070.test > | Running test-suite:Fujitsu/Fortran/0680 ... > | FAIL: test-suite :: Fujitsu/Fortran/0680/Fujitsu-Fortran-0680_0065.test > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld > * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} > cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1715. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_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… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > 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… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… > > Full commit : https://github.com/llvm/llvm-project/commit/7d2293d1d95379bbdbb6446b088219a…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-14994-g163c67ad3d1b: 41 regressions on aarch64

by Peter Klausler

That patch was reverted. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Monday, June 23, 2025 at 07:20 To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-21-init-14994-g163c67ad3d1b: 41 regressions on aarch64 External email: Use caution opening links or attachments Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O0-debug, after: | commit llvmorg-21-init-14994-g163c67ad3d1b | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Tue Jun 10 14:44:19 2025 -0700 | | [flang][runtime] Replace recursion with iterative work queue (#137727) | | Recursion, both direct and indirect, prevents accurate stack size | calculation at link time for GPU device code. Restructure these | recursive (often mutually so) routines in the Fortran runtime with new | ... 15 lines of the commit log omitted. Produces 41 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0449 ... | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0000.test | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0001.test | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0002.test | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0003.test | ... and 41 more | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-1708>. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> The full lists of regressions and improvements as well as configure and make commands are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> The list of [ignored] baseline and flaky failures are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1041…> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…<https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/163c67ad3d1bf7af6590930d8f18700…>

1 year, 2 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-450-g0dbbc44bfd2: 2 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. In master-arm, after: | commit glibc-2.41.9000-450-g0dbbc44bfd2 | Author: Andreas Schwab <schwab(a)suse.de> | Date: Wed Jun 18 13:17:29 2025 +0200 | | Fix termios related targets | | Move Linux-specific termios headers and tests from misc to termios subdir | and install newly added bits/termios-cbaud.h. Produces 2 regressions: | | regressions.sum: | Running gdb:gdb.base/term.exp ... | FAIL: gdb.base/term.exp: initial: info terminal | Running gdb:gdb.reverse/test_ioctl_TCSETSW.exp ... | FAIL: gdb.reverse/test_ioctl_TCSETSW.exp: handle TCSETSW Used configuration : *CI config* tcwg_gnu_native_check_gdb master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1610. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2049/… 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-arm-build/2049/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2049/… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2049/… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2048/… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=0dbbc44bfd256683705c…

1 year, 2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

by Sam James

Could you file a glibc bug for this please? It needs some analysis to see if it's an FP or not. There's actually a suppression for -Os already there: if (elem < table_size) { /* Compare the byte sequence but only if this is not part of a range. */ /* The compiler might warn that idx may be used uninitialized, however it will be reached iff elem < table_size which means that it was properly set in the loop above. */ DIAG_PUSH_NEEDS_COMMENT; DIAG_IGNORE_Os_NEEDS_COMMENT (8, "-Wmaybe-uninitialized"); if (! is_range # if WIDE_CHAR_VERSION && __wmemcmp (n, &wextra[1], c1) == 0 # else && memcmp (n, &extra[idx + 1], c1) == 0 # endif ) { n += c1 - 1; goto matched; } DIAG_POP_NEEDS_COMMENT;

1 year, 2 months

3
2
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain