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…
Hi,
The issue is caused by an overly strict test tolerance rather than an incorrect compiler result.
We will resolve the issue by changing the tolerance value (error = 0.050) to a value equivalent to approximately 5 ULP (e.g., 0.16).
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月7日 4:48
宛先: 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-1585-g3cf44478fcf5: 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-1585-g3cf44478fcf5
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Fri Jul 24 10:04:32 2026 -0400
|
| [ConstantFolding]Fold llvm.powi via square-and-multiply (#210771)
|
| Compute constant-folded powi using APFloat multiplies in the operand's
| own semantics (square-and-multiply), matching the expansion
| ExpandPowI generates in SelectionDAGBuilder, instead of routing
| ... 1 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0104 ...
| FAIL: test-suite :: Fujitsu/Fortran/0104/Fujitsu-Fortran-0104_0086.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-2259. (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/3cf44478fcf54c8996c88c1214d2170…
Hi, I've done my first patch to glibc, I updated some part of
documentation, nothing else. I formated patch from HEAD of master
branch. After I sent patch, I received on mail error:
```
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/139472
| Author: Nesterov Maksim <maxgoonfuture(a)gmail.com>
| Date: Sat Jul 18 17:29:21 2026 +0300
|
| [PATCH 1/1] Add in *info* documentation (Low-Level Terminal
| Interface > Terminal Modes > Control Modes) *CMSPAR* constant
| description; *CMSPAR* allows to use stick parity (mark/space)
| instead of odd/even.
| ... applied on top of baseline commit:
| 6b29e74c73 math: Update tanh from CORE-MATH (revision cf237fa0)
Produces 1 regression 96 fixes:
|
| regressions.sum:
| Running glibc:posix ...
| FAIL: posix/tst-affinity-static
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| ... and 109 more
```
What should I fix?
Hi,
These tests are incorrect.
The optimization introduced by LLVM-2258 converts trigonometric library calls into LLVM intrinsics and combines matching sin()/cos() pairs into sincos(). As a result, generated code for trigonometric operations changes slightly and produces small numerical variations that are still within expected single-precision accuracy.
The failing cases are therefore test-suite issues rather than compiler correctness issues.
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年7月31日 15:05
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: kito.cheng(a)sifive.com <kito.cheng(a)sifive.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-166-g0e877fd1a637: 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_vla, after:
| commit llvmorg-24-init-166-g0e877fd1a637
| Author: Kito Cheng <kito.cheng(a)sifive.com>
| Date: Wed Jul 15 17:20:55 2026 +0800
|
| Reland "[InstCombine] Combine llvm.sin/llvm.cos libcall pairs into llvm.sincos" (#194616)
|
| This reland #184760
|
| Fixed https://lab.llvm.org/buildbot/#/builders/123/builds/39337
| ... 25 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0118 ...
| FAIL: test-suite :: Fujitsu/Fortran/0118/Fujitsu-Fortran-0118_0309.test
| Running test-suite:Fujitsu/Fortran/0631 ...
| FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0072.test
| Running test-suite:Fujitsu/Fortran/0641 ...
| ... 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=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-2258. (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/0e877fd1a637ec2964883d324600211…
Hello Paul,
ci_notify(a)linaro.org writes:
> 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-2855-g75be6085674
> | Author: Paul Thomas <pault(a)gcc.gnu.org>
> | Date: Fri Jul 24 15:05:46 2026 +0100
> |
> | Fortran: Auto deallocate coarrays, allocated in team blocks [PR126205]
> |
> | Gfortran was not compliant with F2018(11.1.5.2), which requires that
> | coarrays that are allocated within a team block are deallocated immediately
> | before END TEAM.
> | ... 40 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running gfortran:gfortran.dg/coarray/caf.exp ...
> | FAIL: gfortran.dg/coarray/team_allocated_coarrays.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
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1986. (Require
> Linaro login) Please let us know if you have a fix.
This is a false positive, please disregard this report.
This CI job cross-compiles the test binaries from x86_64 to aarch64 and
arm and runs it under QEMU, but there's a problem with the
cross-compilation. I checked the native aarch64 and arm jobs and in
those cases all tests in team_allocated_coarrays.f90 pass. Everything is
fine.
Sorry for the noise.
The problem is that the test binary tries to load libraries from the
host path rather than from the CI toolchain's sysroot:
Running on qemu: timeout -k 30s 630s /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/scripts/qemu-wrapper.sh x86_64 aarch64 any /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/aarch64-linux-gnu/libc ./team_allocated_coarrays.exe
spawn [open ...]
aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory
aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory
ERROR: Image 1(pid: 3135800) failed with signal 0, exitstatus 255.
aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory
aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory
aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory
aarch64-binfmt-P:aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directoryCould not open '/lib/ld-linux-aarch64.so.1': No such file or directory
ERROR: Image 2(pid: 3135804) failed with signal 0, exitstatus 255.
ERROR: Image 3(pid: 3135806) failed with signal 0, exitstatus 255.
ERROR: Image 4(pid: 3135808) failed with signal 0, exitstatus 255.
ERROR: Image 5(pid: 3135810) failed with signal 0, exitstatus 255.
ERROR: Image 6(pid: 3135812) failed with signal 0, exitstatus 255.
ERROR: Image 7(pid: 3135814) failed with signal 0, exitstatus 255.
aarch64-binfmt-P: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory
ERROR: Image 8(pid: 3135817) failed with signal 0, exitstatus 255.
FAIL: gfortran.dg/coarray/team_allocated_coarrays.f90 -fcoarray=lib -pthread -O2 -lcaf_shmem -lrt execution test
This happens with several testcases, not only team_allocated_coarrays.f90.
I don't know if it the problem is in the testsuite or in our CI scripts.
--
Thiago
(he/him)