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…
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.
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…
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
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…
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…
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…
Hi,
The failures were caused by re-applying the LLVM change introduced by commit(efd053f8ef306e6fa21ab0cd1bd185ef48f09fc0).
Although the change had previously been reverted due to regression failures, it was later re-applied unchanged by commit(44ea65c07a600ca1c32912b5cd7356f6792b2b03). This reintroduced the same failures that had already been reported in LLVM-2266.
The issue has already been addressed as part of the resolution for LLVM-2266, and the corresponding fix was committed in:
https://dev.azure.com/miratech-soft/b6c3f009-db3a-422a-91be-d5c0809bb862/_g…
Please ignore the mail.
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年8月28日 1:43
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: rupprecht(a)google.com <rupprecht(a)google.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-6091-g44ea65c07a60: 3 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_vls-lto-lld, after:
| commit llvmorg-24-init-6091-g44ea65c07a60
| Author: Jordan Rupprecht <rupprecht(a)google.com>
| Date: Wed Aug 26 13:02:20 2026 -0500
|
| Re-apply "[PromoteMemToReg] Insert store undef when removing lifetime markers" (#218935)
|
| Reapplies #191909 / reverts #218804
|
| Re-apply as-is. The issues were downstream and have been since fixed.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C++/0041 ...
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0335.test
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0337.test
| Running test-suite:Fujitsu/C/0096 ...
| FAIL: test-suite :: Fujitsu/C/0096/Fujitsu-C-0096_0358.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=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -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-2267. (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_vls-…
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_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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/44ea65c07a600ca1c32912b5cd7356f…
Hi,
These tests are incorrect. Therefore, we will correct the tests.
Details are as follows.
Investigation shows that all failures are caused by assumptions in the test programs rather than compiler defects.
Two independent issues were identified.
Issue 1: Fujitsu-C-0060_0008.test and Fujitsu-C-0076_0009.test
These tests use NaN/Infinity related computations while being compiled with -ffast-math.
The source files explicitly enable:
- -fhonor-nans
but do not enable:
- -fhonor-infinities
As a result, optimizations assuming that infinities are not significant remain legal under -ffast-math.
Fujitsu-C-0060_0008.test generates Inf and -Inf through division by zero and compares them against expected values. The test assumes IEEE infinity semantics are preserved, but the compilation options do not require that behavior.
Fujitsu-C-0076_0009.test exhibits the same problem.
Issue 2: Fujitsu-Fortran-0311_0026.test
This test uses Cray pointers and an allocatable array that shares the same storage.
However, the allocatable arrays participating in the aliasing relationship do not have the TARGET attribute.
Under Flang's documented aliasing rules for Cray pointers, optimizations may assume that Cray-pointer targets do not alias ordinary variables unless the aliased variables are declared with the TARGET attribute.
Consequently, the optimizer may legally treat the two objects as non-aliasing despite referring to the same storage at runtime.
The failure therefore originates from the test program not expressing the required aliasing relationship.
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 年 8 月 29 日 (土曜日) 16:20
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: jfargnoli(a)nvidia.com <jfargnoli(a)nvidia.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-6257-gc47197af5327: 3 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_vls-lto-lld, after:
| commit llvmorg-24-init-6257-gc47197af5327
| Author: Justin Fargnoli <jfargnoli(a)nvidia.com>
| Date: Thu Aug 27 13:03:39 2026 -0700
|
| [LTO] Enable `PrepareForLTO` for loop unrolling in pre-link pipelines (#192155)
|
| Currently, the unroller will not unroll loops with inlineable calls.
| However, calls that may not appear to be inlineable during the pre-link
| phase may become inlineable during the post-link phase. The unroller's
| ... 4 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0060 ...
| FAIL: test-suite :: Fujitsu/C/0060/Fujitsu-C-0060_0008.test
| Running test-suite:Fujitsu/C/0076 ...
| FAIL: test-suite :: Fujitsu/C/0076/Fujitsu-C-0076_0009.test
| Running test-suite:Fujitsu/Fortran/0311 ...
| ... and 1 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 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -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-2268. (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_vls-…
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_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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/c47197af53270a4795040756c27802f…
Hi,
I believe these may be flaky since I checked with my 4 patches on
cfarm185 machine with following configure command
configure --prefix=/home/avinashd/opt --enable-languages=c,c++ --
target=aarch64-unknown-linux-gnu --disable-multilib --enable-fix-
cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --
disable-bootstrap
on top of the commit
a5da203dd95900ba8bab16432667989f3d018c76 : xtensa: Make use of CONST.S
instruction
On Fri, 2026-08-28 at 22:17 +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.
>
> In aarch64 native, after:
> | 4 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/142333
> | 25ff335aad8 [PATCH 4/4] rs6000: Add sha3 builtins and
> documentation [RFC02645]
> | f47d33c1b4e [PATCH 3/4] rs6000: Add __dmr2048 type (QDOmode) and
> map it to DMR pair register
> | 1eb45af654c [PATCH 2/4] genmodes: Use wider types for
> mode_unit_size array based on max size
The only change in middle-end that has happened is with this patch
(2/4). And that is to generate the macro MODE_UNIT_SIZE_TYPE instead of
unsigned char. This should not have caused the below mentioned
regressions. All other patches are rs6000 backend related.
Please let me know if these regressions are always reproducible or if I
have tested it incorrectly on the cfarm185 machine. I can have a look
at what is happening.
Thanks,
Avinash Jayakar
> | 63b651a8d8f [PATCH 1/4] rs6000: Add sha2 and shapad builtins
> [RFC02645]
> | ... applied on top of baseline commit:
> | aaa0f6b1e87 match.pd: fold reductions of vector duplicates and
> repeats [PR127039]
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0
> in branch percentages, 0 in condition/decision, 1 in prime-paths, 0
> in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered
> paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check 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
>
> 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-aarch64-precommit/bui…
> 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-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
My changes are PowerPC specific, I don't understand how aarch64 failures
are due to my changes.
| FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
| FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
Should I wait for another build? or try to reproduce this issue on cfram
machine (Aarch64) ?
Thanks,
Manjunath S Matti.
On 24/08/26 6:05 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 aarch64 native, after:
> | gcc patch https://patchwork.sourceware.org/patch/142026
> | Author: Manjunath S Matti <mmatti(a)linux.ibm.com>
> | Date: Sun Aug 23 10:57:59 2026 -0500
> |
> | [PATCH] rs6000: Fix ICE with __int128 vector built-ins and -mno-vsx [PR126512]
> |
> | The changes have been bootstrapped and regression tested on
> | powerpc64le-linux and powerpc64-linux.
> |
> | ... 29 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 1ccae7a1e12 AVR: target/127024 - Fix build warning: skipping two-word instruction
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check 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
>
> 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-aarch64-precommit/bui…
> 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-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
No, this isn't plausible. The maintainer_utils changes have no effect at all on the compiler. So there must be some other cause.
R.
On 21/08/2026 15:45, 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 aarch64 native, after:
> | 5 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/141841
> | 237059276db [PATCH v1 5/5] maintainer_utils: more array size verification.
> | 4891de9f00a [PATCH v1 4/5] maintainer_utils: Ensure the list of user data is sorted.
> | f18b6593669 [PATCH v1 3/5] maintainer_utils: Move DCO entries outside of roles.
> | 3126c9b698f [PATCH v1 2/5] maintainer_utils: Fix errors in schema.
> | 9145fb8e995 [PATCH v1 1/5] maintainer_utils.py: Add a store method
> | ... applied on top of baseline commit:
> | de8bbe99481 Add fixme comment to vect_slp_node_weight and containing_loop
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check 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
>
> 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-aarch64-precommit/bui…
> 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-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
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.
Hi,
Two independent failures were observed in the test-suite.
Both failures are caused by pre-existing undefined behavior in the test programs:
1. Accessing elements through a std::initializer_list after the lifetime of its backing temporary array has ended.
2. Reading uninitialized automatic variables.
The commit (efd053f) merely exposed these latent issues through improved lifetime-aware optimization.
Therefore, this is the test-suite issue, not a compiler defect.
Please ignore the mail. We will 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年8月21日 21:40
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: isoard(a)amd.com <isoard(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-4794-gefd053f8ef30: 3 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_vls-lto-lld, after:
| commit llvmorg-24-init-4794-gefd053f8ef30
| Author: Alexandre Isoard <isoard(a)amd.com>
| Date: Tue Aug 18 07:36:19 2026 -0700
|
| [PromoteMemToReg] Insert store undef when removing lifetime markers (#191909)
|
| The `lifetime.start` and `lifetime.end` can help avoid the creation of
| spurious phi-node.
|
| ... 20 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C++/0041 ...
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0335.test
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0337.test
| Running test-suite:Fujitsu/C/0096 ...
| FAIL: test-suite :: Fujitsu/C/0096/Fujitsu-C-0096_0358.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=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -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-2266. (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_vls-…
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_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
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/efd053f8ef306e6fa21ab0cd1bd185e…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-arm_eabi, after:
| commit v11.1.0-302-g288d39e26d4
| Author: Richard Henderson <richard.henderson(a)linaro.org>
| Date: Mon Aug 10 09:08:31 2026 -0700
|
| tcg: Simplify bswap/hswap expansion using bitswap
|
| Reviewed-by: Philippe Mathieu-Daudé <philmd(a)oss.qualcomm.com>
| Signed-off-by: Richard Henderson <richard.henderson(a)linaro.org>
Produces 14 regressions:
|
| regressions.sum:
| Running gcc:gcc.target/aarch64/advsimd-intrinsics/advsimd-intrinsics.exp ...
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O0 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O1 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O2 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
| ... and 11 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-2006. (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_embed_check_gcc--master-arm_eabi-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_gnu_embed_check_gcc--master-arm_eabi-bu…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/…
Full commit : https://gitlab.com/qemu-project/qemu/commit/288d39e26d48ed26e4f786ddb3a25ee…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 cross, after:
| commit binutils-2_41-release-11539-gb04b71c9f4b
| Author: Alan Modra <amodra(a)gmail.com>
| Date: Thu Aug 6 11:17:25 2026 +0930
|
| prepare stub bfd for use as dynobj
|
| There are a few wrinkles to using the stub bfd. Target code that
| assumes the stub bfd sections are all stub sections must be corrected
| to test SEC_LINKER_CREATED. Those without the flag are stub sections,
| ... 34 lines of the commit log omitted.
Produces 5 regressions:
|
| regressions.sum:
| Running g++:g++.dg/asan/asan.exp ...
| FAIL: c-c++-common/asan/pr59063-2.c -O2 execution test
| FAIL: c-c++-common/asan/pr59063-2.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
| FAIL: c-c++-common/asan/pr59063-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
| FAIL: c-c++-common/asan/pr59063-2.c -O3 -g execution test
| ... and 1 more
Used configuration :
*CI config* tcwg_gnu_cross_check_gcc aarch64-linux-gnu cross
*configure and test flags:* --target aarch64-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-2004. (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_cross_check_gcc--master-aarch64-bui…
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_cross_check_gcc--master-aarch64-bui…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
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=b04b71c9f4bba…
Hi,
Investigation showed that the test programs explicitly specify both always_inline and noinline on the same function.
Since these attributes have contradictory semantics, the new diagnostic correctly reports an error.
Therefore, this is a test-suite issue rather than a compiler bug.
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 年 8 月 17 日 (月曜日) 13:19
宛先: 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>; 76546742+ketjandr(a)users.noreply.github.com <76546742+ketjandr(a)users.noreply.github.com>
件名: [Linaro-TCWG-CI] llvmorg-24-init-4536-g6a2d309c7d20: 2 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-O0-debug, after:
| commit llvmorg-24-init-4536-g6a2d309c7d20
| Author: Kenzo Tjandra <76546742+ketjandr(a)users.noreply.github.com>
| Date: Sun Aug 16 12:16:01 2026 -0400
|
| [Clang] Diagnose conflict between always_inline/noinline attributes (#215173)
|
| This PR aims to diagnose `always_inline` and `noinline` conflicts which
| currently could pass silently through `Sema` or cause a crash (with
| assertions enabled). Changes include:
| ... 17 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0077 ...
| NOEXE: test-suite :: Fujitsu/C/0077/Fujitsu-C-0077_0032.test
| NOEXE: test-suite :: Fujitsu/C/0077/Fujitsu-C-0077_0033.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-2264. (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/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/6a2d309c7d204730a9a35f3261f8448…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 native, after:
| commit binutils-2_41-release-11540-ge189bfd9b49
| Author: Alan Modra <amodra(a)gmail.com>
| Date: Thu Aug 6 11:17:38 2026 +0930
|
| use linker created stub bfd for dynobj
|
| A linker created bfd is a good choice for somewhere to attach linker
| created dynamic sections. It is always the correct format and doesn't
| have anything other than linker generated info to potentially confuse
| ... 86 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| # FAILED
| # build_abe linux:
| # build_abe glibc:
| # build_abe gdb:
| # First few build errors in logs:
| # 00:16:11 make[3]: *** [../gcc-interface/Makefile:467: common-tools] Error 1
| # 00:16:11 make[2]: *** [Makefile:197: gnattools-native] Error 2
| # 00:16:11 make[1]: *** [Makefile:10774: all-gnattools] Error 2
| # 00:16:11 make: *** [Makefile:1102: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| 2
| # build_abe linux:
| 4
| # build_abe glibc:
| # FAILED
| # build_abe gdb:
Used configuration :
*CI config* tcwg_gnu_native_build 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-1999. (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
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_build--master-aarch64-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_gnu_native_build--master-aarch64-build/…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_build--master-aarch64-build/…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_build--master-aarch64-build/…
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=e189bfd9b492a…