Hi,
thanks for the report. I looked into this and I dont think my patch is
actually responsible for these failures. The gcov-39.c prime-paths test
seems to be a pre-existing flaky test rather than something introduced by
my changes — my patch only touches the tree optimization path (final value
replacement logic) and has no interaction with gcov instrumentation or path
coverage counting.
Could someone check if this failure shows up in the baseline as well?
Happy to dig deeper if needed, but from what I can see this looks unrelated
to my patch.
Thanks
---------
Lunex<imlunex2011(a)gmail.com>
> From: ci_notify(a)linaro.org
> Date: Thu, 27 Aug 2026 14:30:00 +0000 (UTC)
> Reply-To: linaro-toolchain(a)lists.linaro.org
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
My manual investigation process has detected a problem with that
conclusion, and ditto.
> In aarch64 native, after:
> | gcc patch https://patchwork.sourceware.org/patch/142242
> | Author: Hans-Peter Nilsson <hp(a)axis.com>
> | Date: Wed Aug 26 15:16:16 2026 +0200
> |
> | NOT vs. ROTATE (was: [CRIS PATCH] Support bitreverse32, rotatesi3_16 and other swap variants.)
> |
> | > From: Hans-Peter Nilsson <hp(a)axis.com>
> | > Date: Tue, 25 Aug 2026 17:50:01 +0200
> |
> | ... 36 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | d9dcc189896 fortran: array descriptor: Move dtype layout constants out of header [PR122521]
>
> 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
That's quite unlikely, as that message was a suggestion for a
documentation patch that touched only gcc/doc/md.texi.
I have a hunch gcc.misc-tests/gcov-39.c is flaky, if not generally
then at least in the context of your CI. I suggest you consider
filtering out that test until your human resources has investigated
the flakiness.
> 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.
brgds, H-P
Hello Linaro CI Team,
This looks unrelated to the patch. It only defines LINK_SSP_SPEC inside the DEFAULT_LIBC == LIBC_MUSL block of gcc/config/linux.h
plus two rs6000 headers, so nothing from it is compiled into an aarch64-linux-gnu build. To be sure I built aarch64-linux-gnu
cross compilers from master with and without the patch using the same configure flags as this CI, and xgcc -dumpspecs output is
byte-identical, while the same tree targeted at aarch64-linux-musl does show the new -lssp_nonshared spec.
The failing test is a gcov prime-paths count, and the build's own results.compare.txt says
"No regression found in 3 common sum files". Happy to dig further if anyone sees a connection I am missing.
Thanks,
Sunil Dora
________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Tuesday, September 1, 2026 10:48 AM
To: Dora, Sunil Kumar <SunilKumar.Dora(a)windriver.com>
Cc: raj.khem(a)gmail.com <raj.khem(a)gmail.com>
Subject: [Linaro-TCWG-CI] gcc patch #142457: 2 regressions on aarch64
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.
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/142457
| Author: Khem Raj <raj.khem(a)gmail.com>
| Date: Sun Aug 30 22:15:06 2026 +0530
|
| [PATCH v2] Add ssp_nonshared to link commandline for musl targets [PR127138]
|
| musl provides __stack_chk_fail in libc but, unlike glibc, not the
| __stack_chk_fail_local alias that gcc calls in PIC/PIE code on some
| targets (32-bit x86, PowerPC). musl-based distributions ship that
| ... 20 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 2c3724c84c1 Daily bump.
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.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-arm, after:
| commit glibc-2.44.9000-218-g371d58d11bf
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Mon Aug 31 13:09:37 2026 -0300
|
| posix: Add POSIX posix_spawn_file_actions_add{,f}chdir
|
| Use proper symbols instead of alias to the *_np counterpart.
|
| The declarations are also moved from __USE_XOPEN2K24XSI to
| ... 5 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running glibc:elf ...
| FAIL: elf/tst-valgrind-smoke
Used configuration :
*CI config* tcwg_glibc_check master-arm
*configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-2051. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
Details of the regressions above, from the testsuite logs:
| FAIL: elf/tst-valgrind-smoke
| original exit status 1
| /usr/bin/valgrind
| /lib/ld-linux-armhf.so.3
| bin: /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/valgrind-test
| ld.so: /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/glibc-glibc.git~master/elf/ld.so
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=371d58d11bf7aacd4bf4…
Hi,
This test is incorrect.
This is a test configuration issue caused by an inappropriate floating-point tolerance setting.
Updating the test to use the standard FP32 tolerance resolves the failure while preserving the intended validation of single-precision numerical results.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信日時: 2026年9月27日 2:46
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; a.bataev(a)outlook.com <a.bataev(a)outlook.com>
件名: [Linaro-TCWG-CI] llvmorg-24-init-10324-gfa939745e0ac: 1 regression on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after:
| commit llvmorg-24-init-10324-gfa939745e0ac
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Wed Sep 23 14:33:54 2026 -0400
|
| [SLP]Pair small sign-aware reduction groups only if both signs have one
|
| The small-group check of the flattened fsub/fneg fadd reductions
| used whenever any leaf was negated, vectorizing 2-wide parts that
| have no opposite-sign part to combine with via the vector fsub.
| ... 5 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0680 ...
| FAIL: test-suite :: Fujitsu/Fortran/0680/Fujitsu-Fortran-0680_0005.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2284. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/fa939745e0aceb6cd92debec4badd42…
Hi,
These tests are incorrect. Therefore, we will correct the tests.
The investigation concluded that all 13 failures are caused by expected floating-point precision differences introduced by reassociation enabled by commit #222302.
No compiler malfunction was identified. The affected test cases contain overly strict or incorrect tolerance settings and should be updated accordingly.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信日時: 2026年9月14日 1:44
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; tom.eccles(a)arm.com <tom.eccles(a)arm.com>
件名: [Linaro-TCWG-CI] llvmorg-24-init-8067-gf40e465b112a: 13 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-24-init-8067-gf40e465b112a
| Author: Tom Eccles <tom.eccles(a)arm.com>
| Date: Wed Sep 9 17:20:24 2026 +0100
|
| [flang] Ignore subscript conversions when reassociating sums (#222302)
|
| Implicit conversions of INTEGER(4) array indices to SubscriptInteger
| were treated as conversions in the surrounding floating-point sum,
| preventing reassociation of ordinary array-element expressions.
| ... 6 lines of the commit log omitted.
Produces 13 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0340 ...
| FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0099.test
| FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0117.test
| FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0181.test
| FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0185.test
| ... and 15 more
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2276. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/f40e465b112a1a0cc1f6f544b33f356…
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,
On 2026-09-13 01:18, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In glibc_check master-aarch64, after:
> | glibc patch https://patchwork.sourceware.org/patch/143640
> | Author: Aurelien Jarno <aurelien(a)aurel32.net>
> | Date: Sat Sep 12 13:34:20 2026 +0200
> |
> | [PATCH] x86_64/cet: fix tst-shstk-legacy-1{f,g} tests [BZ #31877]
> |
> | The tst-shstk-legacy-1f and tst-shstk-legacy-1g tests depend on the
> | tst-shstk-legacy-mod-1.so module to test that legacy shadow stack code
> | in init_array does not trigger a segfault in tst-shstk-legacy-1f, while
> | ... 6 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | fa91c51bb7 elf: Do not load cache extensions from an old-format ld.so.cache [BZ #34600]
This patch only changes files in sysdeps/x86_64, so I really doubt in
causes issues for the aarch64 build. Could you please retry?
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien(a)aurel32.net http://aurel32.net