- linaro-toolchain - lists.linaro.org

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

by Sam James

-> PR121494

1 week

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 week, 3 days

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 week, 5 days

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

2 weeks, 4 days

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

2 weeks, 5 days

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

2 weeks, 5 days

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

2 weeks, 5 days

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.

2 weeks, 6 days

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.

2 weeks, 6 days

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.

3 weeks

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.

3 weeks, 4 days

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…

4 weeks

2
2
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 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 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 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 month, 1 week

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 month, 1 week

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 month, 2 weeks

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 month, 2 weeks

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 month, 2 weeks

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 month, 2 weeks

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 month, 3 weeks

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 month, 4 weeks

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 month, 4 weeks

3
2
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-14927-g007d29e30c6e: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, As discussed in https://github.com/llvm/llvm-project/issues/141928 , this is an error of the test program Fortran/0614/0614_0005.f. Please ignore the mail, sorry. We've fixed the test internally. It will be pushd to the GitHub. > 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-14927-g007d29e30c6e > | Author: Dominik Adamski <dominik.adamski(a)amd.com> > | Date: Tue Jun 10 16:46:13 2025 +0200 > | > | [Flang] Turn on alias analysis for locally allocated objects (#143489) > | > | Previously, a bug in the MemCptOpt LLVM IR pass caused issues with > | adding alias tags for locally allocated objects for Fortran code. > | > | ... 8 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0614 ... > | FAIL: test-suite :: Fujitsu/Fortran/0614/Fujitsu-Fortran-0614_0005.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-1707. 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/007d29e30c6e311501ed97b7a368521…

1 month, 4 weeks

1
0
0 0

[PATCH] [arm] require armv7 support for [PR120424] (was: Re: [PATCH, FYI?] [arm] [vxworks] require thumb2 for pr120424.C)

by Alexandre Oliva

On Jun 19, 2025, Alexandre Oliva <oliva(a)adacore.com> wrote: > Or maybe the requirements for this testcase should be stated as > arm_arch_v7? I'd have to add arm_arch_v7 to > check_effective_target_arm_arch_FUNC_ok et al, if there aren't reasons > why it's not there, but I'd be happy to do that, and use dg-add-options > instead of an explicit -march=armv7, like pr117675.c, if that would be > preferred. It turned out that the regression report I got from linaro was related https://linaro.atlassian.net/browse/GNU-1599 While testing a configuration with -mfloat-abi=hard, -marmv7 is rejected because it doesn't have an FPU. Requiring thumb2 wouldn't have avoided this failure, but requiring armv7 is a proper fix for both problems. (sorry it me took so long; I'm still busy busy with other fp2sp-elimination-disabled-during-lra problems affecting arm) Without stating the architecture version required by the test, test runs with options that are incompatible with the required architecture version fail, e.g. -mfloat-abi=hard. armv7 was not covered by the long list of arm variants in target-supports.exp, so add it, and use it for the effective target requirement and for the option. Tested on arm-eabi, and also on arm-vx7r2 with gcc-14. Ok to install? for gcc/testsuite/ChangeLog PR rtl-optimization/120424 * lib/target-supports.exp (arm arches): Add arm_arch_v7. * g++.target/arm/pr120424.C: Require armv7 support. Use dg-add-options arm_arch_v7 instead of explicit -march=armv7. --- gcc/testsuite/g++.target/arm/pr120424.C | 4 +++- gcc/testsuite/lib/target-supports.exp | 1 + 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.target/arm/pr120424.C b/gcc/testsuite/g++.target/arm/pr120424.C index 4d0e49013c04a..40295ac80da93 100644 --- a/gcc/testsuite/g++.target/arm/pr120424.C +++ b/gcc/testsuite/g++.target/arm/pr120424.C @@ -1,5 +1,7 @@ /* { dg-do compile } */ -/* { dg-options "-march=armv7 -O2 -fstack-clash-protection -fnon-call-exceptions" } */ +/* { dg-require-effective-target arm_arch_v7_ok } */ +/* { dg-options "-O2 -fstack-clash-protection -fnon-call-exceptions" } */ +/* { dg-add-options arm_arch_v7 } */ /* { dg-final { scan-assembler-not {#-8} } } */ /* LRA register elimination gets confused when register spilling causes arm_frame_pointer_required to switch from false to true, and diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index dfffe3adfbdd0..858fa1787f19c 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -6073,6 +6073,7 @@ foreach { armfunc armflag armdefs } { v6z_arm "-march=armv6z+fp -marm" "__ARM_ARCH_6Z__ && !__thumb__" v6z_thumb "-march=armv6z+fp -mthumb -mfloat-abi=softfp" "__ARM_ARCH_6Z__ && __thumb__" v6m "-march=armv6-m -mthumb -mfloat-abi=soft" __ARM_ARCH_6M__ + v7 "-march=armv7" __ARM_ARCH_7__ v7a "-march=armv7-a+fp" __ARM_ARCH_7A__ v7a_arm "-march=armv7-a+fp -marm" "__ARM_ARCH_7A__ && !__thumb__" v7a_fp_hard "-march=armv7-a+fp -mfpu=auto -mfloat-abi=hard" __ARM_ARCH_7A__ -- Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/ Free Software Activist FSFLA co-founder GNU Toolchain Engineer More tolerance and less prejudice are key for inclusion and diversity. Excluding neuro-others for not behaving ""normal"" is *not* inclusive!

2 months

1
0
0 0

[automated CI mails] Need help with a regression Linaro CI notified me of

by Filip Kastl

Hi all. I got an automated mail about this GCC regression related to one of my commits. https://linaro.atlassian.net/browse/GNU-1578 The mail itself mentioned only a testsuite regression. I fixed that. However, this was also linked in the mail: https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil… That looks like a different regression. As far as I can tell, `make profiledbootstrap` is failing on arm. I have only very limited access to arm machines. I tried to reproduce this on an Aarch64 machine and didn't succeed. Could you check that this regression is still present on current trunk and/or help me reproduce it? Btw the "Instructions to reproduce the build" link doesn't work for me. I get "Request is not authorized". https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Thanks, Filip Kastl

2 months

2
2
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-434-g5cf101a85aa: 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 master-aarch64, after: | commit glibc-2.41.9000-434-g5cf101a85aa | Author: H. Peter Anvin (Intel) <hpa(a)zytor.com> | Date: Wed Jun 11 18:35:36 2025 -0700 | | linux: implement arbitrary and split speeds in termios | | Linux has supported arbitrary speeds and split speeds in the kernel | since 2008 on all platforms except Alpha (fixed in 2020), but glibc | was never updated to match. This is further complicated by POSIX uses | ... 33 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:12:17 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/aarch64-linux-gnu/libc/usr/include/bits/termios.h:54:10: fatal error: bits/termios-cbaud.h: No such file or directory | # 00:12:17 make[4]: *** [Makefile:627: sanitizer_platform_limits_posix.lo] Error 1 | # 00:12:17 make[3]: *** [Makefile:533: all-recursive] Error 1 | # 00:12:17 make[2]: *** [Makefile:420: all] Error 2 | # 00:12:17 make[1]: *** [Makefile:12801: all-target-libsanitizer] Error 2 | # 00:12:17 make: *** [Makefile:1065: 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-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1607. 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-aarch64-build/1133/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_build--master-aarch64-build/1133/a… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1133/a… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1132/a… 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=5cf101a85aae0d703cdd…

2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-14805-g112490f06abc: 2 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This is probably a false detection by a precision error of floating-point arithmetic. Please ignore the mail. > 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-14805-g112490f06abc > | Author: Craig Topper <craig.topper(a)sifive.com> > | Date: Mon Jun 9 12:38:08 2025 -0700 > | > | [ConstantFolding] Add support for llvm.atan in constant folding. (#143416) > | > | Fixes #143360 > > Produces 2 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0360 ... > | FAIL: test-suite :: Fujitsu/Fortran/0360/Fujitsu-Fortran-0360_0269.test > | FAIL: test-suite :: Fujitsu/Fortran/0360/Fujitsu-Fortran-0360_0272.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-1704. 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/112490f06abca669eb3fe158739bf75…

2 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-423-gcde5caa4bb2: 1 regression 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 glibc_check master-arm, after: | commit glibc-2.41.9000-423-gcde5caa4bb2 | Author: Cupertino Miranda <cupertino.miranda(a)oracle.com> | Date: Mon Jun 16 12:51:53 2025 +0000 | | malloc: add testing for large tcache support | | This patch adds large tcache support tests by re-executing malloc tests | using the tunable: glibc.malloc.tcache_max=1048576 | Test names are postfixed with "largetcache". | ... 2 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:. ... | FAIL: lint-makefiles Used configuration : *CI config* tcwg_glibc_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-1606. 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_glibc_check--master-arm-build/2931/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/2931/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2931/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2931/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2930/artifact/… 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=cde5caa4bb21d5c474b9…

2 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-417-gf3c82fc1b4: 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 glibc_build master-aarch64, after: | commit glibc-2.41.9000-417-gf3c82fc1b4 | Author: Radko Krkos <krkos(a)mail.muni.cz> | Date: Sat Jun 14 11:07:40 2025 +0200 | | io: Mark lockf() __wur [BZ #32800] | | In commit 0476597b28 flock() was marked __wur in posix/unistd.h, but not | in io/fcntl.h, the declarations must match. | | ... 1 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | # First few build errors in logs: | # 00:01:42 programs/locarchive.c:641:18: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 programs/locarchive.c:653:14: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 programs/locarchive.c:660:14: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 programs/locarchive.c:679:14: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 make[2]: *** [../o-iterator.mk:9: /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/locale/locarchive.o] Error 1 | # 00:01:42 make[1]: *** [Makefile:484: locale/others] Error 2 | # 00:01:42 make: *** [Makefile:20: all] Error 2 | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1 Used configuration : *CI config* tcwg_glibc_build 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-1605. 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_glibc_build--master-aarch64-build/2952/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2952/artif… Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2952/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2950/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=f3c82fc1b41261f582f5…

2 months

2
1
0 0

Re: [Linaro-TCWG-CI] glibc patch #113987: 1 regression on aarch64

by H.J. Lu

On Mon, Jun 9, 2025 at 10:02 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. > > In glibc_check master-aarch64, after: > | glibc patch https://patchwork.sourceware.org/patch/113987 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Mon Jun 9 05:22:10 2025 +0800 > | > | [PATCH] i386: Update ___tls_get_addr to preserve vector registers > | > | Compiler generates the following instruction sequence for dynamic TLS > | access: > | > | ... 44 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 0a027674a10 x86: Avoid GLRO(dl_x86_cpu_features) > > Produces 1 regression: > | > | regressions.sum: > | Running glibc:elf ... > | FAIL: elf/tst-tls23 So, this is a run-time failure. What happens if you run it by hand? > Used configuration : > *CI config* tcwg_glibc_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_glibc_check--master-aarch64-precommit/3701/a… > 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-aarch64-precommit/3701/a… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/a… > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/a… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2930/artif… > > 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.

2 months, 1 week

1
0
0 0

Fwd: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed build (failure) (main)

by Cameron McInally

Hi Linaro folks, It appears my latest commit has broken your BuildBot: fatal error: file 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\llvm\include\llvm\Support\Compiler.h' has been modified since the precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' was built: size changed (was 26948, now 27102) note: please rebuild precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' I'm not sure if it's possible for me to rebuild the precompiled header myself. Any suggestions on how to proceed? Thanks in advance, Cameron ---------- Forwarded message --------- From: <llvm.buildmaster(a)lab.llvm.org> Date: Fri, Jun 6, 2025 at 6:13 PM Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed build (failure) (main) To: Cameron McInally <cameron.mcinally(a)nyu.edu>, Thurston Dang <thurston(a)google.com> Cc: <llvm.buildmaster(a)lab.llvm.org> The Buildbot has detected a new failure on builder flang-arm64-windows-msvc while building clang. Full details are available at: https://urldefense.proofpoint.com/v2/url?u=https-3A__lab.llvm.org_buildbot_… Worker for this Build: linaro-armv8-windows-msvc-01 Blamelist: Cameron McInally <cameron.mcinally(a)nyu.edu>, Thurston Dang <thurston(a)google.com> BUILD FAILED: failed build (failure) Step 5 (build-unified-tree) failure: build (failure) ... 378.972 [2600/10/4115] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/char-set.cpp.obj 380.006 [2599/10/4116] Building CXX object tools/flang/lib/Evaluate/CMakeFiles/FortranEvaluate.dir/cmake_pch.cxx.obj 380.596 [2598/10/4117] Building AArch64GenInstrInfo.inc... 381.268 [2597/10/4118] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/char-buffer.cpp.obj 382.326 [2596/10/4119] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/debug-parser.cpp.obj 382.422 [2595/10/4120] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/characters.cpp.obj 382.547 [2594/10/4121] Building AArch64GenSubtargetInfo.inc... 383.755 [2593/10/4122] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/instrumented-parser.cpp.obj 385.992 [2592/10/4123] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/message.cpp.obj 388.630 [2591/10/4124] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj FAILED: tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj ccache C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\clang-cl.exe /nologo -TP -DFLANG_INCLUDE_TESTS=1 -DGTEST_HAS_RTTI=0 -DUNICODE -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_GLIBCXX_ASSERTIONS -D_HAS_EXCEPTIONS=0 -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -D_UNICODE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/lib/Parser -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/llvm/include -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/../mlir/include -imsvcC:/Users/tcw g/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/clang/include -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/llvm/../clang/include /DWIN32 /D_WINDOWS /Zc:inline /Zc:__cplusplus /Oi /Brepro /bigobj /permissive- -Werror=unguarded-availability-new /W4 -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -Wctad-maybe-unsupported /Gw -Wno-deprecated-copy -Wno-string-conversion -Wno-ctad-maybe-unsupported -Xclang -fno-pch-timestamp /O2 /Ob2 -std:c++17 -MD /EHs-c- /GR- -UNDEBUG /YuC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/cmake_pch.hxx /FpC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/ lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch /FIC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/cmake_pch.hxx /showIncludes /Fotools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj /Fdtools\flang\lib\Parser\CMakeFiles\FortranParser.dir\FortranParser.pdb -c -- C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/lib/Parser/preprocessor.cpp fatal error: file 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\llvm\include\llvm\Support\Compiler.h' has been modified since the precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' was built: size changed (was 26948, now 27102) note: please rebuild precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' 1 error generated. 392.025 [2591/9/4125] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/prescan.cpp.obj 393.052 [2591/8/4126] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/parsing.cpp.obj 393.434 [2591/7/4127] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/parse-tree.cpp.obj 395.861 [2591/6/4128] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/expr-parsers.cpp.obj 402.121 [2591/5/4129] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/io-parsers.cpp.obj 408.915 [2591/4/4130] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/openacc-parsers.cpp.obj 412.795 [2591/3/4131] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/executable-parsers.cpp.obj 425.616 [2591/2/4132] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/Fortran-parsers.cpp.obj 437.843 [2591/1/4133] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/openmp-parsers.cpp.obj ninja: build stopped: subcommand failed. Sincerely, LLVM Buildbot

2 months, 1 week

2
2
0 0

RE: [Linaro-TCWG-CI] llvmorg-21-init-14077-g6f64a600649a: 125 regressions on aarch64

by Eli Friedman

I guess the issue is the following: clang: ../llvm/llvm/lib/Target/AArch64/AArch64FrameLowering.cpp:2857: StackOffset llvm::AArch64FrameLowering::resolveFrameOffsetReference(const MachineFunction &, int64_t, bool, bool, Register &, bool, bool) const: Assertion `-ObjectOffset > (int64_t)AFI->getSVECalleeSavedStackSize() && "Math isn't correct for CSRs with FPAfterSVECalleeSaves"' failed. PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script. I'll try to have a patch tomorrow. Thanks, -Eli -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Saturday, June 7, 2025 10:41 PM To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com Cc: maxim.kuvyrkov(a)linaro.org; Eli Friedman <efriedma(a)quicinc.com> Subject: [Linaro-TCWG-CI] llvmorg-21-init-14077-g6f64a600649a: 125 regressions on aarch64 WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. 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-14077-g6f64a600649a | Author: Eli Friedman <efriedma(a)quicinc.com> | Date: Mon Jun 2 18:28:23 2025 -0700 | | [AArch64] Initial compiler support for SVE unwind on Windows. (#138609) | | Most bits of this are straightforward: when we emit SVE instructions in | the prologue/epilogue, emit corresponding opcodes. | | ... 7 lines of the commit log omitted. Produces 125 regressions: | | regressions.sum: | Running test-suite:Fujitsu/C/0003 ... | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0088.test | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0090.test | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0091.test | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0092.test | ... and 122 more | # "NOEXE" means : the test program cannot be compiled 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://linaro.atlassian.net/browse/LLVM-1699. 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-O0-debug-build/1023… 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-O0-debug-build/1023… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1023… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1023… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1022… 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/6f64a600649a95141526043b170aa42…

2 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-1247-gbdae7824cd9: 7 regressions on arm

by Jonathan Wakely

On Fri, 6 Jun 2025 at 18: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. > > In gcc_check master-arm, after: > | commit gcc-16-1247-gbdae7824cd9 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Jun 4 15:53:20 2025 +0100 > | > | libstdc++: Optimize std::counting_semaphore for futex path > | > | Rename __semaphore_base to __semaphore_impl, because it's not used as a > | base class. Replace the three identical lambda expressions with a named > | class, __semaphore_impl::_Available, which stores the most recent > | ... 27 lines of the commit log omitted. > > Produces 7 regressions: > | > | regressions.sum: > | Running g++:g++.dg/modules/modules.exp ... > | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors) > | FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors) > | FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess errors) > | FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess errors) > | ... and 3 more > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1598. Please let us know if you have a fix. It should be fixed at r16-1270-g7407891a3d7c17 > > If you have any questions regarding this report, please ask on linaro-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/3946/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/3946/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3945/artifact/ar… > > 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

2 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-427-g86627faec10d: 11 regressions on arm

by Jonathan Wakely

On Wed, 4 Jun 2025 at 02:50, <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 master-arm_eabi, after: > | commit gcc-16-427-g86627faec10d > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Fri Apr 25 21:09:18 2025 +0100 > | > | libstdc++: Rewrite atomic builtin checks [PR70560] > | > | Currently the GLIBCXX_ENABLE_ATOMIC_BUILTINS macro checks for a variety > | of __atomic built-ins for bool, short and int. If all those checks pass, > | then it defines _GLIBCXX_ATOMIC_BUILTINS and uses the definitions from > | ... 80 lines of the commit log omitted. > > Produces 11 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 (test for excess errors) > | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++26 (test for excess errors) > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 (test for excess errors) > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 (test for excess errors) > | ... and 7 more > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc master-arm_eabi > *configure and test flags:* --target arm-eabi > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1595. Please let us know if you have a fix. I've opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120567 for this. > > If you have any questions regarding this report, please ask on linaro-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_eabi-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_embed_check_gcc--master-arm_eabi-build/1… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=86627faec10da53d753280501…

2 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-1041-g2da641d0170: 5105 regressions on master-thumb_m33_hard_eabi

by H.J. Lu

On Wed, Jun 4, 2025 at 10:39 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. > > In arm-eabi cortex-m33 hard, after: > | commit gcc-16-1041-g2da641d0170 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Sun Jun 1 09:29:48 2025 +0800 > | > | Move get_call_rtx_from to final.c > | > | Move get_call_rtx_from to final.c and call call_from_call_insn. > | > | PR other/120493 > | ... 8 lines of the commit log omitted. > > Produces 5105 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/arm/cmse/cmse.exp ... > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler ands\tr0, r4 > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler ands\tr1, r4 > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler ands\tr2, r4 > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler bl\t__gnu_cmse_nonsecure_call > | ... and 5101 more > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m33 --with-float=hard --target_board=-mthumb/-march=armv8-m.main+dsp+fp/-mtune=cortex-m33/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m33 > Please try this. -- H.J.

2 months, 1 week

2
2
0 0

[Linaro-TCWG-CI] gcc-16-1028-g9739ae9384d: 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_kernel/gnu-master-aarch64-mainline-allmodconfig, after: | commit gcc-16-1028-g9739ae9384d | Author: Andrew Pinski <quic_apinski(a)quicinc.com> | Date: Thu May 29 23:50:08 2025 -0700 | | Have TODO_verify_* not set by any pass | | This is a follow up to the patch set starting at https://gcc.gnu.org/pipermail/gcc-patches/2014-April/386650.html. | | Currently TODO_verify_{il,all} is set by a few passes as TODOs afterwards but | ... 32 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 30 | # First few build errors in logs: | # 00:05:59 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:05:59 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:05:59 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 scripts/gcc-plugins/gcc-common.h:177:26: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 make[3]: *** [scripts/gcc-plugins/Makefile:54: scripts/gcc-plugins/latent_entropy_plugin.so] Error 1 | # 00:06:00 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:01 make[3]: *** [scripts/gcc-plugins/Makefile:54: scripts/gcc-plugins/stackleak_plugin.so] Error 1 | # 00:06:03 make[2]: *** [scripts/Makefile.build:461: scripts/gcc-plugins] Error 2 | | From | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 36872 | # linux build successful: | all Used configuration : tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig We track this bug report under https://linaro.atlassian.net/browse/GNU-1592. 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: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allmodco… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allmodco… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9739ae9384dd7cd3bb1c7683d…

2 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-13711-ga0d699a8e686: 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_vls-lto-lld, after: > | commit llvmorg-21-init-13711-ga0d699a8e686 > | Author: Slava Zakharin <szakharin(a)nvidia.com> > | Date: Wed May 28 17:18:04 2025 -0700 > | > | Reland "[flang] Added noalias attribute to function arguments. (#140803)" > | > | This helps to disambiguate accesses in the caller and the callee > | after LLVM inlining in some apps. I did not see any performance > | changes, but this is one step towards enabling other optimizations > | ... 14 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0122 ... > | FAIL: test-suite :: Fujitsu/Fortran/0122/Fujitsu-Fortran-0122_0045.test > | FAIL: test-suite :: Fujitsu/Fortran/0122/Fujitsu-Fortran-0122_0048.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-1691. 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/a0d699a8e686cba99690cf28463d145…

2 months, 2 weeks

1
0
0 0

RE: [Linaro-TCWG-CI] llvmorg-21-init-11733-g2d12d31f44ac: 3 regressions on aarch64

by Slava Zakharin

Hello, I think there was an error in bisecting these regressions. I can reproduce the same failure with commit 6dc6ca3302edadad7d4b195a05038995b84606d0, which happened before mine. Thanks, Slava -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Wednesday, May 21, 2025 9:10 PM To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com Cc: Slava Zakharin <szakharin(a)nvidia.com>; maxim.kuvyrkov(a)linaro.org Subject: [Linaro-TCWG-CI] llvmorg-21-init-11733-g2d12d31f44ac: 3 regressions on aarch64 [You don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] 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-Ofast-sve_vls-lto-lld, after: | commit llvmorg-21-init-11733-g2d12d31f44ac | Author: Slava Zakharin <szakharin(a)nvidia.com> | Date: Mon May 12 18:33:47 2025 -0700 | | [flang] Propagate contiguous attribute through HLFIR. (#138797) | | This change allows marking more designators producing an opaque | box with 'contiguous' attribute, e.g. like in test1 case | in flang/test/HLFIR/propagate-contiguous-attribute.fir. | ... 5 lines of the commit log omitted. Produces 3 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0105 ... | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0089.test | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0204.test | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0205.test | # "NOEXE" means : the test program cannot be compiled 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-1686. 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://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/2d12d31f44acac54d7b2858624cb8a1…

2 months, 3 weeks

3
3
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-12714-gd36028120a6e: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This regression is caused by a latent bug in the loop-interchange. I've confirmed https://github.com/llvm/llvm-project/pull/140709 fixes the bug. We'll wait for merge of https://github.com/llvm/llvm-project/pull/140709. You don't need to investigate this failure. Thanks. > 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-12714-gd36028120a6e > | Author: Sebastian Pop <spop(a)nvidia.com> > | Date: Wed May 21 08:27:39 2025 -0500 > | > | [flang] add -floop-interchange and enable it with opt levels (#140182) > | > | Enable the use of -floop-interchange from the flang driver. > | Enable in flang LLVM's loop interchange at levels -O2, -O3, -Ofast, and -Os. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0347 ... > | FAIL: test-suite :: Fujitsu/Fortran/0347/Fujitsu-Fortran-0347_0240.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-1687. 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://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/d36028120a6ef6346bfaafe82d4d1a2…

2 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-12430-g70501ed2f0f9: 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. 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-12430-g70501ed2f0f9 > | Author: Sam Tebbs <samuel.tebbs(a)arm.com> > | Date: Mon May 19 13:27:17 2025 +0100 > | > | [LoopVectorizer] Prune VFs based on plan register pressure (#132190) > | > | This PR moves the register usage checking to after the plans are > | created, so that any recipes that optimise register usage (such as > | partial reductions) can be properly costed and not have their VF pruned > | ... 3 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0340 ... > | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0076.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-1684. 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://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/70501ed2f0f9dc06baffa7ee124845e…

2 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-11722-gcf3242f3b0f6: 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. 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-11722-gcf3242f3b0f6 > | Author: Luke Lau <luke(a)igalia.com> > | Date: Tue May 13 02:11:55 2025 +0300 > | > | [InstCombine] Pull shuffles out of binops with splatted ops (#137948) > | > | Given a binary op on splatted vector and a splatted constant, > | InstCombine will normally pull the shuffle out in > | `InstCombinerImpl::foldVectorBinop`: > | ... 50 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0639 ... > | FAIL: test-suite :: Fujitsu/Fortran/0639/Fujitsu-Fortran-0639_0140.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-1681. 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://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/cf3242f3b0f6eec47786426777f6e0b…

2 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-372-g064cac730f8: 18 regressions on aarch64

by Sam James

See PR119930, PR120098, PR120101, PR120099.

3 months, 2 weeks

1
0
0 0

Windows builder issues

by Aaron Ballman

It looks like https://lab.llvm.org/buildbot/#/workers/149 is having problems: FAILED: bin/clang.exe C:\WINDOWS\system32\cmd.exe /C "cd . && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E vs_link_exe --intdir=tools\clang\tools\driver\CMakeFiles\clang.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests -- C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\lld-link.exe /nologo @CMakeFiles\clang.rsp /out:bin\clang.exe /implib:lib\clang.lib /pdb:bin\clang.pdb /version:0.0 /machine:ARM64 /STACK:10000000 /INCREMENTAL:NO /subsystem:console && C:\WINDOWS\system32\cmd.exe /C "cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang++.exe && cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang-cl.exe && cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang-cpp.exe"" LINK: command "C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\lld-link.exe /nologo @CMakeFiles\clang.rsp /out:bin\clang.exe /implib:lib\clang.lib /pdb:bin\clang.pdb /version:0.0 /machine:ARM64 /STACK:10000000 /INCREMENTAL:NO /subsystem:console /MANIFEST:EMBED,ID=1" failed (exit code 1) with the following output: lld-link: error: failed to write output 'bin\clang.exe': permission denied Any chance you can look into it? Thanks! ~Aaron

3 months, 2 weeks

2
2
0 0

Re: [Linaro-TCWG-CI] glibc patch #111247: 90 regressions on arm

by Stefan Liebler

Hi, For this V2-patch, I got the same "Operation not permitted" errors as for the V1 one: https://lists.linaro.org/archives/list/linaro-toolchain@lists.linaro.org/th… @Adhemerval: have you had a look? The only non-s390x changes of my patch are in: elf/Makefile elf/tst-glibc-hwcaps-cache.script => There the libmarkermod6 libraries are added. As I don't have an arm, I've checked on x86_64, that the testcase elf/tst-glibc-hwcaps-cache.c contains the libmarkermod6.so files in glibc-hwcaps/z13-z17 directories by adding a "ldconfig -p" to the test. Any idea why those "Operation not permitted" regressions hits my patch, but no others? Bye, Stefan On 4/30/25 20:19, 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 glibc_check master-arm, after: > | glibc patch https://patchwork.sourceware.org/patch/111247 > | Author: Stefan Liebler <stli(a)linux.ibm.com> > | Date: Tue Apr 29 13:28:58 2025 +0200 > | > | [PATCH v2] S390: Add new s390 platform z17. > | > | Hi, > | need a V2: stfle_bits on stack in init_cpu_features_no_tunables() needs to be > | zeroed before usage. If there is no more feedback, I will commit this patch shortly. > | ... 41 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 84977600dac math: Fix UB on sinpif (BZ 32925) > > Produces 90 regressions: > | > | regressions.sum: > | Running glibc:debug ... > | FAIL: debug/tst-fortify-syslog > | Running glibc:dirent ... > | FAIL: dirent/tst-readdir-long > | FAIL: dirent/tst-readdir-zero-inode > | ... and 99 more > > Used configuration : > *CI config* tcwg_glibc_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > 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_glibc_check--master-arm-precommit/3574/artif… > 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-precommit/3574/artif… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2743/artifact/… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

3 months, 2 weeks

2
1
0 0

Re: [Linaro-TCWG-CI] gdb patch #111028: 2 regressions on arm

by Tom de Vries

On 4/30/25 06: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 gdb_check master-arm, after: > | gdb patch https://patchwork.sourceware.org/patch/111028 > | Author: Tom de Vries <tdevries(a)suse.de> > | Date: Fri Apr 25 17:13:32 2025 +0200 > | > | [PATCH v2] [gdb/testsuite] Simplify gdb.tui/tui-layout-asm.exp > | > | On x86_64-cygwin, with test-case gdb.tui/tui-layout-asm.exp I run into: > | ... > | WARNING: The following failure is probably due to the TUI window > | ... 49 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 48d0ac705c4 Handle base type without DW_AT_byte_size > > Produces 2 regressions: > | > | regressions.sum: > | Running gdb:gdb.python/py-missing-objfile.exp ... > | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_exec_var > | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_lib_var > The FAILs are obviously unrelated to the patch which modifies a different test-case. But anyway, this a know PR ( https://sourceware.org/bugzilla/show_bug.cgi?id=32445 ). I've just committed a fix. Thanks, - Tom > Used configuration : > *CI config* tcwg_gdb_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > 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_gdb_check--master-arm-precommit/4439/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/4439/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > > Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/2666/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.

3 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-142-g01e5ef3e8b9: 2 regressions on arm

by Tomasz Kaminski

Hi, I have just pushed the following fix on trunk, that fixes a similar issue for 32bit x86_64. https://gcc.gnu.org/cgit/gcc/commit/?id=2ca5725e104d432317a44ad45183a4f555d… Please let me know if the build failure is addressed. Regards, Tomasz On Wed, Apr 30, 2025 at 5:14 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 gcc_check master-arm, after: > | commit gcc-16-142-g01e5ef3e8b9 > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Wed Apr 23 13:17:09 2025 +0200 > | > | libstdc++: Minimalize temporary allocations when width is > specified [PR109162] > | > | When width parameter is specified for formatting range, tuple or > escaped > | presentation of string, we used to format characters to temporary > string, > | and write produce sequence padded according to the spec. However, > once the > | ... 53 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: std/format/debug.cc -std=gnu++23 execution test > | FAIL: std/format/debug.cc -std=gnu++26 execution test > > 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-1571. 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_gcc_check--master-arm-build/3771/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/3771/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3771/artifact/ar… > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3771/artifact/ar… > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3770/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=01e5ef3e8b91288f5d387a277…

3 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gdb-16-branchpoint-1244-g5ea1eec52f4: 4 regressions 4 fixes on arm

by Tom de Vries

On 4/26/25 22: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. > > In master-arm, after: > | commit gdb-16-branchpoint-1244-g5ea1eec52f4 > | Author: Tom de Vries <tdevries(a)suse.de> > | Date: Wed Apr 9 08:59:42 2025 +0200 > | > | [gdb/tdep] Handle ldaex and stlex in {thumb,arm}_deal_with_atomic_sequence_raw > | > | The Linaro CI reported a regression [1] in test-case > | gdb.base/step-over-syscall.exp due to commit 674d4856730 ("[gdb/testsuite] Fix > | gdb.base/step-over-syscall.exp with glibc 2.41"). > | ... 100 lines of the commit log omitted. > > Produces 4 regressions 4 fixes: > | > | regressions.sum: > | Running gdb:gdb.base/step-over-syscall.exp ... > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: check_pc_after_cross_syscall: single step over fork final pc > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: pc after stepi matches insn addr after syscall > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: check_pc_after_cross_syscall: single step over fork final pc > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: pc after stepi matches insn addr after syscall > | > | fixes.sum: > | Running gdb:gdb.base/step-over-syscall.exp ... > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: continue to syscall insn fork (the program exited) > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: find syscall insn in fork > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: single step over fork (the program is no longer running) > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: break on syscall insn > Hi, I've looked at this, and AFAICT this is PR32817 ( https://sourceware.org/bugzilla/show_bug.cgi?id=32817 ). This is unrelated to the mentioned commit. Thanks, - Tom > 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-1570. 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/1993/… > 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/1993/… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/… > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1991/… > > Instruction to reproduce the build : 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=5ea1eec52f47f…

3 months, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-275-ge04afb7177: 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 master-aarch64, after: | commit glibc-2.41.9000-275-ge04afb7177 | Author: H. Peter Anvin <hpa(a)zytor.com> | Date: Fri Apr 25 07:30:59 2025 +0200 | | linux/termio: remove <termio.h> and struct termio | | The <termio.h> interface is absolutely ancient: it was obsoleted by | <termios.h> already in the first version of POSIX (1988) and thus | predates the very first version of Linux. Unfortunately, some constant | ... 15 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:08:58 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:489:31: error: invalid application of ‘sizeof’ to incomplete type ‘__sanitizer::termio’ | # 00:08:58 make[4]: *** [Makefile:627: sanitizer_platform_limits_posix.lo] Error 1 | # 00:08:58 make[3]: *** [Makefile:533: all-recursive] Error 1 | # 00:08:58 make[2]: *** [Makefile:420: all] Error 2 | # 00:08:58 make[1]: *** [Makefile:12800: all-target-libsanitizer] Error 2 | # 00:08:58 make: *** [Makefile:1064: 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-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1569. 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-aarch64-build/1084/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_build--master-aarch64-build/1084/a… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1084/a… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1083/a… 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=e04afb71771710cdc602…

3 months, 3 weeks

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain