linaro-toolchain

linaro-toolchain@lists.linaro.org

6 participants
5798 discussions

[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…

1 day, 6 hours

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.

1 day, 6 hours

[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…

5 days, 3 hours

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…

1 week

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

1 week, 1 day

Re: [Linaro-TCWG-CI] llvmorg-24-init-6625-gedbf358d0149: 4 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Thank you for your thorough investigation. As you pointed out, there was a problem with the tests. We will fix the tests. The tests fail because the comparison uses a relative tolerance of 1.0e-14, which is too strict for single-precision floating-point calculations, causing valid FP32 results such as 0.90000003 to be rejected when compared with the reference value 0.9. This issue is not due to actual computational errors caused by code generation or optimization, but rather a problem with the test configuration resulting from a double-precision tolerance being set for single-precision operations. The observed discrepancy is a rounding error of approximately 1 ULP, which falls within the normal range for single-precision operations. Therefore, it is appropriate to relax the comparison tolerance using TEST_SUITE_FP_TOLERANCE_FP32 (0x1.0p-22). Please ignore the mail. We'll update the tests. We apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: Newcombe, Caroline <caroline.newcombe(a)hpe.com> 送信: 2026 年 9 月 5 日 (土曜日) 5:12 宛先: linaro-toolchain(a)lists.linaro.org <linaro-toolchain(a)lists.linaro.org>; 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> 件名: Re: [Linaro-TCWG-CI] llvmorg-24-init-6625-gedbf358d0149: 4 regressions on aarch64 Thanks for your report. I think you’d need to add 0640_0214, 0640_0215, 0640_0223 and 0640_0224 to Fujitsu/Fortran/0640/fpconfig.cmake with TEST_SUITE_FP_TOLERANCE_FP32. Alternatively, applying -fno-reciprocal-math to these tests should also take care of the discrepancy in results. All four print REAL*4 values but are currently graded against the directory default FP_TOLERANCE, which is derived from the FP64 constants, so 1.0e-14 with TEST_SUITE_FUJITSU_WITH_FAST_MATH=ON and 0x1.0p-51 without. Testing on aarch64 with the fast-math configuration, I see a single REAL*4 value change in each of them, from .9 to .90000003. That is one ULP of binary32 arising from reciprocal substitution on 9.0/10.0: the correctly rounded quotient is 0x3F666666, or 0.899999976, while 9.0f * (1.0f/10.0f) rounds to 0x3F666667, or 0.900000036. The relative difference is 6.6e-8, roughly six orders of magnitude above the tolerance being applied, so the comparison fails even though the result is within one ULP. Some of the outputs also show REAL*8 values shifting by one ULP, for instance .6 to .6000000000000001, but those are around 1.8e-16 and pass comfortably. Since -freciprocal-math is implied by -ffast-math, which this configuration uses, the substitution is permitted and I don't think the new value should be treated as incorrect. TEST_SUITE_FP_TOLERANCE_FP32 is 2.38e-7, which covers the new test results. It appears the tests have been passing just because the reciprocal substitution happened not to fire. My recent change to Flang enables the FIR loop invariant code motion pass by default. The pass perturbs the IR enough that the cost model's reciprocal decision flips, resulting in the slight difference to reference output. Best, Caroline From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Thursday, September 3, 2026 at 5:25 PM To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: Newcombe, Caroline <caroline.newcombe(a)hpe.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> Subject: [Linaro-TCWG-CI] llvmorg-24-init-6625-gedbf358d0149: 4 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-Ofast-sve_vla, after: | commit llvmorg-24-init-6625-gedbf358d0149 | Author: Caroline Newcombe <caroline.newcombe(a)hpe.com> | Date: Mon Aug 31 11:20:03 2026 -0400 | | [flang] Enable FIR loop invariant code motion by default (#218703) | | The FIR loop invariant code motion pass was added in #173438, where it | was disabled by default. This enables it for optimization levels above | `-O0`. The option `-disable-fir-licm` has been added in place of | ... 5 lines of the commit log omitted. Produces 4 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0640 ... | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0214.test | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0215.test | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0223.test | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0224.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://urldefense.com/v3/__https://linaro.atlassian.net/browse/LLVM-2272__… . (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 * https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-… The full lists of regressions and improvements as well as configure and make commands are in * https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-… The list of [ignored] baseline and flaky failures are in * https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-… Reference build : https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-… Instruction to reproduce the build : https://urldefense.com/v3/__https://gitlab.com/LinaroLtd/tcwg/ci/interestin… Full commit : https://github.com/llvm/llvm-project/commit/edbf358d014942a17953c3ccfcf9f20…

1 week, 1 day

Re: [Linaro-TCWG-CI] llvmorg-24-init-6563-ge448a895252d: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, We investigated the failure and confirmed that it is caused by an overly strict floating-point tolerance in the test. After the LoopInterchange-related optimization changes, the order of some floating-point operations differs, producing small rounding differences typical of single-precision arithmetic. The observed relative error is approximately 2.8e-7, which is reasonable for REAL*4 calculations. The test currently uses a tolerance equivalent to double-precision accuracy, so we plan to update the test tolerance to an appropriate single-precision value (1.0e-6). 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 月 1 日 (火曜日) 20:11 宛先: 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>; madhura(a)nvidia.com <madhura(a)nvidia.com> 件名: [Linaro-TCWG-CI] llvmorg-24-init-6563-ge448a895252d: 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-6563-ge448a895252d | Author: Madhur Amilkanthwar <madhura(a)nvidia.com> | Date: Mon Aug 31 09:56:48 2026 +0530 | | [Clang][Flang] Enable loop interchange by default at >O1 opt levels (#216920) | | PR #124911 enabled the LoopInterchange pass by default in the LLVM | optimization pipeline (the PipelineTuningOptions default used by opt), | but the clang and flang frontends override that default and keep it off. | ... 15 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0344 ... | FAIL: test-suite :: Fujitsu/Fortran/0344/Fujitsu-Fortran-0344_0317.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-2269. (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/e448a895252d5dd74f85450a2b1438e…

1 week, 5 days

Re: [Linaro-TCWG-CI] 2025-09-68-g2d608e140: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, This is the test-suite issue rather than the compiler defect. The source code contains an inconsistent declaration for src2, and the failure became visible after removal of the option that suppressed incompatible pointer type diagnostics. 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月2日 11:26 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> CC: 114733434+ohno-fj(a)users.noreply.github.com <114733434+ohno-fj(a)users.noreply.github.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> 件名: [Linaro-TCWG-CI] 2025-09-68-g2d608e140: 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-O0-debug, after: | commit 2025-09-68-g2d608e140 | Author: ohno-fj <114733434+ohno-fj(a)users.noreply.github.com> | Date: Tue Sep 1 08:01:57 2026 +0900 | | Workitem 16933_0002 (for GCC) (#131) | | Co-authored-by: ohno <ohno.yasuyuki(a)jp.fujitsu.com> Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/C/0002 ... | NOEXE: test-suite :: Fujitsu/C/0002/Fujitsu-C-0002_0050.test | # "NOEXE" means : the test program cannot be compiled 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="-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-2271. (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-O0-debug-build… 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-O0-debug-build… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/fujit… Full commit : https://github.com/fujitsu/compiler-test-suite/commit/2d608e140687b2b0de363…

1 week, 5 days

[Linaro-TCWG-CI] glibc-2.44.9000-140-ged0c137b97e: 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-140-ged0c137b97e | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Mon Aug 17 15:15:32 2026 -0300 | | elf: Open the normalized $\ORIGIN rpath in AT_SECURE programs (BZ 34360) | | For AT_SECURE programs the loader honors $\ORIGIN in DT_RPATH only when the | expansion is rooted in a trusted directory, but it validated the lexically | normalized path while opening the raw expansion. As "a/b/../c" only names | ... 13 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-origin-secure 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-2016. (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=ed0c137b97eb940b4b64…

1 week, 6 days

[Linaro-TCWG-CI] glibc-2.44.9000-126-gd179e02998c: 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 aarch64 native, after: | commit glibc-2.44.9000-126-gd179e02998c | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Tue Jul 28 18:13:22 2026 -0300 | | elf: Allow RPATH/RUNPATH for static-pie (BZ 33326) | | The initial static-pie support (commit 9d7a3741c9e59eba87fb) reused | ld.so ELF parsing logic, even though RPATH/RUNPATH should not appear | in the static-pie bootstrap. With static PIE, RPATH/RUNPATH on the | ... 15 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-pie-rpath-static Used configuration : *CI config* tcwg_gnu_native_check_glibc aarch64-linux-gnu *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a We track this bug report under https://linaro.atlassian.net/browse/GNU-2015. (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_gnu_native_check_glibc--master-aarch64-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… 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=d179e02998ce31c93436…

1 week, 6 days

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain