I'd like to apologize for causing these regressions. Below
I've copied out the relevant parts from the logs. To me it
looks like _Xv is a reserved identifier.
I'll prepare a patch to fix the issue.
On 9/9/25 6:54 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-eabi cortex-m3 softfp, after:
> | commit gcc-16-3649-gc440b585ba3
> | Author: Luc Grosheintz <luc.grosheintz(a)gmail.com>
> | Date: Thu Sep 4 14:20:28 2025 +0200
> |
> | libstdc++: Implement constant_wrapper, cw from P2781R9.
> |
> | This is a partial implementation of P2781R9. It adds std::cw and
> | std::constant_wrapper, but doesn't modify __integral_constant_like for
> | span/mdspan.
> | ... 25 lines of the commit log omitted.
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running g++:g++.old-deja/old-deja.exp ...
> | FAIL: g++.old-deja/g++.robertl/eb39.C -std=c++26 (test for excess errors)
Code:
4651: template<_CwFixedValue _Xv, typename>
4652: struct constant_wrapper : _CwOperators
4653: {
Compiler error:
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/type_traits:4651:26:
error: expected '>' before numeric constant
My guess is that _Xv is a reserved name. It's not on the list
of common bad identifiers [1], but it's the only guess I have.
[1]: https://gcc.gnu.org/onlinedocs/libstdc++/manual/source_code_style.html
> | FAIL: g++.old-deja/g++.robertl/eb54.C -std=c++26 (test for excess errors)
Same as above.
> | UNRESOLVED: g++.old-deja/g++.robertl/eb54.C -std=c++26 compilation failed to produce executable
Same as above.
> | FAIL: g++.old-deja/g++.warn/iomanip.C -std=gnu++26 (test for excess errors)
Same as above.
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv7-m -mtune=cortex-m3 -mfloat-abi=softfp -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m3 --with-float=softfp --target_board=-mthumb/-march=armv7-m/-mtune=cortex-m3/-mfloat-abi=softfp/-mfpu=auto qemu_cpu=cortex-m3
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1676. 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://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_…
>
> 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
Thanks for the report. There is also an LLVM issue tracking this. I commented there: https://github.com/llvm/llvm-project/issues/157763#issuecomment-3273773003
The test is violating F2023 C15121 that is not properly enforced by flang semantics but that lowering now relies on.
Although we will likely improve LEN lowering which would have the side effect of working around the segfault in the specific case of 0727_0008, I think we will enforce C15121 in a manner that will reject it.
See The LLVM link for more details and suggestion on how to fix the test.
Jean Perier
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Wednesday, September 10, 2025 6:12 AM
To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com
Cc: maxim.kuvyrkov(a)linaro.org; Jean Perier <jperier(a)nvidia.com>
Subject: [Linaro-TCWG-CI] llvmorg-22-init-6821-ga103b9b207f6: 1 regression on aarch64
[You don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
External email: Use caution opening links or attachments
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-22-init-6821-ga103b9b207f6
| Author: jeanPerier <jperier(a)nvidia.com>
| Date: Mon Sep 8 12:07:37 2025 +0200
|
| [flang][lowering] fix vector subscripts in character elemental procedures (#156661)
|
| Fixes https://github.com/llvm/llvm-project/issues/145151
|
| Character elemental procedures require evaluating the result
| ... 22 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0727 ...
| FAIL: test-suite :: Fujitsu/Fortran/0727/Fujitsu-Fortran-0727_0008.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-2088. 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://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1378…
The full lists of regressions and improvements as well as configure and make commands are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1378…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1378…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1378…
Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1377…
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/a103b9b207f67e0afbaf41647a56a4c…
Hi,
These errors are caused by incorrect test programs. Please ignore the mail. We'll update the tests.
I apologize for the false detection.
> 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-22-init-6056-g89f53af3fffe
> | Author: Yingwei Zheng <dtcxzyw2333(a)gmail.com>
> | Date: Tue Sep 2 21:41:02 2025 +0800
> |
> | [ConstraintElim] Use constraints from bounded memory accesses (#155253)
> |
> | This patch removes bound checks that are dominated by bounded memory
> | accesses. For example, if we have an array `int A[5]` and `A[idx]` is
> | performed successfully, we know that `idx u< 5` after the load.
> | ... 7 lines of the commit log omitted.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/C/0094 ...
> | FAIL: test-suite :: Fujitsu/C/0094/Fujitsu-C-0094_0040.test
> | Running test-suite:Fujitsu/C/0137 ...
> | FAIL: test-suite :: Fujitsu/C/0137/Fujitsu-C-0137_0280.test
> | Running test-suite:Fujitsu/C/0170 ...
> | ... 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-2086. 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://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
>
> 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/89f53af3fffed3e41167fbb7bc10d48…
Hi,
Probably this failure is a false detection caused by the fast-math flag. The test uses NaN and very large values. Appending -fhonor-nans -fhonor-infinities resolves the failure.
Please ignore the mail. We'll update the test.
Sorry for the noise.
> 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-22-init-5791-ga36c13492afa
> | Author: Slava Zakharin <szakharin(a)nvidia.com>
> | Date: Fri Aug 29 13:04:55 2025 -0700
> |
> | [flang] Re-enable setting `noalias` on procedure arguments. (#155949)
> |
> | This is a follow-up on #140803, which was disabled in #142128
> | due to #143219.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0351 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0351/Fujitsu-Fortran-0351_0099.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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -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-2081. 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://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-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/a36c13492afa64f925a9cf6ffe99534…
Hi,
This error is caused by an incorrect test program. Please ignore the mail. We'll update the test.
> 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-22-init-5728-gf19b807a2362
> | Author: Peter Klausler <pklausler(a)nvidia.com>
> | Date: Fri Aug 29 07:49:09 2025 -0700
> |
> | [flang] Extend error checking for implicit interfaces (#155473)
> |
> | When an external procedure is called by means of an implicit interface
> | that turns out to be different in a significant way from the actual
> | interface in its definition elsewhere in the source file, we emit an
> | ... 5 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0178 ...
> | NOEXE: test-suite :: Fujitsu/Fortran/0178/Fujitsu-Fortran-0178_0006.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="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -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-2079. 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://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-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/f19b807a23628776895cfc02f4a2938…
Hi,
This commit is practically a revert commit. This commit should not be harmful. Our team will take a look. Please ignore the mail.
Sorry for the noise.
> 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-22-init-5156-g8849750e9988
> | Author: Nikita Popov <npopov(a)redhat.com>
> | Date: Tue Aug 26 09:14:21 2025 +0200
> |
> | [flang] Disable loop interchange by default (#155279)
> |
> | Disable loop interchange by default, while keeping the ability to
> | explicitly enable using `-floop-interchange`. This matches Clang.
> |
> | ... 1 lines of the commit log omitted.
>
> Produces 1 regression 1 fix:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0631 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0058.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/0347 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0347/Fujitsu-Fortran-0347_0240.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 -treat-scalable-fixed-error-as-warning=false -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 -treat-scalable-fixed-error-as-warning=false -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 -treat-scalable-fixed-error-as-warning=false -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-1756. 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://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…
>
> 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/8849750e998819903dc749411bc9a7c…
Hi,
Probably this failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. We'll update the test.
Sorry for the noise.
> 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-22-init-4761-g6560adb58405
> | Author: Connector Switch <c8ef(a)outlook.com>
> | Date: Fri Aug 22 15:55:46 2025 +0800
> |
> | [flang] optimize atand/atan2d precision (#154544)
> |
> | Part of https://github.com/llvm/llvm-project/issues/150452.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0360 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0360/Fujitsu-Fortran-0360_0271.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 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -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-1752. 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://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
>
> 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/6560adb5840596afbeb3f4574bf6d0c…
On Jun 19, 2025, Alexandre Oliva <oliva(a)adacore.com> wrote:
> Or maybe the requirements for this testcase should be stated as
> arm_arch_v7? I'd have to add arm_arch_v7 to
> check_effective_target_arm_arch_FUNC_ok et al, if there aren't reasons
> why it's not there, but I'd be happy to do that, and use dg-add-options
> instead of an explicit -march=armv7, like pr117675.c, if that would be
> preferred.
It turned out that the regression report I got from linaro was related
https://linaro.atlassian.net/browse/GNU-1599
While testing a configuration with -mfloat-abi=hard, -marmv7 is rejected
because it doesn't have an FPU.
Requiring thumb2 wouldn't have avoided this failure, but requiring armv7
is a proper fix for both problems.
(sorry it me took so long; I'm still busy busy with other
fp2sp-elimination-disabled-during-lra problems affecting arm)
Without stating the architecture version required by the test, test
runs with options that are incompatible with the required
architecture version fail, e.g. -mfloat-abi=hard.
armv7 was not covered by the long list of arm variants in
target-supports.exp, so add it, and use it for the effective target
requirement and for the option.
Tested on arm-eabi, and also on arm-vx7r2 with gcc-14. Ok to install?
for gcc/testsuite/ChangeLog
PR rtl-optimization/120424
* lib/target-supports.exp (arm arches): Add arm_arch_v7.
* g++.target/arm/pr120424.C: Require armv7 support. Use
dg-add-options arm_arch_v7 instead of explicit -march=armv7.
---
gcc/testsuite/g++.target/arm/pr120424.C | 4 +++-
gcc/testsuite/lib/target-supports.exp | 1 +
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/gcc/testsuite/g++.target/arm/pr120424.C b/gcc/testsuite/g++.target/arm/pr120424.C
index 4d0e49013c04a..40295ac80da93 100644
--- a/gcc/testsuite/g++.target/arm/pr120424.C
+++ b/gcc/testsuite/g++.target/arm/pr120424.C
@@ -1,5 +1,7 @@
/* { dg-do compile } */
-/* { dg-options "-march=armv7 -O2 -fstack-clash-protection -fnon-call-exceptions" } */
+/* { dg-require-effective-target arm_arch_v7_ok } */
+/* { dg-options "-O2 -fstack-clash-protection -fnon-call-exceptions" } */
+/* { dg-add-options arm_arch_v7 } */
/* { dg-final { scan-assembler-not {#-8} } } */
/* LRA register elimination gets confused when register spilling
causes arm_frame_pointer_required to switch from false to true, and
diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index dfffe3adfbdd0..858fa1787f19c 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -6073,6 +6073,7 @@ foreach { armfunc armflag armdefs } {
v6z_arm "-march=armv6z+fp -marm" "__ARM_ARCH_6Z__ && !__thumb__"
v6z_thumb "-march=armv6z+fp -mthumb -mfloat-abi=softfp" "__ARM_ARCH_6Z__ && __thumb__"
v6m "-march=armv6-m -mthumb -mfloat-abi=soft" __ARM_ARCH_6M__
+ v7 "-march=armv7" __ARM_ARCH_7__
v7a "-march=armv7-a+fp" __ARM_ARCH_7A__
v7a_arm "-march=armv7-a+fp -marm" "__ARM_ARCH_7A__ && !__thumb__"
v7a_fp_hard "-march=armv7-a+fp -mfpu=auto -mfloat-abi=hard" __ARM_ARCH_7A__
--
Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/
Free Software Activist FSFLA co-founder GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity.
Excluding neuro-others for not behaving ""normal"" is *not* inclusive!