linaro-toolchain

linaro-toolchain@lists.linaro.org

8 participants
5800 discussions

[Linaro-TCWG-CI] glibc-2.44.9000-218-g371d58d11bf: 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.44.9000-218-g371d58d11bf | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Mon Aug 31 13:09:37 2026 -0300 | | posix: Add POSIX posix_spawn_file_actions_add{,f}chdir | | Use proper symbols instead of alias to the *_np counterpart. | | The declarations are also moved from __USE_XOPEN2K24XSI to | ... 5 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-valgrind-smoke 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-2051. (Require Linaro login) 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: Details of the regressions above, from the testsuite logs: | FAIL: elf/tst-valgrind-smoke | original exit status 1 | /usr/bin/valgrind | /lib/ld-linux-armhf.so.3 | bin: /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/valgrind-test | ld.so: /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/ld.so You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=371d58d11bf7aacd4bf4…

1 day, 12 hours

Re: [Linaro-TCWG-CI] llvmorg-24-init-10324-gfa939745e0ac: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, This test is incorrect. This is a test configuration issue caused by an inappropriate floating-point tolerance setting. Updating the test to use the standard FP32 tolerance resolves the failure while preserving the intended validation of single-precision numerical results. Please ignore the mail. We'll update the test. We apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信日時: 2026年9月27日 2:46 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> CC: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; a.bataev(a)outlook.com <a.bataev(a)outlook.com> 件名: [Linaro-TCWG-CI] llvmorg-24-init-10324-gfa939745e0ac: 1 regression on aarch64 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-24-init-10324-gfa939745e0ac | Author: Alexey Bataev <a.bataev(a)outlook.com> | Date: Wed Sep 23 14:33:54 2026 -0400 | | [SLP]Pair small sign-aware reduction groups only if both signs have one | | The small-group check of the flattened fsub/fneg fadd reductions | used whenever any leaf was negated, vectorizing 2-wide parts that | have no opposite-sign part to combine with via the vector fsub. | ... 5 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0680 ... | FAIL: test-suite :: Fujitsu/Fortran/0680/Fujitsu-Fortran-0680_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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/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 -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2284. (Require Linaro login) 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 * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/fa939745e0aceb6cd92debec4badd42…

1 day, 22 hours

Re: [Linaro-TCWG-CI] llvmorg-24-init-8067-gf40e465b112a: 13 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, These tests are incorrect. Therefore, we will correct the tests. The investigation concluded that all 13 failures are caused by expected floating-point precision differences introduced by reassociation enabled by commit #222302. No compiler malfunction was identified. The affected test cases contain overly strict or incorrect tolerance settings and should be updated accordingly. Please ignore the mail. We'll update the test. We apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信日時: 2026年9月14日 1:44 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> CC: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; tom.eccles(a)arm.com <tom.eccles(a)arm.com> 件名: [Linaro-TCWG-CI] llvmorg-24-init-8067-gf40e465b112a: 13 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-24-init-8067-gf40e465b112a | Author: Tom Eccles <tom.eccles(a)arm.com> | Date: Wed Sep 9 17:20:24 2026 +0100 | | [flang] Ignore subscript conversions when reassociating sums (#222302) | | Implicit conversions of INTEGER(4) array indices to SubscriptInteger | were treated as conversions in the surrounding floating-point sum, | preventing reassociation of ordinary array-element expressions. | ... 6 lines of the commit log omitted. Produces 13 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0340 ... | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0099.test | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0117.test | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0181.test | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0185.test | ... and 15 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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2276. (Require Linaro login) 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 * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/f40e465b112a1a0cc1f6f544b33f356…

5 days, 4 hours

[Linaro-TCWG-CI] glibc-2.44.9000-175-g8f50cdcb631: 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.44.9000-175-g8f50cdcb631 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Wed Sep 9 15:43:05 2026 -0300 | | linux: Use __libc_procmaps_iterate on __readonly_area_fallback | | Instead of stdio and __getdelim, which removes the malloc usage from | the fortify %n check path. The closure now only checks the mapping | address range and permissions, with the line parsing done by | ... 7 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-valgrind-smoke 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-2040. (Require Linaro login) 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: Details of the regressions above, from the testsuite logs: | FAIL: elf/tst-valgrind-smoke | original exit status 1 | /usr/bin/valgrind | /lib/ld-linux-armhf.so.3 | bin: /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/valgrind-test | ld.so: /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/ld.so You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=8f50cdcb6318c6e34cce…

1 week, 6 days

[Linaro-TCWG-CI] glibc-2.44.9000-164-gfa91c51bb7b: 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.44.9000-164-gfa91c51bb7b | Author: Shamil Abdulaev <ashamil435(a)gmail.com> | Date: Fri Sep 11 14:59:48 2026 +0200 | | elf: Do not load cache extensions from an old-format ld.so.cache [BZ #34600] | | Since b9957a70b8 the cache extensions are loaded in | _dl_maybe_load_ldsocache. A cache written by "ldconfig -c old" has no | new-format header, so tmp_cache_new is NULL there and | ... 9 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-dl-cache-old-format 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-2034. (Require Linaro login) 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 * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=fa91c51bb7bdd47ba4a1…

2 weeks, 1 day

Re: [Linaro-TCWG-CI] llvmorg-24-init-8067-gf40e465b112a: 13 regressions on aarch64

by Tom Eccles

Thank you for pointing out the issue. I believe this is a problem with the Fujistu test suite. I’ve created an issue there https://github.com/fujitsu/compiler-test-suite/issues/147 The fortran standard explicitly allows reassociation of floating point operations within a single programming language statement. The tests are too strict, passing only for strict left-to-write lowering of all floating point expressions. As discussed in the RFC, https://discourse.llvm.org/t/rfc-flang-reasssociate-within-real-and-complex… this was expected. The only difference was that with this more recent patch more tests than I anticipated were affected. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Sunday, 13 September 2026 at 17:45 To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; Tom Eccles <Tom.Eccles(a)arm.com> Subject: [Linaro-TCWG-CI] llvmorg-24-init-8067-gf40e465b112a: 13 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-24-init-8067-gf40e465b112a | Author: Tom Eccles <tom.eccles(a)arm.com> | Date: Wed Sep 9 17:20:24 2026 +0100 | | [flang] Ignore subscript conversions when reassociating sums (#222302) | | Implicit conversions of INTEGER(4) array indices to SubscriptInteger | were treated as conversions in the surrounding floating-point sum, | preventing reassociation of ordinary array-element expressions. | ... 6 lines of the commit log omitted. Produces 13 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0340 ... | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0099.test | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0117.test | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0181.test | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0185.test | ... and 15 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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2276. (Require Linaro login) 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 * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/f40e465b112a1a0cc1f6f544b33f356… 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.

2 weeks, 1 day

Re: [Linaro-TCWG-CI] glibc patch #143640: 2 regressions 99 fixes on aarch64

by Aurelien Jarno

Hi, On 2026-09-13 01: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 glibc_check master-aarch64, after: > | glibc patch https://patchwork.sourceware.org/patch/143640 > | Author: Aurelien Jarno <aurelien(a)aurel32.net> > | Date: Sat Sep 12 13:34:20 2026 +0200 > | > | [PATCH] x86_64/cet: fix tst-shstk-legacy-1{f,g} tests [BZ #31877] > | > | The tst-shstk-legacy-1f and tst-shstk-legacy-1g tests depend on the > | tst-shstk-legacy-mod-1.so module to test that legacy shadow stack code > | in init_array does not trigger a segfault in tst-shstk-legacy-1f, while > | ... 6 lines of the commit log omitted. > | ... applied on top of baseline commit: > | fa91c51bb7 elf: Do not load cache extensions from an old-format ld.so.cache [BZ #34600] This patch only changes files in sysdeps/x86_64, so I really doubt in causes issues for the aarch64 build. Could you please retry? Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien(a)aurel32.net http://aurel32.net

2 weeks, 2 days

[Linaro-TCWG-CI] binutils-2_41-release-11802-gfe54f17b832: 1 regression 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 binutils_check master-aarch64, after: | commit binutils-2_41-release-11802-gfe54f17b832 | Author: Alan Modra <amodra(a)gmail.com> | Date: Thu Sep 10 18:05:39 2026 +0930 | | ld-elf shared.exp | | Don't "return" when no CXX, disabling numerous later non-c++ tests. | Enable "Run with libdl3b.so" too. | | ... 4 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running ld:ld-elf/shared.exp ... | FAIL: Run with libdl3b.so Used configuration : *CI config* tcwg_binutils_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-2029. (Require Linaro login) 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 * http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… Current build : http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… Reference build : http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=fe54f17b832ba…

2 weeks, 5 days

Re: [Linaro-TCWG-CI] llvmorg-24-init-7065-g70d088d10d20: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, This test is incorrect. Therefore, we will correct the test. The issue became visible after LLVM commit(70d088d) changed symbol resolution behavior to prefer a specific procedure defined in a generic interface over an explicitly declared intrinsic procedure. As a result, int(1,1), which had previously been resolved as the intrinsic function INT(A,KIND), is now resolved as ifunc01(1,1). Consequently, its result changes from 1 to 2. Because the test still assumes the previous behavior and retains the corresponding expected output, the failure is exposed. To address this issue, the test should be updated to verify the results of the intrinsic function INT and the specific procedure ifunc01 independently. Before: if (int(1).ne.int(1,1)) print *,'error' After: if (int(1).ne.1) print *,'erro*' if (*nt(1,1).ne.2) print *,'error' This change explicitly verifies that the intrinsic function INT returns 1 and that the specific procedure ifunc01 associated with the generic interface returns 2, eliminating the dependency on the previous symbol resolution behavior. Please ignore the mail. We'll update the test. We apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信: 2026 年 9 月 4 日 (金曜日) 21:34 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; ali.bahrani94521036(a)gmail.com <ali.bahrani94521036(a)gmail.com> 件名: [Linaro-TCWG-CI] llvmorg-24-init-7065-g70d088d10d20: 1 regression on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-24-init-7065-g70d088d10d20 | Author: Ali Bahrani <ali.bahrani94521036(a)gmail.com> | Date: Wed Sep 2 13:40:28 2026 -0400 | | [Flang] Interface vs explicit intrinsics priority (#215355) | | Updated `ExpressionAnalyzer::ResolveGeneric` method to prioritize | internal interface definition over explicit intrinsic in symbol resolution. | | ... 4 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0625 ... | FAIL: test-suite :: Fujitsu/Fortran/0625/Fujitsu-Fortran-0625_0035.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;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -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/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2273. (Require Linaro login) 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 * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/70d088d10d207483dca826b5f51ee9d…

3 weeks, 1 day

Re: [Linaro-TCWG-CI] gcc-17-3926-g93ac5163b5d: 3 regressions on arm

by Richard Earnshaw (foss)

On 05/09/2026 09:06, 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 armv8l-unknown-linux-gnueabihf native, after: > | commit gcc-17-3926-g93ac5163b5d > | Author: Dominic P <gcc(a)gcc.dp11.uk> > | Date: Sun Aug 2 11:56:05 2026 +0100 > | > | arm: fix vshll_n intrinsics with boundary shift [PR111609] > | > | The NEON widening-shift-left-long intrinsics (vshll_n_s8/s16/s32 and > | vshll_n_u8/u16/u32) accept a shift amount in the range [0, element_size]. > | The bounds check in neon_vshll<sup>_n<mode> already permits a shift of > | ... 32 lines of the commit log omitted. > > Produces 3 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/vfp-shift-a2t2.c scan-assembler vshll.u16[ \t]+[qQ][0-9]+, [dD][0-9]+, #[0-9]+!?([ \t]+@[a-zA-Z0-9 ]+)?\n > | FAIL: gcc.target/arm/vfp-shift-a2t2.c scan-assembler vshll.u32[ \t]+[qQ][0-9]+, [dD][0-9]+, #[0-9]+!?([ \t]+@[a-zA-Z0-9 ]+)?\n > | FAIL: gcc.target/arm/vfp-shift-a2t2.c scan-assembler vshll.u8[ \t]+[qQ][0-9]+, [dD][0-9]+, #[0-9]+!?([ \t]+@[a-zA-Z0-9 ]+)?\n > Fixed. R. > Used configuration : > *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --with-fpu=neon-fp-armv8 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-2020. (Require Linaro login) 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 > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1062… > The full lists of regressions and improvements as well as configure and make commands are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1062… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1062… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1062… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1062… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

3 weeks, 1 day

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain