Hi,
This test is incorrect.
0196_0003.c contains intentional undefined behavior and should not be used as a runtime correctness test. The observed SIGSEGV is a valid consequence of the program's undefined behavior, and the test should be converted to a compile-only test to avoid environment-dependent failures.
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年10月16日 19:37
宛先: 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>; cullen.rhodes(a)arm.com <cullen.rhodes(a)arm.com>
件名: [Linaro-TCWG-CI] llvmorg-24-init-14147-g4149fd77e859: 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 llvmorg-24-init-14147-g4149fd77e859
| Author: Cullen Rhodes <cullen.rhodes(a)arm.com>
| Date: Wed Oct 14 09:22:35 2026 +0100
|
| [AArch64][GlobalISel] Do not run the Localizer at -O0 (attempt 2) (#231406)
|
| This was disabled earlier this year (#177359) before being shortly reverted due
| to two test failures which have since been fixed. The flaky LLDB issue was
| fixed in #210050 and the libcxxabi test in #230518.
| ... 10 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0196 ...
| FAIL: test-suite :: Fujitsu/C/0196/Fujitsu-C-0196_0003.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="-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-2297. (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/4149fd77e8591b5426bc119a88c194e…
Hi,
This issue occurs in the TSVC tests included in the LLVM test suite, not in the Fujitsu Compiler Test Suite.
Additionally, since we were able to verify that the tests run successfully on our machine environment, we are closing this issue.
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年10月9日 15:13
宛先: 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>
件名: [Linaro-TCWG-CI] llvmorg-24-init-13113-g3f1163972448: 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_vect/main-aarch64-Ofast-sve_vla, after:
| commit llvmorg-24-init-13113-g3f1163972448
| Author: David Sherwood <david.sherwood(a)arm.com>
| Date: Thu Oct 8 14:21:01 2026 +0100
|
| [LV][NFC] Fix "vectorization is possible but not beneficial" message (#228024)
Produces 2 regressions:
|
| regressions.sum:
| Running vectorization:MultiSource/Benchmarks/TSVC ...
| FAIL: s3110
| FAIL: s318
| # "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_SUBDIRS=MultiSource/Benchmarks/TSVC "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2291. (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_vect--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_vect--main-aarch64-Ofast-sve_vla-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_vect--main-aarch64-Ofast-sve_vla-…
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_vect--main-aarch64-Ofast-sve_vla-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_vect--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/3f1163972448320aecc9241e8691333…
That looks unrelated, false alarm?
Thanks,
Sid
On Oct 18, 2026 16:05, 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/146226
| Author: Siddhesh Poyarekar <siddhesh(a)gotplt.org>
| Date: Sat Oct 17 20:45:26 2026 -0400
|
| [PATCH] libssp: Support _FORTIFY_SOURCE=3 [PR109270]
|
| Add __builtin_dynamic_object support into libssp header to
allow usage
| of _FORTIFY_SOURCE=3 with it.
|
| ... 8 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 2d1f1bc18a5 a68: compare types using TYPE_CANONICAL in
a68_low_assignation [PR algol68/127977]
Produces 1 regression:
|
| regressions.sum:
| Running libstdc++:libstdc++-dg/conformance.exp ...
| FAIL: 29_atomics/atomic/wait_notify/127757.cc -std=gnu++20
execution test
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-precom
mit/builds/11142/archive/artifacts/artifacts.precommit/00-sumfiles/
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-precom
mit/builds/11142/archive/artifacts/artifacts.precommit/notify/
The list of [ignored] baseline and flaky failures are in
*
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precom
mit/builds/11142/archive/artifacts/artifacts.precommit/sumfiles/xfai
ls.xfail
Current build :
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precom
mit/builds/11142/archive/artifacts/
Reference build :
http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/
builds/10733/archive/artifacts/
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies
the
master files.
Hello TCWG,
LLVM is preparing to bump the minimum cmake version - https://github.com/llvm/llvm-project/pull/223854 to 3.31.
Please could you update the version in your bot image(s)? On the PR Mehdi is asking about buildkite libcxx, but if you update the cmake version for the buildbot images, it will apply to buildkite and buildbot so you will be ready for when the PR lands.
I don't know if there is any upper limit on the version, but if you're building it from source anyway I'd match 3.31 exactly and save yourself some hassle.
Thanks,
David Spickett.
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.
In the program (Fujitsu/Fortran/0632/Fujitsu-Fortran-0632_0000.test), the execution result differs from the expected result when compiled with -ffast-math.
Investigation showed that the failure is related to the REAL MOD optimization enabled by -ffast-math.
Disabling the REAL MOD optimization with -fno-fast-real-mod avoids the issue:
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月29日 14:39
宛先: 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>; jonathon.gibney(a)hpe.com <jonathon.gibney(a)hpe.com>
件名: [Linaro-TCWG-CI] llvmorg-24-init-10518-g053331c2c9f4: 1 regression 5 fixes 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-10518-g053331c2c9f4
| Author: jon-gibney <jonathon.gibney(a)hpe.com>
| Date: Thu Sep 24 08:43:46 2026 -0500
|
| Revert "[flang] Respect math flags during conversions (#214311)" (#225887)
|
| This reverts commit 688119653fd40fa46244e1c300e728677a4f001a.
|
| This caused a regression in Fujitsu test 0291/0291_0008.f with
| ... 4 lines of the commit log omitted.
Produces 1 regression 5 fixes:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0632 ...
| FAIL: test-suite :: Fujitsu/Fortran/0632/Fujitsu-Fortran-0632_0000.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
|
| fixes.sum:
| Running test-suite:Fujitsu/Fortran/0000 ...
| FAIL: test-suite :: Fujitsu/Fortran/0000/Fujitsu-Fortran-0000_0009.test
| ... and 5 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=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-2285. (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/053331c2c9f47fb0795c19f33c128ab…
On 10/12/26 11:57 AM, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-linux-gnueabihf cross, after:
> | commit gcc-17-4941-g4eda76ca63df
> | Author: Jerry DeLisle<jvdelisle(a)gcc.gnu.org>
> | Date: Wed Sep 30 19:26:47 2026 -0700
> |
> | libgfortran: [PR127684] caf_shmem: SYNC IMAGES hang on terminated image
> |
> | SYNC IMAGES hung when an image of the image set stopped or failed while
> | another image of the set was waiting in the statement.
> |
> | ... 43 lines of the commit log omitted.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running gfortran:gfortran.dg/coarray/caf.exp ...
> | FAIL: gfortran.dg/coarray/sync_images_failed_1.f90 -fcoarray=lib -pthread -O2 -lcaf_shmem -lrt execution test
> | FAIL: gfortran.dg/coarray/sync_images_stopped_2.f90 -fcoarray=lib -pthread -O2 -lcaf_shmem -lrt execution test
> | FAIL: gfortran.dg/coarray/sync_images_stopped_3.f90 -fcoarray=lib -pthread -O2 -lcaf_shmem -lrt execution test
>
> Used configuration :
> *CI config* tcwg_gnu_cross_check_gcc arm-linux-gnueabihf cross
> *configure and test flags:* --target arm-linux-gnueabihf --disable-multilib --with-float=hard --with-fpu=vfpv3-d16 --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
Hi,
Thanks for the report. These are not regressions from the patch: the
three tests are new in it, and on this configuration every coarray test
linked with -lcaf_shmem fails at execution, so each newly added one
shows up in the regression delta.
libcaf_shmem starts the images by fork () + execve (argv[0], ...) of the
test executable. Your harness starts the test through qemu-wrapper.sh,
which passes -L <sysroot> to qemu, but the re-executed images are
dispatched by binfmt_misc (arm-binfmt-P) without the sysroot, cannot
find the dynamic loader and exit with status 255. The gfortran.log
should show "arm-binfmt-P: Could not open '/lib/ld-linux-armhf.so.3'"
followed by "ERROR: Image N failed with signal 0, exitstatus 255" for
all images.
Exporting QEMU_LD_PREFIX=<sysroot> in the test environment (in addition
to -L) should fix all of the caf_shmem execution tests; the environment
is passed on to the images. The same happens on your aarch64 cross
configuration.
Regards,
Jerry
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.
I’ve fixed this issue in https://github.com/llvm/llvm-project/pull/230153
Best,
Gaetan
--
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Date: Wednesday, 7 October 2026 at 18:39
To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: Gaetan Bossu <Gaetan.Bossu(a)arm.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
Subject: [Linaro-TCWG-CI] llvmorg-24-init-11909-ga0cbcd03575c: 68 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-11909-ga0cbcd03575c
| Author: Gaëtan Bossu <gaetan.bossu(a)arm.com>
| Date: Fri Oct 2 11:52:31 2026 +0100
|
| Reland [AArch64][CostModel] Consider some nxv1 operations as legal (#214471) (#228371)
|
| This is allowing some operations on vscale x 1 types, namely:
| - load/store
| - masked load/store
| ... 17 lines of the commit log omitted.
Produces 68 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0096 ...
| NOEXE: test-suite :: Fujitsu/C/0096/Fujitsu-C-0096_0135.test
| Running test-suite:Fujitsu/C/0104 ...
| NOEXE: test-suite :: Fujitsu/C/0104/Fujitsu-C-0104_0006.test
| NOEXE: test-suite :: Fujitsu/C/0104/Fujitsu-C-0104_0007.test
| ... and 68 more
| # "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="-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-2290. (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/a0cbcd03575c21d4c9b3935ea30c4b3…
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.