Hi,
These tests are incorrect. Therefore, we will correct the tests.
Details are as follows.
Investigation shows that all failures are caused by assumptions in the test programs rather than compiler defects.
Two independent issues were identified.
Issue 1: Fujitsu-C-0060_0008.test and Fujitsu-C-0076_0009.test
These tests use NaN/Infinity related computations while being compiled with -ffast-math.
The source files explicitly enable:
- -fhonor-nans
but do not enable:
- -fhonor-infinities
As a result, optimizations assuming that infinities are not significant remain legal under -ffast-math.
Fujitsu-C-0060_0008.test generates Inf and -Inf through division by zero and compares them against expected values. The test assumes IEEE infinity semantics are preserved, but the compilation options do not require that behavior.
Fujitsu-C-0076_0009.test exhibits the same problem.
Issue 2: Fujitsu-Fortran-0311_0026.test
This test uses Cray pointers and an allocatable array that shares the same storage.
However, the allocatable arrays participating in the aliasing relationship do not have the TARGET attribute.
Under Flang's documented aliasing rules for Cray pointers, optimizations may assume that Cray-pointer targets do not alias ordinary variables unless the aliased variables are declared with the TARGET attribute.
Consequently, the optimizer may legally treat the two objects as non-aliasing despite referring to the same storage at runtime.
The failure therefore originates from the test program not expressing the required aliasing relationship.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 8 月 29 日 (土曜日) 16:20
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: jfargnoli(a)nvidia.com <jfargnoli(a)nvidia.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-6257-gc47197af5327: 3 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-24-init-6257-gc47197af5327
| Author: Justin Fargnoli <jfargnoli(a)nvidia.com>
| Date: Thu Aug 27 13:03:39 2026 -0700
|
| [LTO] Enable `PrepareForLTO` for loop unrolling in pre-link pipelines (#192155)
|
| Currently, the unroller will not unroll loops with inlineable calls.
| However, calls that may not appear to be inlineable during the pre-link
| phase may become inlineable during the post-link phase. The unroller's
| ... 4 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0060 ...
| FAIL: test-suite :: Fujitsu/C/0060/Fujitsu-C-0060_0008.test
| Running test-suite:Fujitsu/C/0076 ...
| FAIL: test-suite :: Fujitsu/C/0076/Fujitsu-C-0076_0009.test
| Running test-suite:Fujitsu/Fortran/0311 ...
| ... and 1 more
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2268. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/c47197af53270a4795040756c27802f…
Hi,
I believe these may be flaky since I checked with my 4 patches on
cfarm185 machine with following configure command
configure --prefix=/home/avinashd/opt --enable-languages=c,c++ --
target=aarch64-unknown-linux-gnu --disable-multilib --enable-fix-
cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --
disable-bootstrap
on top of the commit
a5da203dd95900ba8bab16432667989f3d018c76 : xtensa: Make use of CONST.S
instruction
On Fri, 2026-08-28 at 22:17 +0000, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es).
> Please find some details below.
>
> In aarch64 native, after:
> | 4 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/142333
> | 25ff335aad8 [PATCH 4/4] rs6000: Add sha3 builtins and
> documentation [RFC02645]
> | f47d33c1b4e [PATCH 3/4] rs6000: Add __dmr2048 type (QDOmode) and
> map it to DMR pair register
> | 1eb45af654c [PATCH 2/4] genmodes: Use wider types for
> mode_unit_size array based on max size
The only change in middle-end that has happened is with this patch
(2/4). And that is to generate the macro MODE_UNIT_SIZE_TYPE instead of
unsigned char. This should not have caused the below mentioned
regressions. All other patches are rs6000 backend related.
Please let me know if these regressions are always reproducible or if I
have tested it incorrectly on the cfarm185 machine. I can have a look
at what is happening.
Thanks,
Avinash Jayakar
> | 63b651a8d8f [PATCH 1/4] rs6000: Add sha2 and shapad builtins
> [RFC02645]
> | ... applied on top of baseline commit:
> | aaa0f6b1e87 match.pd: fold reductions of vector duplicates and
> repeats [PR127039]
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0
> in branch percentages, 0 in condition/decision, 1 in prime-paths, 0
> in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered
> paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-
> linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-
> fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<----------------------
> ----8<--------------------------
>
> The information below contains the details of the failures, and the
> ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure
> and make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
My changes are PowerPC specific, I don't understand how aarch64 failures
are due to my changes.
| FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
| FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
Should I wait for another build? or try to reproduce this issue on cfram
machine (Aarch64) ?
Thanks,
Manjunath S Matti.
On 24/08/26 6:05 pm, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 native, after:
> | gcc patch https://patchwork.sourceware.org/patch/142026
> | Author: Manjunath S Matti <mmatti(a)linux.ibm.com>
> | Date: Sun Aug 23 10:57:59 2026 -0500
> |
> | [PATCH] rs6000: Fix ICE with __int128 vector built-ins and -mno-vsx [PR126512]
> |
> | The changes have been bootstrapped and regression tested on
> | powerpc64le-linux and powerpc64-linux.
> |
> | ... 29 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 1ccae7a1e12 AVR: target/127024 - Fix build warning: skipping two-word instruction
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
No, this isn't plausible. The maintainer_utils changes have no effect at all on the compiler. So there must be some other cause.
R.
On 21/08/2026 15:45, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 native, after:
> | 5 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/141841
> | 237059276db [PATCH v1 5/5] maintainer_utils: more array size verification.
> | 4891de9f00a [PATCH v1 4/5] maintainer_utils: Ensure the list of user data is sorted.
> | f18b6593669 [PATCH v1 3/5] maintainer_utils: Move DCO entries outside of roles.
> | 3126c9b698f [PATCH v1 2/5] maintainer_utils: Fix errors in schema.
> | 9145fb8e995 [PATCH v1 1/5] maintainer_utils.py: Add a store method
> | ... applied on top of baseline commit:
> | de8bbe99481 Add fixme comment to vect_slp_node_weight and containing_loop
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | FAIL: gcc.misc-tests/gcov-39.c gcov: 0 failures in line counts, 0 in branch percentages, 0 in condition/decision, 1 in prime-paths, 0 in return percentages, 0 in intermediate format, 0 failed in filters
> | FAIL: gcc.misc-tests/gcov-39.c line 175: expected 1/8 covered paths, was 1/7
>
> Used configuration :
> *CI config* tcwg_gcc_check aarch64-linux-gnu
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi,
Two independent failures were observed in the test-suite.
Both failures are caused by pre-existing undefined behavior in the test programs:
1. Accessing elements through a std::initializer_list after the lifetime of its backing temporary array has ended.
2. Reading uninitialized automatic variables.
The commit (efd053f) merely exposed these latent issues through improved lifetime-aware optimization.
Therefore, this is the test-suite issue, not a compiler defect.
Please ignore the mail. We will update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信日時: 2026年8月21日 21:40
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: isoard(a)amd.com <isoard(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-4794-gefd053f8ef30: 3 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-24-init-4794-gefd053f8ef30
| Author: Alexandre Isoard <isoard(a)amd.com>
| Date: Tue Aug 18 07:36:19 2026 -0700
|
| [PromoteMemToReg] Insert store undef when removing lifetime markers (#191909)
|
| The `lifetime.start` and `lifetime.end` can help avoid the creation of
| spurious phi-node.
|
| ... 20 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C++/0041 ...
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0335.test
| FAIL: test-suite :: Fujitsu/C++/0041/Fujitsu-C++-0041_0337.test
| Running test-suite:Fujitsu/C/0096 ...
| FAIL: test-suite :: Fujitsu/C/0096/Fujitsu-C-0096_0358.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2266. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/efd053f8ef306e6fa21ab0cd1bd185e…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-arm_eabi, after:
| commit v11.1.0-302-g288d39e26d4
| Author: Richard Henderson <richard.henderson(a)linaro.org>
| Date: Mon Aug 10 09:08:31 2026 -0700
|
| tcg: Simplify bswap/hswap expansion using bitswap
|
| Reviewed-by: Philippe Mathieu-Daudé <philmd(a)oss.qualcomm.com>
| Signed-off-by: Richard Henderson <richard.henderson(a)linaro.org>
Produces 14 regressions:
|
| regressions.sum:
| Running gcc:gcc.target/aarch64/advsimd-intrinsics/advsimd-intrinsics.exp ...
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O0 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O1 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O2 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vrev.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
| ... and 11 more
Used configuration :
*CI config* tcwg_gnu_embed_check_gcc master-arm_eabi
*configure and test flags:* --target arm-eabi
We track this bug report under https://linaro.atlassian.net/browse/GNU-2006. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_eabi-bu…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/…
Full commit : https://gitlab.com/qemu-project/qemu/commit/288d39e26d48ed26e4f786ddb3a25ee…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 cross, after:
| commit binutils-2_41-release-11539-gb04b71c9f4b
| Author: Alan Modra <amodra(a)gmail.com>
| Date: Thu Aug 6 11:17:25 2026 +0930
|
| prepare stub bfd for use as dynobj
|
| There are a few wrinkles to using the stub bfd. Target code that
| assumes the stub bfd sections are all stub sections must be corrected
| to test SEC_LINKER_CREATED. Those without the flag are stub sections,
| ... 34 lines of the commit log omitted.
Produces 5 regressions:
|
| regressions.sum:
| Running g++:g++.dg/asan/asan.exp ...
| FAIL: c-c++-common/asan/pr59063-2.c -O2 execution test
| FAIL: c-c++-common/asan/pr59063-2.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
| FAIL: c-c++-common/asan/pr59063-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
| FAIL: c-c++-common/asan/pr59063-2.c -O3 -g execution test
| ... and 1 more
Used configuration :
*CI config* tcwg_gnu_cross_check_gcc aarch64-linux-gnu cross
*configure and test flags:* --target aarch64-linux-gnu --disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
We track this bug report under https://linaro.atlassian.net/browse/GNU-2004. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=b04b71c9f4bba…
Hi,
Investigation showed that the test programs explicitly specify both always_inline and noinline on the same function.
Since these attributes have contradictory semantics, the new diagnostic correctly reports an error.
Therefore, this is a test-suite issue rather than a compiler bug.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 8 月 17 日 (月曜日) 13:19
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; 76546742+ketjandr(a)users.noreply.github.com <76546742+ketjandr(a)users.noreply.github.com>
件名: [Linaro-TCWG-CI] llvmorg-24-init-4536-g6a2d309c7d20: 2 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O0-debug, after:
| commit llvmorg-24-init-4536-g6a2d309c7d20
| Author: Kenzo Tjandra <76546742+ketjandr(a)users.noreply.github.com>
| Date: Sun Aug 16 12:16:01 2026 -0400
|
| [Clang] Diagnose conflict between always_inline/noinline attributes (#215173)
|
| This PR aims to diagnose `always_inline` and `noinline` conflicts which
| currently could pass silently through `Sema` or cause a crash (with
| assertions enabled). Changes include:
| ... 17 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0077 ...
| NOEXE: test-suite :: Fujitsu/C/0077/Fujitsu-C-0077_0032.test
| NOEXE: test-suite :: Fujitsu/C/0077/Fujitsu-C-0077_0033.test
| # "NOEXE" means : the test program cannot be compiled
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2264. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/6a2d309c7d204730a9a35f3261f8448…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 native, after:
| commit binutils-2_41-release-11540-ge189bfd9b49
| Author: Alan Modra <amodra(a)gmail.com>
| Date: Thu Aug 6 11:17:38 2026 +0930
|
| use linker created stub bfd for dynobj
|
| A linker created bfd is a good choice for somewhere to attach linker
| created dynamic sections. It is always the correct format and doesn't
| have anything other than linker generated info to potentially confuse
| ... 86 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| # FAILED
| # build_abe linux:
| # build_abe glibc:
| # build_abe gdb:
| # First few build errors in logs:
| # 00:16:11 make[3]: *** [../gcc-interface/Makefile:467: common-tools] Error 1
| # 00:16:11 make[2]: *** [Makefile:197: gnattools-native] Error 2
| # 00:16:11 make[1]: *** [Makefile:10774: all-gnattools] Error 2
| # 00:16:11 make: *** [Makefile:1102: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe gcc:
| 2
| # build_abe linux:
| 4
| # build_abe glibc:
| # FAILED
| # build_abe gdb:
Used configuration :
*CI config* tcwg_gnu_native_build aarch64-linux-gnu
*configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
We track this bug report under https://linaro.atlassian.net/browse/GNU-1999. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_build--master-aarch64-build/…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_build--master-aarch64-build/…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_build--master-aarch64-build/…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_build--master-aarch64-build/…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=e189bfd9b492a…
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)
Hi,
The tests are incorrect.
The causes are as follows.
The following test cases started to fail after commit 491f16472b0f08ed72481b671c1470c6de953fa0.
- Fujitsu/Fortran/0391/Fujitsu-Fortran-0391_0047.test
- Fujitsu/Fortran/0588/Fujitsu-Fortran-0588_0052.test
Investigation showed that both failures are caused by invalid test code which references disassociated pointers.
The LLVM change itself is not the root cause. The change only exposed latent problems in the test programs because the result shape of array expressions is now determined differently when one operand has a compile-time known shape.
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月30日 21:43
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: caroline.newcombe(a)hpe.com <caroline.newcombe(a)hpe.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-24-init-1860-g491f16472b0f: 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-1860-g491f16472b0f
| Author: Caroline Newcombe <caroline.newcombe(a)hpe.com>
| Date: Mon Jul 27 10:48:35 2026 -0400
|
| [flang][hlfir] Prefer a constant-shape operand for elemental array results (#209791)
|
| Elemental operands are conformable, so their extents are identical and
| the result shape may be taken from either operand. This patch prefers an
| operand whose shape is a compile-time constant, producing a statically
| ... 2 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0391 ...
| FAIL: test-suite :: Fujitsu/Fortran/0391/Fujitsu-Fortran-0391_0047.test
| Running test-suite:Fujitsu/Fortran/0588 ...
| FAIL: test-suite :: Fujitsu/Fortran/0588/Fujitsu-Fortran-0588_0052.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-2256. (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/491f16472b0f08ed72481b671c1470c…
Hi,
These tests are incorrect.
The failures are caused by test cases that require exact floating-point results for vectorized reductions.
The observed differences are small rounding variations that depend on vector length and execution environment.
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月24日 17:04
宛先: 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>; benjamin.maxwell(a)arm.com <benjamin.maxwell(a)arm.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-22857-g308393ede14c: 4 regressions 1 fix on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-23-init-22857-g308393ede14c
| Author: Benjamin Maxwell <benjamin.maxwell(a)arm.com>
| Date: Mon Jul 13 13:30:37 2026 +0100
|
| [LV] Allow scalable epilogue VFs matching the MainLoop VF (#208686)
|
| This effectively limited scalable epilogue VFs to the MainLoopVF/2, as
| all VFs are powers-of-two. This restriction does not exist for fixed
| vector VFs. This could result in worse VF selections for scalable
| ... 3 lines of the commit log omitted.
Produces 4 regressions 1 fix:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0366 ...
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0002.test
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0007.test
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0011.test
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0098.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/0682 ...
| FAIL: test-suite :: Fujitsu/Fortran/0682/Fujitsu-Fortran-0682_0041.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2254. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/308393ede14cc8533d1be122b5df88b…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In arm-eabi v7-a softfp, after:
| commit v11.1.0-rc0-83-gb693da615a7
| Author: Peter Maydell <peter.maydell(a)linaro.org>
| Date: Mon Jul 20 19:05:30 2026 +0100
|
| Revert "target/arm: Build cpu32-system.o as common object"
|
| In c8bea1276c we moved cpu32.c and built it as a common object. The
| commit message says "cpu32.c only contains CPU types used in 32-bit
| system emulation". However, this is incorrect -- it contains 32-bit
| ... 14 lines of the commit log omitted.
Produces 21 regressions 38360 fixes:
|
| regressions.sum:
| Running g++:g++.dg/vect/vect.exp ...
| FAIL: g++.dg/vect/pr95401.cc -std=c++20 (test for excess errors)
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++20 compilation failed to produce executable
| FAIL: g++.dg/vect/pr95401.cc -std=c++26 (test for excess errors)
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++26 compilation failed to produce executable
| ... and 19 more
|
| fixes.sum:
| Running g++:g++.dg/compat/compat.exp ...
| FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/bitfield2 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/pr83487-1 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/pr83487-2 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| ... and 38392 more
Used configuration :
*CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
*configure and test flags:* --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9
We track this bug report under https://linaro.atlassian.net/browse/GNU-1983. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/…
Full commit : https://gitlab.com/qemu-project/qemu/commit/b693da615a7ab2adae7383fecb87b0e…
Hi, thanks for this notification. It's a bit strange that patch 1/2 [1] failed and patch 2/2 [2] passed.
[1]: https://patchwork.sourceware.org/project/glibc/patch/20260728161215.1512331…
[2]: https://patchwork.sourceware.org/project/glibc/patch/20260728161215.1512331…
Is everything OK with the CI Job?
Thanks,
Yury
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: 29 July 2026 10:55 AM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #140108: 3 regressions 111 fixes on arm
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In glibc_check master-arm, after:
| glibc patch https://patchwork.sourceware.org/patch/140108
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Tue Jul 28 17:12:14 2026 +0100
|
| [PATCH 1/2] malloc: Refactor malloc API into a separate header
|
| This commit moves declarations for various malloc functions from
| the malloc.c file to a separate header that can be used to include
| these declarations in other source files.
| ... 2 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 26f0f2aa7d benchtests: Create objdir in the bench-%.c generation rule
Produces 3 regressions 111 fixes:
|
| regressions.sum:
| Running glibc:posix ...
| FAIL: posix/tst-affinity
| FAIL: posix/tst-affinity-pid
| FAIL: posix/tst-affinity-static
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| Running glibc:dirent ...
| FAIL: dirent/tst-readdir-long
| ... and 123 more
<...>
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,
Fujitsu/Fortran/0303/Fujitsu-Fortran-0303_0076.test fails because the test program violates the Fortran standard by redefining an active DO variable through a Cray pointer alias.
This is a test issue rather than a compiler defect.
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月25日 22:10
宛先: 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>; 47756807+khaki3(a)users.noreply.github.com <47756807+khaki3(a)users.noreply.github.com>
件名: [Linaro-TCWG-CI] llvmorg-24-init-787-gd9fff42ccd58: 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-O0-debug, after:
| commit llvmorg-24-init-787-gd9fff42ccd58
| Author: Matsu <47756807+khaki3(a)users.noreply.github.com>
| Date: Mon Jul 20 04:10:54 2026 -0700
|
| [flang] Lower plain DO loops without a secondary-induction iter_arg (#207816)
|
| Example:
| ```fortran
| do i = lb, ub, step
| ... 13 lines of the commit log omitted.
Produces 3 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0303 ...
| FAIL: test-suite :: Fujitsu/Fortran/0303/Fujitsu-Fortran-0303_0076.test
| Running test-suite:Fujitsu/Fortran/0365 ...
| FAIL: test-suite :: Fujitsu/Fortran/0365/Fujitsu-Fortran-0365_0036.test
| Running test-suite:Fujitsu/Fortran/0372 ...
| ... 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="-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-2255. (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/d9fff42ccd58cb3d95cff60641011d7…
On Sun, Jul 19, 2026 at 07:12:50PM +0000, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 cross, after:
> | commit gcc-17-2353-gee27c516c7b6
> | Author: Dylan Rees <dylan.rees(a)arm.com>
> | Date: Mon Jul 13 09:57:17 2026 +0000
> |
> | aarch64: Improve simd highpart builtin folding
> |
> | The current helper function folding calls to lowpart builtins into
> | highpart builtins calls does not handle cases where we have a 64b
> | wide uniform vector, which can be extended to 128b, used for
> | ... 15 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/simd/simd.exp ...
> | FAIL: gcc.target/aarch64/simd/fold_to_highpart_7.c check-function-bodies foo
>
> Used configuration :
> *CI config* tcwg_gnu_cross_check_gcc aarch64-linux-gnu cross
> *configure and test flags:* --target aarch64-linux-gnu --disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1974. (Require Linaro login) Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-aarch64-bui…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s…
>
> Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git
This should be fixed by: https://gcc.gnu.org/pipermail/gcc-patches/2026-July/725423.html
Issue is with 'ssa_uniform_vector_p' which does not handle vector duplicates where the splat is the RHS of an SSA definition.
Best,
Dylan
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,
The tests are incorrect.
The causes are as follows.
The test programs perform an exact comparison of a single-precision floating-point result.
Because it is compiled with -msve-vector-bits=scalable, the generated code adapts to the SVE vector length of the execution environment. As a result, the composition of partial sums and the order of floating-point additions vary between systems, producing different rounding results.
The tests failed because it did not allow normal floating-point rounding differences caused by vectorized execution and compared the result against specific values using exact equality.
Please ignore the mail. We'll update the tests.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 7 月 14 日 (火曜日) 9:53
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: david.green(a)arm.com <david.green(a)arm.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-20756-gd445267fbb56: 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-Ofast-sve_vla, after:
| commit llvmorg-23-init-20756-gd445267fbb56
| Author: David Green <david.green(a)arm.com>
| Date: Fri Jun 26 15:54:41 2026 +0100
|
| [AArch64] Increase the max interleave factor to 4 for loops with reductions (#205612)
|
| The default max interleave factor is 2. Increasing it to 4 universally
| can spend an amount of codeside on something that does not always
| increase performance (especially if the loop gets over-unrolled). Small
| ... 5 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0366 ...
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0002.test
| FAIL: test-suite :: Fujitsu/Fortran/0366/Fujitsu-Fortran-0366_0098.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-2247. (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/d445267fbb569e67ba9311f8c2bc675…
Hello!
The single regression reported by Linaro TCWG CI on both aarch64 and arm
is XPASS: nptl/tst-create4. This test is
intentionally marked XFAIL in the patch (test-xfail-tst-create4 = yes)
because it verifies the non-interleave property that this
patch deliberately removes: with the patch, constructors of independent
DSOs loaded from different threads can interleave. An
XPASS on some runs is expected flaky behaviour for a test that documents
a removed property; it does not indicate a real regression.
No PASS->FAIL transitions are reported on either architecture. The
97/111 ‘fixes’ are environment-driven (no cgroupv2, no /dev/fuse,
no root in CI container). An x86_64 make check run under identical
conditions on both sides shows 0 patch-attributable transitions.
> A third test, tst-create4/tst-create4mod-a/tst-create4mod-b,
> documents a property that the patch removes: under the pre-BZ-15686
> locking model, dl_load_lock serialised the entire _dl_open across
> threads, so constructors of independent DSOs loaded from different
> threads could not interleave. After the patch, they can. The test
> asserts the OLD non-interleaving behaviour and is therefore marked
> XFAIL via test-xfail-tst-create4 = yes. It is included as a
> diagnostic tool for downstream applications that may have implicitly
> relied on the old total order -- plugin registries whose registration
> order determined behaviour, signal-handler chains installed in
> constructors, global logger/telemetry setup, etc.
Thanks!
17.07.2026 23:53, ci_notify(a)linaro.org:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In glibc_check master-arm, after:
> | glibc patchhttps://patchwork.sourceware.org/patch/139350
> | Author: Artem Proskurnev<temap(a)mail.ru>
> | Date: Thu Jul 16 19:04:01 2026 +0300
> |
> | [PATCH v3] elf: Release dl_load_lock before running dlopen constructors (BZ 15686)
> |
> | This addresses one instance of the long-standing class of deadlocks
> | described in BZ #15686: ELF constructors and destructors invoked by
> | the dynamic loader run with dl_load_lock held, so any code path in
> | ... 232 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | a29c483d3c Add RWF_NOSIGNAL from Linux 6.18 to bits/uio-ext.h
>
> Produces 1 regression 111 fixes:
> |
> | regressions.sum:
> | Running glibc:nptl ...
> | XPASS: nptl/tst-create4
> |
> | fixes.sum:
> | Running glibc:debug ...
> | FAIL: debug/tst-fortify-syslog
> | ... and 125 more
>
> Used configuration :
> *CI config* tcwg_glibc_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> If you have any questions regarding this report, please ask onlinaro-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_glibc_check--master-arm-precommit/builds/10367/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_glibc_check--master-arm-precommit/builds/10367/archive/artifacts/artifacts.precommit/notify/
> The list of [ignored] baseline and flaky failures are in
> *http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10367/archive/artifacts/artifacts.precommit/sumfiles/xfails.xfail
>
> Current build :http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/builds/10367/archive/artifacts/
> Reference build :http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10332/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.
On 7/9/2026 4:56 PM, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | commit gcc-17-2261-g649b2a6d9f9f
> | Author: Jeff Law <jeffrey.law(a)oss.qualcomm.com>
> | Date: Wed Jul 8 12:30:56 2026 -0600
> |
> | [PR rtl-optimization/126136] Fix dest = cond ? x : -1 when STORE_FLAG_VALUE is -1
> |
> | So a while back I added support for selecting x/-1 into the ifcvt.cc by using
> | scc and a couple ALU operations. That code explicitly rejects STORE_FLAG_VALUE
> | if it is not 1 or -1.
> | ... 20 lines of the commit log omitted.
>
> Produces 7 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/torture/dg-torture.exp ...
> | FAIL: gcc.dg/torture/pr126136.c -O0 execution test
> | FAIL: gcc.dg/torture/pr126136.c -O1 execution test
> | FAIL: gcc.dg/torture/pr126136.c -O2 execution test
> | FAIL: gcc.dg/torture/pr126136.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
> | ... and 3 more
>
> Used configuration :
> *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --with-fpu=neon-fp-armv8
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1959. (Require Linaro login) Please let us know if you have a fix.
As others noted, this is a case where the test assumed signed chars.
The patch makes the signedness explicit.
Bootstrapped and regression tested on armv7 and verified the test now
passes on that platform. Pushing to the trunk.
jeff
On Wed, Jul 15, 2026 at 10:10 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 armv8l-unknown-linux-gnueabihf native, after:
> | commit gcc-17-2325-g4302e16581b4
> | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com>
> | Date: Fri Jul 10 16:55:19 2026 -0700
> |
> | vect: Add back testcases for trapping math with comparisons [PR36190]
> |
> | These were originally renamed to no-trapping-math-vect-*.c in r0-87196-g04b03edb56633f
> | but were fixed in r0-107313-gf9613c9a919462 but never added back to the
> | trapping versions.
> | ... 17 lines of the commit log omitted.
>
> Produces 10 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/vect/vect.exp ...
> | FAIL: gcc.dg/vect/vect-111.c (test for excess errors)
> | FAIL: gcc.dg/vect/vect-111.c -flto -ffat-lto-objects (test for excess errors)
> | FAIL: gcc.dg/vect/vect-ifcvt-12.c (test for excess errors)
> | FAIL: gcc.dg/vect/vect-ifcvt-12.c -flto -ffat-lto-objects (test for excess errors)
> | ... and 6 more
FAIL: gcc.dg/vect/vect-111.c (test for excess errors)
Excess errors:
cc1: warning: '-fassociative-math' disabled; other options take precedence
This is caused by an interaction with -ftrapping-math added by the new
testcases and this from check_vect_support_and_set_flags:
```
} elseif [is-effective-target arm_neon_ok] {
eval lappend DEFAULT_VECTCFLAGS [add_options_for_arm_neon ""]
# NEON does not support denormals, so is not used for vectorization by
# default to avoid loss of precision. We must pass -ffast-math to test
# vectorization of float operations.
lappend DEFAULT_VECTCFLAGS "-ffast-math"
if [is-effective-target arm_neon_hw] {
set dg-do-what-default run
} else {
set dg-do-what-default compile
}
```
I am not sure what the best way of solving this. Do we just not test
these testcases on arm neon?
or something else?
>
> Used configuration :
> *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a --with-fpu=neon-fp-armv8
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1969. (Require Linaro login) Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1042…
>
> 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
On Tue, Jul 14, 2026 at 10:36 PM <ci_notify(a)linaro.org> wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In aarch64 native, after:
> | commit gcc-17-2060-gf7cde200320e
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Tue Jun 30 09:46:07 2026 +0200
> |
> | libstdc++: Cascade wall-time saves in lazy expansion seeding
> [PR124853]
> |
> | When _M_get_sys_info seeds a Zone line by looking up the active
> rule
> | just before info.begin, the previous code interpreted each rule in
> | isolation against ri.offset() (the line's standard offset alone),
> | ... 71 lines of the commit log omitted.
>
> Produces 6 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ...
> | FAIL: libstdc++-prettyprinters/debug.cc -flto print redirected
> | FAIL: libstdc++-prettyprinters/debug.cc print redirected
> | FAIL: libstdc++-prettyprinters/simple.cc -flto print redirected
> | FAIL: libstdc++-prettyprinters/simple.cc print redirected
> | ... and 2 more
>
> 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
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1968. (Require Linaro login)
> Please let us know if you have a fix.
>
The attribution does not seem correct, as the above patch modifies tzdb.cc
source file and does not touch the container.
>
> 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-build/builds/…
> 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-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
>
Hello,
would you be so kind to point me to the logs of what was failed? :))
(I was unable to find any meaningful info regarding what is wrong :((
)
BTW maybe it would be better to start discussion at
https://github.com/fujitsu/compiler-test-suite/pull/61 ? :)
On Sat, 11 Jul 2026 at 21:48, <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 tcwg_flang_test/main-aarch64-O0-debug, after:
> | commit 2025-09-21-gb3752b8ab8
> | Author: Maxim Solodovnik <solomax666(a)gmail.com>
> | Date: Thu Jul 9 02:58:11 2026 +0000
> |
> | OpenMP specific tests are excluded if OpenMP is absent (#61)
> |
> | * OpenMP specific tests are excluded if OpenMP is absent
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # build_llvm -- clang;lld;flang;clang-tools-extra openmp :
> | 0
> | # test_llvm:
> | # FAILED
> | # First few build errors in logs:
> |
> | From
> | # reset_artifacts:
> | -10
> | # build_llvm -- clang;lld;flang;clang-tools-extra openmp :
> | 0
> | # test_llvm:
> | 1
>
> Used configuration :
> tcwg_flang_test/main-aarch64-O0-debug
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-2245. (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…
>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build…
>
> Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/fujit…
>
> Full commit : https://github.com/fujitsu/compiler-test-suite/commit/b3752b8ab8bb7b0ec0bd7…
--
Best regards,
Maxim
Hi All,
The changes in this patch are limited to the rs6000 backend and only introduce a new machine mode (`TDOmode`) with corresponding rs6000-specific handling. Since the changes are target-specific, I'm not sure why they would cause a bootstrap failure on the ARM configuration.
Could this be an unrelated or flaky CI failure?
For context, the other CI results for this patch are:
https://patchwork.sourceware.org/project/gcc/patch/993e1e61-3bb4-4d74-b507-…
* `linaro-tcwg-bot/tcwg_simplebootstrap_build--master-arm-bootstrap`: **Failed**
* `linaro-tcwg-bot/tcwg_gcc_build--master-aarch64`: **Passed**
* `linaro-tcwg-bot/tcwg_gcc_build--master-arm`: **Passed**
* `linaro-tcwg-bot/tcwg_simplebootstrap_build--master-aarch64-bootstrap`: **Passed**
Thanks,
Jeevitha
-------- Forwarded Message --------
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-Path: <ci_notify(a)linaro.org>
Received: from ltc-imap-p9a.rchland.ibm.com ([unix socket]) by ltc-imap-p9a.rchland.ibm.com (Cyrus 3.0.7-28.el8_10 Fedora) with LMTPA; Thu, 09 Jul 2026 19:55:24 -0500
X-Cyrus-Session-Id: ltc-imap-p9a.rchland.ibm.com-861175-1783644924-2-1779235549232312115
X-Sieve: CMU Sieve 3.0
Received: from localhost (localhost.localdomain [127.0.0.1]) by ltc-imap-p9a.rchland.ibm.com (Postfix) with ESMTP id E2079818AF44C for <jeevitha(a)imap.linux.ibm.com>; Thu, 9 Jul 2026 19:55:24 -0500 (CDT)
X-Virus-Scanned: amavis at linux.ibm.com
X-Spam-Flag: NO
X-Spam-Score: 0.204
X-Spam-Level:
X-Spam-Status: No, score=0.204 tagged_above=-9999 required=6.2 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NORMAL_HTTP_TO_IP=0.001, NUMERIC_HTTP_ADDR=0.001, SPF_HELO_NONE=0.001, WEIRD_PORT=0.001] autolearn=disabled
Received: from ltc-imap-p9a.rchland.ibm.com ([127.0.0.1]) by localhost (ltc-imap-p9a.rchland.ibm.com [127.0.0.1]) (amavis, port 10024) with LMTP id Ik3PP5N3ZHK9 for <jeevitha(a)imap.linux.ibm.com>; Thu, 9 Jul 2026 19:55:10 -0500 (CDT)
Received: from mx1.linux.ibm.com (ltc-mx1-p9a.rchland.ibm.com [9.5.196.147]) by imap.linux.ibm.com (Postfix) with ESMTPS id 40DB6818AF295 for <jeevitha(a)imap.linux.ibm.com>; Thu, 9 Jul 2026 19:55:10 -0500 (CDT)
Received: from smtprelay02.wdc07v.mail.ibm.com (unknown [9.208.129.120]) by mx1.linux.ibm.com (Postfix) with ESMTPS id EA666205250 for <jeevitha(a)linux.ibm.com>; Thu, 9 Jul 2026 19:55:09 -0500 (CDT)
Received: from smtpav05.wdc07v.mail.ibm.com (smtpav05.wdc07v.mail.ibm.com [10.39.53.232]) by smtprelay02.wdc07v.mail.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 66A0t9pY51249502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:09 GMT
Received: from smtpav05.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1800758059 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:09 +0000 (GMT)
Received: from smtpav05.wdc07v.mail.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F068558061 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:08 +0000 (GMT)
Received: from ppma11.dal12v.mail.ibm.com (unknown [10.241.166.155]) by smtpav05.wdc07v.mail.ibm.com (Postfix) with ESMTPS for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:08 +0000 (GMT)
Received: from pps.filterd (ppma11.dal12v.mail.ibm.com [127.0.0.1]) by ppma11.dal12v.mail.ibm.com (8.18.1.7/8.18.1.7) with ESMTP id 66A0nj9v017242 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:08 GMT
Authentication-Results: dal12v.mail.ibm.com; spf=softfail smtp.mailfrom=ci_notify(a)linaro.org; dkim=pass header.d=linaro.org header.s=google; dmarc=pass header.from=linaro.org
Received: from mx0b-001b2d05.pphosted.com (mx0b-001b2d05.pphosted.com [205.220.172.48]) by ppma11.dal12v.mail.ibm.com (PPS) with ESMTPS id 4f7f6yfc38-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:06 +0000 (GMT)
Received: from pps.filterd (m0373562.ppops.net [127.0.0.1]) by mx0b-001b2d05.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 669M6q3h2930946 for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:05 GMT
Authentication-Results: ppops.net; spf=pass smtp.mailfrom=ci_notify(a)linaro.org; dkim=pass header.s=google header.d=linaro.org
Received: from mail-qk1-f174.google.com (mail-qk1-f174.google.com [209.85.222.174]) by mx0b-001b2d05.pphosted.com (PPS) with ESMTPS id 4fam5eav0e-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for <jeevitha(a)linux.ibm.com>; Fri, 10 Jul 2026 00:55:05 +0000 (GMT)
Received: by mail-qk1-f174.google.com with SMTP id af79cd13be357-92e67555e24so16515985a.3 for <jeevitha(a)linux.ibm.com>; Thu, 09 Jul 2026 17:55:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1783644905; x=1784249705; darn=linux.ibm.com; h=list-id:content-type:mime-version:subject:message-id:to:reply-to :date:from:from:to:cc:subject:date:message-id:reply-to:content-type; bh=4+boJic9Z+2+iemk9uIpfZbFIsdxvdLiBrC89rSo71A=; b=fm0v1+3FPg0HqLoZyB1TBow87sPbwSXVQ+KlYQN1IgLdI8A3reZZFGJ8NStZUNrxxY DikCITundRkgUjfULlIELsIZFNNgUgXn0hhNhyRntODZS1DolV1+hTTWs2Jjz2VRp+hq 1UpvAjsUMeR6d9pJM46bbqwNnv0s4fGyNYeMiIAS3SGNMCWRnnIps5zo26A05vrK7SOv Nd5XU4Py061x62ZuI+LBS3GHRsbWadYghq0VAzS2fGn3w+pRJZDvADqyP8aqOQIfTufN s3fqtFEhQOfnv0RWCk17m8EwhU7VmD1LsvILdGl3eDdDj6cQL6+GthGLDkmz9ISTAa61 TYzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1783644905; x=1784249705; h=list-id:content-type:mime-version:subject:message-id:to:reply-to :date:from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to:content-type; bh=4+boJic9Z+2+iemk9uIpfZbFIsdxvdLiBrC89rSo71A=; b=ZRbhEw1+CFPvTQulfmlpKhaEGrAEwvI1dQm3rVPyA4aaMA5FlfraZDJVVfng/P0CiO Pi/nOhPq1fkmtK+NYmDyeLiG7zkaeLdtjUVEH7OkHh/9gQC9pKnQd8qLgGNOA9Q7EAak vFz14sqPmWpo6hHhRQ2khl8JeCy02Vp0upo5LHED5aQnfh99No7CEvNDf/z/zDTQGtW7 9nNzjH0lVo07rpt3fjTS/9/4/snFBJQPmratje/qTIRMVvM97JXtJlBrgwzXJ6AvgYak kisYU+UguA3FIP4hI1H202uAgW2M8rfZVMkSsjs1porgVZS6YeCMUoeRBTO4Oka4fXme pUew==
X-Gm-Message-State: AOJu0Yxda79eYHKZMmZ6/dc2/B9wN0aGK5g83yeAfE9cafHhnN3eTLPm hp0mF/YHISgXEPLK6J65FU28bShyGb8De6hV3ITGsXrZI0OCJL2zo6scQw03jYvS21HnGzWOi1v 4ohCs
X-Gm-Gg: AfdE7cnGBZ0g2LvpXgPDLAnsYUoDpcn9CqPUjRaAs/AHxBEqE2K1RD3tkJNEKSuanh/ 5TXnZeuA2YI08/ohzv55OyXRB3pzOm1NaQpURn6SV/OjwIH/q0bkurgUabU4S1Yj32WOgXGPYPa ZL6hy8y3TtpWUtoxLTkXgC/hW4oLONKKEChttfHxKvFsRvK5w7UjP5lQUqVmDai17KT8XnKqzzO RGW8PKdJV6v0e2JhVMKwRD8UdXoIoBqqt8fOtI0kB3l+Ry3CsbM4HwiVLvIkbywCf9D3NiKinrz vM5h+XNFSkPy/qNS2pneF+wQNY4w3Hf28euuddjAwhzgyMC9MuLzd5OR14qFodboN5xjHFm9WEr iSJEbKwY35FXwGT7K2U6Jk97Dddje+96KZniG8GRxDkiirCafRDbhcx6536bVPBVJWFtuQUN4QD iJ3tBjSi8sm8Gddv//OEpqHQwcoheWdGuJOsGQTNF8O7XZA7pzHkQndq5yzskUxkLsingO/JAP/ v9WdLo=
X-Received: by 2002:a05:620a:19a0:b0:92e:7068:1de6 with SMTP id af79cd13be357-92ecf68ccf9mr964082685a.56.1783644904639; Thu, 09 Jul 2026 17:55:04 -0700 (PDT)
Received: from 72d3563a6d18 (ec2-54-172-246-49.compute-1.amazonaws.com. [54.172.246.49]) by smtp.gmail.com with ESMTPSA id af79cd13be357-92ee5d36a22sm73492585a.39.2026.07.09.17.55.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Jul 2026 17:55:03 -0700 (PDT)
From: ci_notify(a)linaro.org
X-Google-Original-From: tcwg-validation(a)linaro.org
Date: Fri, 10 Jul 2026 00:55:03 +0000 (UTC)
Reply-To: linaro-toolchain(a)lists.linaro.org
To: jeevitha(a)linux.ibm.com
Message-ID: <1196044404.73385.1783644903827@72d3563a6d18>
Subject: [Linaro-TCWG-CI] gcc patch #138844: Failure on arm
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_Part_73384_1250231304.1783644903313"
X-Jenkins-Job: TCWG Precommit tcwg_simplebootstrap_build/master-arm-bootstrap
X-Jenkins-Result: FAILURE
List-ID:
X-CLX-Shades: MLX
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwNzEwMDAwNSBTYWx0ZWRfX/QbUtdwXAKAB aWo86CEW34/md+P55nH35zFMSa2utkEnxxLt7o+dkvDccyzbsv+kCv+R5Ob/zpzeT3IFG6tTKEX KojMivWE5yZZRKZfnHy6KrVMJq7uxknnjOHmUxaPpoghRzH7iI8mGL7Es3zP2+trgatuPYUHNou Wfr6aTqeRdiwXGOgSqfkfVTeIM3x8X3r/yTaeXdBntLNtfAif1eu7STxhaRQ1aUC+c4ADFdOJk+ Zg15RbXwWCRN1VADNWCBH6pkBvyKctVZCw6KKBe7MxvpoYQBMbM0Yyo+kbMlzlK0NeN/qRg29qJ D79wXolwL7pSMan4PHXLrFTXiCHYRNhnAFcjisYEpsQScaRTsOs6OhmL7bnMxjureLr79IFAxUo zhwawIYeaPpZ93Wv1Wvcd5ji1R9C92ugpf6KeJ4OujFErbyZoUIOtoMOwwAXwUy5Z9tNtKWCwpZ mvvemM4gvmBe34G4ecI2EiYNyUyW3Hp8Odf/VQq0goxgQ+BZPL596CjWOhNAJ
X-Proofpoint-GUID: XA-23DF6gEgcniOZwVkQ-DTZRVYB2VTm
X-CLX-Response: 1TFkXGxwfEQpMehcbEhkRCllEF28FHUcfGHloaWxOEQpYWBdvQW5PH316Z2x 6exEKeE4XaFxna3haWE4ae28RCnhLF29Bbk8ffXpnbHp7EQp5TBdiBVkBf21mbWFfQBEKQ0gXBx kSGhEKQ1kXBxsdGhEKQ0kXGgQaGhoRCllNF2dmchEKWUkXGnEaEBp3BhseH3EYHRAadwYYGgYaE QpZXhdsbHkRCklGF0NIR3UZdUJFWV5PThEKSUcXeE9NEQpDThdyawcYGW5sHE1vTUlEQ2VwXXxB ewdufnB4fHNoGHx+RxEKWFwXHwQaBB4YGgUbGgQbGhoEGxkeBBkeEBseGh8aEQpeWRdCQk9PbxE KTVwXHB4TEQpMWhd4aV1NaxEKRVkXbGtrEQpMXxd6BQUFBQUFBQUFHREKTEYXb2trY2trEQpCTx dlaVBnYUZ9bBsFBREKQ1oXGBoTBBIfBBgYGAQbHR4RCkJeFxsRCkJcFxsRCl5OFxsRCkJLF3pMT V57aEhdaRoFEQpCSRd6TE1ee2hIXWkaBREKQkUXbEVsHmMdTBJCXEIRCkJOF3pMTV57aEhdaRoF EQpCTBdsRWweYx1MEkJcQhEKQmwXbEVsHmMdTBJCXEIRCkJAF2Viex1zH39ubW5FEQpCWBdnS0l aQHlTeE5NfhEKWlgXGREKeUMXY1tkYn1laUlhE2MRCllLFx8THh0RClpLFx8THh0RCnBnF29CG3 kebn5JQhlCEBkaEQpwaBdrR1lZaFgBG3B7UxAZGhEKcGgXa1tOa0VnXVNoSXoQGRoRCnBoF2sbR HJbT3JAW2hoEBkaEQpwaBdtHUJJGV5JXm96SxAZGhEKcGgXYVxiGnJAbUxGa1gQGRoRCnBoF2Uc bHBHHm56a0NeEBkaEQpwaBdnY1pEUmJLX1p/YhAZGhEKcGgXaUQdQ1tle2BZfUIQGRoRCnB9F2Q SaEBOR2wbRFBiEBkaEQpwZxdgfmBEQF1iXX1eeBAeEhEKcGcXZm5GZnphXEVJQEsQGRoRCnB9F2 5kXGBiQH5aHEAbEBkaEQpwfRdlR21kSWxsGW9DGhAZGhEKcH0XbVlzbEFwfH0SGgEQGRoRCnB9F 3pcGkBQTRpGaWdNEBkaEQpwfxdpfWkfT2QTGEBobhAbHhsRCnBfF21tQXxSQWFNWE0ZEBkaEQpw fxdgY15iYX9iUkRmQxAZGhEKcF8XZXIcHH5/WU9rQR0QGRoRCnBDF25iGFhuc2trWUtPEBkaEQp tfhcaEQpYTRdLESA=
X-Authority-Analysis: v=2.4 cv=A6Rc+aWG c=1 sm=1 tr=0 ts=6a5042e9 cx=c_pps a=UZBReMFAb/XnTJ6n9KjCdA==:117 a=4i7SwhsebvtlREVtV86eDg==:17 a=RAioF0-LDSMA:10 a=y97k-4bRjHMA:10 a=Kan8h273Bse8B8Jy5C1n:22 a=Tf50yhtgai_kYZK-W9C0:22 a=h-DKXlNGRfCIpgHfyL0k:22 a=CCpqsmhAAAAA:8 a=F3QvygtyAAAA:8 a=VnNF1IyMAAAA:8 a=KKAkSRfTAAAA:8 a=VCkTNp8_fUlclFnFz1EA:9 a=lqcHg5cX4UMA:10 a=QEXdDO2ut3YA:10 a=cT35ftHboTvi5MAKYRRR:22 a=ul9cdbp4aOFLsgKbc677:22 a=Zmt_HxeAg-O1BNttnniw:22 a=cvBusfyB2V15izCimMoJ:22
X-Proofpoint-Spam-Info: AW1haW4tMjYwNzEwMDAwNSBTYWx0ZWRfX7QmG5Onrzk8Q 33gso025apajvQ721u6LbWkssi7jJCuoq+Pv2gu1BajkqrfRl6RkIE7VScbICpQS4CkZmxeq7+o L84NC/U0AJTw57i3sg16bzAvuZf5yCs=
X-Proofpoint-ORIG-GUID: XA-23DF6gEgcniOZwVkQ-DTZRVYB2VTm
X-Proofpoint-Banner-Trigger: inbound
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1143,Hydra:6.1.134,FMLib:17.12.100.49 definitions=2026-07-09_04,2026-07-09_04,2025-10-01_01
X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=1 impostorscore=0 lowpriorityscore=0 suspectscore=0 clxscore=165 adultscore=0 malwarescore=0 spamscore=0 phishscore=0 priorityscore=183 bulkscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=inbound adjust=1 reason=mlx scancount=1 engine=8.22.0-2606150000 definitions=main-2607100005 domainage_hfrom=5947 domainage_replyto=5947
X-TM-AS-GCONF: 00
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In simplebootstrap_build master-arm-bootstrap, after:
| gcc patch https://patchwork.sourceware.org/patch/138844
| Author: jeevitha <jeevitha(a)linux.ibm.com>
| Date: Fri Jul 10 00:08:25 2026 +0530
|
| [PATCH] rs6000: Add TDOmode support
|
| Hi All,
|
| The following patch has been bootstrapped and regtested on powerpc64le-linux.
| ... 15 lines of the commit log omitted.
| ... applied on top of baseline commit:
| d06b04d90ca Remove uses of `CONSTEXPR` macro
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe bootstrap:
| # FAILED
| # First few build errors in logs:
| # 01:33:42 make[2]: *** [Makefile:26651: compare] Error 1
| # 01:33:42 make[1]: *** [Makefile:26631: stage3-bubble] Error 2
| # 01:33:42 make: *** [Makefile:1140: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe bootstrap:
| 1
Used configuration :
*CI config* tcwg_simplebootstrap_build master-arm-bootstrap
*configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
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_simplebootstrap_build--master-arm-boots…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots…
Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots…
Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
Hi,
I work on lldb on Windows at Apple.
We have done some work recently to bring lldb-server.exe up to par with the current lldb implementation on Windows, which uses an in-process debugger. This new implementation matches other platforms like macOS and Linux which also use a debug server.
We have full test parity (all the tests that work with the in process debugger also work with lldb-server.exe). We are actively testing both configs in CI: https://ci-external.swift.org/job/lldb-windows/job/main/
We are ready to make the change to make lldb-server.exe the default implementation on Windows. In the codebase, this means switching the flag here: https://github.com/llvm/llvm-project/blob/d981ae2be3be6fd65ad66e763fcc20b3a….
However, building lldb-server.exe requires libxml2, which the buildbot https://lab.llvm.org/buildbot/#/builders/141 does not have.
I’m reaching out to you to ask if it’s please possible to install libxml2 on the bot?
The easiest way to do that would be to run “vcpkg install libxml2” on the bot. Vcpkg is already in the PATH, so CMake should pick up the libxml2 includes automatically once it’s installed.
I am happy to validate the build once the installation is complete and will address any issues that may arise.
Best regards,
Charles Zablit
On Thu, Jul 9, 2026 at 11:59 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 simplebootstrap_build master-arm-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/138785
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Wed May 13 08:27:50 2026 +0800
> |
> | [PATCH v2] x86: Honor preserve_none ABI for x86-64 MS calls
> |
> | In 64-bit mode, preserve_none attribute uses a different calling
> | convention. Ignore MS ABI with preserve_none attribute to always
> | use the preserve_none calling convention with preserve_none
> | ... 45 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | e5af677005c Daily bump.
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 00:07:41 make[3]: [Makefile:1882: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored)
> | # 00:58:25 make[3]: [Makefile:1882: armv8l-unknown-linux-gnueabihf/bits/largefile-config.h] Error 1 (ignored)
> | # 01:14:22 collect2: error: ld returned 1 exit status
> | # 01:14:22 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/lto/Make-lang.in:93: lto1] Error 1
> | # 01:14:22 collect2: error: ld returned 1 exit status
> | # 01:14:22 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/cp/Make-lang.in:147: cc1plus] Error 1
> | # 01:14:23 collect2: error: ld returned 1 exit status
> | # 01:14:23 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/c/Make-lang.in:88: cc1] Error 1
> | # 01:14:23 collect2: error: ld returned 1 exit status
> | # 01:14:23 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/objc/Make-lang.in:78: cc1obj] Error 1
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
The only file which my patch changes is gcc/config/i386/i386.cc.
How can it impact arm?
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-arm-bootstrap
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> 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_simplebootstrap_build--master-arm-boots…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-arm-boots…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
--
H.J.
Hi,
These tests are incorrect. Therefore, we will correct them.
The lastprivate variables pa/pb did not meet OpenMP's requirements because they were treated as private instead of the required shared variable type.
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月7日 21:06
宛先: 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>; safonsof(a)amd.com <safonsof(a)amd.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-21388-g154834916515: 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-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-23-init-21388-g154834916515
| Author: Sergio Afonso <safonsof(a)amd.com>
| Date: Wed Jul 1 16:54:06 2026 +0100
|
| [Flang][OpenMP][MLIR] Improve SPMD-No-Loop handling (#206953)
|
| This patch modifies the handling of the
| `-fopenmp-assume-teams-oversubscription` and
| `-fopenmp-assume-threads-oversubscription` compiler options in Flang and
| ... 13 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0688 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0688/Fujitsu-Fortran-0688_0014.test
| NOEXE: test-suite :: Fujitsu/Fortran/0688/Fujitsu-Fortran-0688_0016.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 -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-2242. (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/154834916515ad8f9286a759a4f629f…
Hi,
These tests are incorrect. Therefore, we will correct them.
The test incorrectly uses statement function dummy argument names (e.g., a, b) that conflict with already declared array variables in the same scope.
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 月 9 日 (木曜日) 5:14
宛先: 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>; kwyatt.external(a)hpe.com <kwyatt.external(a)hpe.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-21399-gb1b919870974: 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-23-init-21399-gb1b919870974
| Author: kwyatt-ext <kwyatt.external(a)hpe.com>
| Date: Wed Jul 1 11:35:28 2026 -0500
|
| [flang] Implement check for statement function dummy argument names (#204417)
|
| Implement F2023 19.4.2 conformance check for statement function dummy
| argument names
|
| ... 16 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0289 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0289/Fujitsu-Fortran-0289_0025.test
| Running test-suite:Fujitsu/Fortran/0572 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0572/Fujitsu-Fortran-0572_0463.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-2243. (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/b1b9198709749eb612bfce7cfb6a3ab…
Hi,
These tests are incorrect. Therefore, we will correct them.
The tests fail after a change in Flang runtime allocation behavior from malloc to 64-byte aligned aligned_alloc.
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 月 4 日 (土曜日) 14:21
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
Cc: jason.van-beusekom(a)hpe.com <jason.van-beusekom(a)hpe.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-21381-ga675a661b86f: 9 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-23-init-21381-ga675a661b86f
| Author: Jason Van Beusekom <jason.van-beusekom(a)hpe.com>
| Date: Wed Jul 1 10:36:38 2026 -0500
|
| [Flang-RT] Change alignment for allocatable and pointer arrays to 64 … (#206525)
|
| …bytes
|
| in https://github.com/llvm/llvm-project/pull/194969 the default array
| ... 9 lines of the commit log omitted.
Produces 9 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0449 ...
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0005.test
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0006.test
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0009.test
| FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0082.test
| ... and 6 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-2240. (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/a675a661b86f54d45e90778362a97c1…
Hi,
The test violates Fortran dummy argument aliasing rules.
Overlapping elements (xx(6) and yy(1)) reference the same memory (x(6)), and the code performs both read and write through different dummy arguments, resulting in undefined behavior.
Please ignore the mail. We'll update the test.
We apologize for the false detection.
Best regards,
Yasuyuki Ohno
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
________________________________
差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
送信: 2026 年 7 月 5 日 (日曜日) 21:01
宛先: 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>; kunalspathak.github(a)gmail.com <kunalspathak.github(a)gmail.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-20398-g2668971e1421: 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-23-init-20398-g2668971e1421
| Author: Kunal Pathak <kunalspathak.github(a)gmail.com>
| Date: Wed Jun 24 08:22:51 2026 -0700
|
| [AArch64][ISel] Enable profile-aware branch condition merging (#201486)
|
| AArch64 previously inherited the default {-1, -1, -1} for
| `getJumpConditionMergingParams`, causing
| `shouldKeepJumpConditionsTogether` in SelectionDAGBuilder to always
| ... 28 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0328 ...
| FAIL: test-suite :: Fujitsu/Fortran/0328/Fujitsu-Fortran-0328_0022.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-2241. (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/2668971e14219205ddf6b1f753cf83f…
On 7/4/26 18:40, ci_notify(a)linaro.org wrote:
> /usr/bin/ld: error: libcommon.a: file too short
I don't understand this. How can any patch to the Fortran front end
(much less a completely trivial one) affect libcommon.a? If that file
was truncated maybe it was a transient disk-full or file system error?
-Sandra
On 05/07/2026 02: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 simplebootstrap_build master-aarch64-bootstrap, after:
> | 7 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/138418
> | 9535bc30d4a [PATCH v3 7/8] MAINTAINERS: generate from MAINTAINERS.yml
> | 4a13feeed49 [PATCH v3 6/8] MAINTAINERS.yml: Add libcpp to all C and C++ maintainer's roles
> | 246b6c1ec06 [PATCH v3 5/8] MAINTAINERS.yml: Handle libgrust explicitly
> | 024b571b710 [PATCH v3 4/8] MAINTAINERS.yml: Restore James Norris' email address
> | f13d5705819 [PATCH v3 3/8] MAINTAINERS.yml: Correct Martin Liška's name
> | ... and 2 more patches in gcc
> | ... applied on top of baseline commit:
> | e365e5473a8 libgcc, Darwin: Fix missing prerequisite [PR123976].
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 01:34:20 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:34:20 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:42:17 make[8]: [Makefile:868: stamp-modules-bits] Error 1 (ignored)
> | # 02:02:57 make[3]: *** [Makefile:4629: io/intrinsics.lo] Error 1
> | # 02:02:57 make[2]: *** [Makefile:1882: all] Error 2
> | # 02:02:57 make[1]: *** [Makefile:21363: all-target-libgfortran] Error 2
> | # 02:02:57 make: *** [Makefile:1142: all] Error 2
> |
This report is also bogus. The patch doesn't go anywhere near the main compiler or library sources.
R.
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> 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_simplebootstrap_build--master-aarch64-b…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 04/07/2026 04:12, 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 simplebootstrap_build master-aarch64-bootstrap, after:
> | 8 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/138422
> | 16c863d8c02 [PATCH v3 8/8] MAINTAINERS: Add a script to create a new entry in the mainainers data
> | ff60e686f8f [PATCH v3 7/8] MAINTAINERS: generate from MAINTAINERS.yml
> | d3f4eba32fd [PATCH v3 6/8] MAINTAINERS.yml: Add libcpp to all C and C++ maintainer's roles
> | 403583056ec [PATCH v3 5/8] MAINTAINERS.yml: Handle libgrust explicitly
> | 3389564de59 [PATCH v3 4/8] MAINTAINERS.yml: Restore James Norris' email address
> | ... and 3 more patches in gcc
> | ... applied on top of baseline commit:
> | a20f4528f3a tree-optimization/122569 - recognize CLZ via isolated MSB DeBruijn lookup
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 00:09:12 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:09:12 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:59:19 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 00:59:19 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:16:13 make[3]: [Makefile:1881: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:16:13 make[3]: [Makefile:1882: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored)
> | # 01:17:22 make[6]: *** [Makefile:631: libstdc++fsconvenience.la] Error 1
> | # 01:17:22 make[6]: *** [Makefile:628: libstdc++fs.la] Error 1
> | # 01:17:22 make[5]: *** [Makefile:802: all-recursive] Error 1
> | # 01:17:22 make[4]: *** [Makefile:580: all-recursive] Error 1
> |
Nothing in this patch could possibly produce the above error, so it must be due to the baseline commit being broken, or some other problem with the CI bot.
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> 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_simplebootstrap_build--master-aarch64-b…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_simplebootstrap_build--master-aarch64-b…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
This doesn't seem right given the patch. All tests passed when I tested it locally on aarch64 using two different toolchains.
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: 05 July 2026 12:02 PM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #138079: 2 regressions 97 fixes on aarch64
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/138079
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Mon Jun 29 17:37:22 2026 +0100
|
| [PATCH 1/1] aarch64: compile malloc ifuncs conditionally
|
| On AArch64, ifuncs are used for malloc functions by default.
|
| The code for resolvers in sysdeps/aarch64/multiarch/malloc-ifuncs.c
| ... 5 lines of the commit log omitted.
| ... applied on top of baseline commit:
| d109f366ce build-many-glibcs.py: Update Linux kernel version to 7.1
Produces 2 regressions 97 fixes:
|
| regressions.sum:
| Running glibc:nptl ...
| FAIL: nptl/tst-fopen-threaded
| Running glibc:posix ...
| FAIL: posix/tst-affinity-static
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| Running glibc:dirent ...
| FAIL: dirent/tst-readdir-long
| ... and 108 more
Used configuration :
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
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_glibc_check--master-aarch64-precommit/b…
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-aarch64-precommit/b…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Thanks for reporting this.
This is expected regression due to possible bug in Valgrind. For details, see:
https://bugs.kde.org/show_bug.cgi?id=522497https://inbox.sourceware.org/libc-alpha/cover.1782766548.git.fweimer@redhat…
Thanks,
Yury
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: 05 July 2026 10:50 AM
To: Yury Khrustalev
Cc: Yury Khrustalev
Subject: [Linaro-TCWG-CI] glibc patch #138207: 1 regression 97 fixes on aarch64
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/138207
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Wed Jul 1 14:16:17 2026 +0100
|
| [PATCH] aarch64: Fail early if malloc ifunc resolver is called incorrectly
|
| This patch adds simple check that validates the call to ifunc resolver
| for the malloc function. If resolver is called correctly, it must
| receive at least 1 argument that is equal to the value of AT_HWCAP
| ... 6 lines of the commit log omitted.
| ... applied on top of baseline commit:
| d109f366ce build-many-glibcs.py: Update Linux kernel version to 7.1
Produces 1 regression 97 fixes:
|
| regressions.sum:
| Running glibc:elf ...
| FAIL: elf/tst-valgrind-smoke
|
| fixes.sum:
| Running glibc:debug ...
| FAIL: debug/tst-fortify-syslog
| ... and 110 more
Used configuration :
*CI config* tcwg_glibc_check master-aarch64
*configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
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_glibc_check--master-aarch64-precommit/b…
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-aarch64-precommit/b…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-precommit/b…
Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On Thu, 2 Jul 2026 at 23:45, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi cortex-m33 hard, after:
> | commit gcc-17-1905-g70e630b6d29b
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Jun 25 12:59:04 2026 +0100
> |
> | libstdc++: Update feature test macros and tests for C++29
> |
> | With r17-1595-g0c5c6249a2e9a7 G++ supports -std=c++29 so update our
> | feature test macro generation and testsuite to know about it.
> |
> | ... 19 lines of the commit log omitted.
>
> Produces 5 regressions 5 fixes:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++29 execution test
> | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++29 execution test
> | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++29 execution test
> | FAIL: 27_io/print/2.cc -std=gnu++29 (test for excess errors)
> | ... and 1 more
> |
> | fixes.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 execution test
> | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++26 execution test
> | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++26 execution test
> | FAIL: 27_io/print/2.cc -std=gnu++26 (test for excess errors)
> | ... and 1 more
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m33 --with-float=hard --target_board=-mthumb/-march=armv8-m.main+dsp+fp/-mtune=cortex-m33/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m33
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1942. (Require Linaro login) Please let us know if you have a fix.
This isn't really a regression, it's because the tests switched from
being run with -std=gnu++26 to -std=gnu++29, but they still FAIL the
same way.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h…
>
> 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
I think this is a misattribution of the failure. #203481 is a change
of the CMake build system, it does not change anything functional in
the flang compiler. #203481 had a build problem which was fixed in
#204438. But since Flang built successfully, it cannot be the problem
of that CI problem.
Michael
Am Fr., 19. Juni 2026 um 13:56 Uhr schrieb <ci_notify(a)linaro.org>:
>
> 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-23-init-19659-g3fee6e5ab45d
> | Author: Michael Kruse <llvm-project(a)meinersbur.de>
> | Date: Wed Jun 17 16:13:40 2026 +0200
> |
> | [Flang] Add mock flang driver (#203481)
> |
> | Add a mock driver to pass CMake's compiler introspection for
> | CMake_Fortran_COMPILER. It's purpose is to not having to build the full
> | flang compiler for the runtimes-configure phase in
> | ... 59 lines of the commit log omitted.
>
> Produces 18533 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0004 ...
> | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0001.test
> | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0002.test
> | Running test-suite:Fujitsu/Fortran/0005 ...
> | NOEXE: test-suite :: Fujitsu/Fortran/0005/Fujitsu-Fortran-0005_0001.test
> | ... and 19173 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-2235. (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/3fee6e5ab45d1d352f995ae4eafa510…
--
Tardyzentrismus verboten!
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 native, after:
| commit glibc-2.43.9000-403-g9ed3576e61f
| Author: Yury Khrustalev <yury.khrustalev(a)arm.com>
| Date: Tue May 26 11:19:53 2026 +0100
|
| malloc: aarch64: Add ifuncs for malloc functions
|
| Introduce ifuncs and resolvers for functions pertinent to the
| malloc interface on the AArch64 target: malloc, calloc, free,
| realloc, memalign, valloc, pvalloc, posix_memalign, aligned_alloc,
| ... 13 lines of the commit log omitted.
Produces 118 regressions:
|
| regressions.sum:
| Running gdb:gdb.base/call-strs.exp ...
| FAIL: gdb.base/call-strs.exp: call str_func("a","b","c","d","e","f","g")
| FAIL: gdb.base/call-strs.exp: print str_func("a","b","c","d","e","f","g")
| Running gdb:gdb.base/callfuncs.exp ...
| FAIL: gdb.base/callfuncs.exp: noproto: p t_char_array_values("carray 1","carray 2")
| ... and 125 more
Used configuration :
*CI config* tcwg_gnu_native_check_gdb 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-1934. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu…
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=9ed3576e61f7a87eb83d…
Hi,
This test is incorrect.
I apologize for the false detection.
This issue involves the emergence of precision errors due to a change in the evaluation path for complex number division. Therefore, we will correct the tests.
It may take some time due to our internal release process, sorry.
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年6月15日 14:56
宛先: 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>; carlo.bertolli(a)amd.com <carlo.bertolli(a)amd.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-18988-g9ce63d09cff0: 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-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-23-init-18988-g9ce63d09cff0
| Author: carlobertolli <carlo.bertolli(a)amd.com>
| Date: Thu Jun 11 14:19:36 2026 -0500
|
| [AMDGPU][SCEV] Tighten max backedge-taken count for shift recurrence loops. (#197292)
|
| Application code on AMDGPUs often uses the following pattern:
|
| for (int i = blockDim.x / 2; i >= 1; i >>= 1)
| ... 19 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0640 ...
| FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0306.test
| Running test-suite:Fujitsu/Fortran/0641 ...
| FAIL: test-suite :: Fujitsu/Fortran/0641/Fujitsu-Fortran-0641_0279.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2234. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/9ce63d09cff0bf07da9623b75301011…
This seem like a testplatform issue, as this test (and many others) fails
with:
qemu-arm: unable to find CPU model 'cortex-a9'
On Mon, Jun 22, 2026 at 11:10 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 v7-a softfp, after:
> | commit gcc-17-1246-g341ad729c2c
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Thu May 28 08:37:33 2026 +0200
> |
> | libstdc++: Add (generic_)display_string and
> (generic_)native_encoded_string to filesystem::path
> |
> | Furthermore string and generic_string method as marked as
> deprecated
> | in C++26 mode.
> |
> | ... 54 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 27_io/filesystem/path/generic/display_native_string.cc
> -std=gnu++26 execution test
> | FAIL: 27_io/filesystem/path/native/display_native_string.cc
> -std=gnu++26 execution test
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a
> -mfpu=vfpv3-d16 -mfloat-abi=softfp
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16
> --with-float=softfp
> --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp
> qemu_cpu=cortex-a9
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1938. (Require Linaro login)
> Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
>
> 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
>
Hi,
I am reaching out regarding regression emails I received from your CI about the patch series I submitted recently.
V1 (submitted on 18.05.2026): https://patchwork.sourceware.org/project/gdb/cover/20260518183316.127043-1-…
V2 (submitted on 11.06.2026): https://patchwork.sourceware.org/project/gdb/cover/20260611153232.3011-1-mo…
The regressions were reported for the V2 series, in which no functional changes were introduced (only commit message updates). I am wondering if your CI has been passing for V1 or was not triggered?
I would appreciate your help in determining whether the reported regressions are legitimate or false positives. If they are indeed regressions introduced by my changes, I would greatly appreciate guidance on the reproduction steps.
Thanks,
--Mohamed
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
On Tue, Jun 16, 2026 at 3:30 PM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 native, after:
> | commit gcc-17-1571-ga05a055bb2fb
> | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com>
> | Date: Fri Jun 12 11:40:35 2026 -0700
> |
> | phiopt: reorganize factoring/cselim-limited for phiopt
> |
> | This is in preparation for adding factoring out loads
> | for phiopt were we want to loop over all 3 factoring
> | cases if one of them made a change so that a load elimination
> | ... 15 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/aarch64.exp ...
> | FAIL: gcc.target/aarch64/fuse_cmp_csel-1.c check-function-bodies f1
> | FAIL: gcc.target/aarch64/fuse_cmp_csel-1.c check-function-bodies f2
The check here is too restrictive.
It is checking for gt but we now produce le. Both are valid.
cmp w0, w1
csel w3, w4, w3, le
add w0, w2, w3
I will make both fuse_cmp_csel.c and fuse_cmp_csel-1.c less restive
when it comes to the le/gt issue.
Thanks,
Andrea
>
> 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
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1928. (Require Linaro login) Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> 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-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
Hi,
There are two issues with this issue.
Regarding the first one, the testset was crashing during compilation, but the commit (ef4fb183a8d5c0d1910f7b5b6776ba669d6795ef) resolved the crash during compilation.
Regarding the second issue, the testset (0737_0019.f90) is incorrect.
It passes a function that returns a pointer array to an argument expecting a function that returns an allocatable array, and passes a function that returns an allocatable array to an argument expecting a function that returns a pointer array.
Since this is an incorrect testset, we'll correct it.
I 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 年 6 月 4 日 (木曜日) 6:25
宛先: 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>; 47756807+khaki3(a)users.noreply.github.com <47756807+khaki3(a)users.noreply.github.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-17574-g1872f06d60f3: 18 regressions on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-23-init-17574-g1872f06d60f3
| Author: khaki3 <47756807+khaki3(a)users.noreply.github.com>
| Date: Tue Jun 2 04:55:05 2026 -0700
|
| [flang][HLFIR] Add SeparateAllocatableAssign pass (#197814)
|
| Example:
| ```fortran
| !$\acc kernels
| ... 17 lines of the commit log omitted.
Produces 18 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0134 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0134/Fujitsu-Fortran-0134_0211.test
| Running test-suite:Fujitsu/Fortran/0299 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0299/Fujitsu-Fortran-0299_0038.test
| Running test-suite:Fujitsu/Fortran/0390 ...
| ... and 21 more
| # "NOEXE" means : the test program cannot be compiled
| # "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-2230. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/1872f06d60f35133bbc06e047c763b4…
Hi,
This test is incorrect. There is an error in how the volatile attribute of the variable k is handled when using setjmp and longjmp.
Therefore, we'll correct testset.
I 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年6月6日 14:23
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: npopov(a)redhat.com <npopov(a)redhat.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-17879-gf02dd4afbac1: 1 regression on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-23-init-17879-gf02dd4afbac1
| Author: Nikita Popov <npopov(a)redhat.com>
| Date: Thu Jun 4 09:26:12 2026 +0200
|
| [CaptureTracking] Volatile operations only capture address (#201316)
|
| The fact that a volatile access was performed on a certain address is an
| observable effect in the abstract machine, so volatile operations
| capture the address of the accessed pointer. However, they do not
| ... 6 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0094 ...
| FAIL: test-suite :: Fujitsu/C/0094/Fujitsu-C-0094_0065.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2232. (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/f02dd4afbac15705016a9a7962d8716…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In arm-eabi v7-a softfp, after:
| commit v11.0.0-1483-gc8bea1276c8
| Author: Philippe Mathieu-Daudé <philmd(a)linaro.org>
| Date: Fri May 15 12:40:14 2026 +0200
|
| target/arm: Build cpu32-system.o as common object
|
| cpu32.c only contains CPU types used in 32-bit system emulation:
| rename it as cpu32-system.c; always compile the file but only
| register the QOM types for the 32-bit binary.
| ... 6 lines of the commit log omitted.
Produces 38358 regressions 21 fixes:
|
| regressions.sum:
| Running g++:g++.dg/compat/compat.exp ...
| FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/bitfield2 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/pr83487-1 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| FAIL: g++.dg/compat/abi/pr83487-2 cp_compat_x_tst.o-cp_compat_y_tst.o execute
| ... and 38390 more
|
| fixes.sum:
| Running g++:g++.dg/vect/vect.exp ...
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++20 compilation failed to produce executable
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++26 compilation failed to produce executable
| UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++98 compilation failed to produce executable
| FAIL: g++.dg/vect/pr95401.cc -std=c++26 (test for excess errors)
| ... and 19 more
Used configuration :
*CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
*configure and test flags:* --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9
We track this bug report under https://linaro.atlassian.net/browse/GNU-1925. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/…
Full commit : https://gitlab.com/qemu-project/qemu/commit/c8bea1276c85855b2e088b740737d04…
Hi!
This seems to be an issue with your testing infrastructure. These
patches have not touched anything that isn't related to record-full so
there's no way they could be causing failures in gdb.arch tests. I guess
this test is no longer reliable.
--
Cheers,
Guinevere Larsen
It/she
On 6/7/26 3:44 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 gdb_check master-arm, after:
> | 3 patches in gdb
> | Patchwork URL: https://patchwork.sourceware.org/patch/136305
> | 1f3856ef4e9 [PATCH v4 3/8] gdb/record: remove record_full_insn_num
> | 9165d18a941 [PATCH v4 2/8] gdb/record: factor out reading and writing the execution log to corefile
> | 85ad6ec91da [PATCH v4 1/8] gdb/record: Refactor record history
> | ... applied on top of baseline commit:
> | 4562eab73d3 Automatic date update in version.in
>
> Produces 171 regressions:
> |
> | regressions.sum:
> | Running gdb:gdb.arch/skip-prologue.exp ...
> | FAIL: gdb.arch/skip-prologue.exp: f2: $\bp_addr == $\prologue_end_addr (skipped too much)
> | FAIL: gdb.arch/skip-prologue.exp: f4: $\bp_addr == $\prologue_end_addr (skipped too much)
> | Running gdb:gdb.arch/thumb2-it.exp ...
> | FAIL: gdb.arch/thumb2-it.exp: it_3, stepi 3
> | ... and 187 more
>
> Used configuration :
> *CI config* tcwg_gdb_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> 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_gdb_check--master-arm-precommit/builds/…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-build/builds/1021…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
This test is incorrect.
I apologize for the false detection.
The criteria used in the test are inappropriate. Therefore, we will correct the test.
It may take some time due to our internal release process, sorry.
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 年 5 月 30 日 (土曜日) 13:36
宛先: 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-23-init-16289-g9c26d8c30c19: 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_vls-lto-lld, after:
| commit llvmorg-23-init-16289-g9c26d8c30c19
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Thu May 21 10:30:09 2026 -0400
|
| [SLP] Unify IR flag and metadata propagation in vectorizeTree
|
| Replace scattered propagateIRFlags/propagateMetadata calls with a single
| PropagateIRFlags lambda. Excludes copyable scalars from the flag
| intersection set and drops nnan/ninf when a copyable lane cannot prove
| ... 5 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0118 ...
| FAIL: test-suite :: Fujitsu/Fortran/0118/Fujitsu-Fortran-0118_0266.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2228. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/9c26d8c30c1971881d710cf62d0f50b…
Sorry for dropping the ball on this. I'm not really set up to do arm
glibc testing, so I'd initially hoped that this was the same as PR125599.
It turned out to be a different bug, PR125653, which should be fixed by
r17-1422-g4ab2c727829c53.
Thanks,
Richard
ci_notify(a)linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | commit gcc-17-1238-g8e3eff39a456
> | Author: Richard Sandiford <rdsandiford(a)googlemail.com>
> | Date: Tue Jun 2 20:50:27 2026 +0100
> |
> | backprop: Move opt-out for abnormal edges
> |
> | r6-6843-ga864ad5ba2501d made sure that optimize_phi wouldn't
> | optimise phi inputs for abnormal edges. See:
> |
> | ... 17 lines of the commit log omitted.
>
> Produces 147 regressions:
> |
> | regressions.sum:
> | Running glibc:stdio-common ...
> | FAIL: stdio-common/tst-printf
> | FAIL: stdio-common/tst-printf-format-as-c
> | FAIL: stdio-common/tst-printf-format-as-char
> | FAIL: stdio-common/tst-printf-format-as-int
> | ... and 143 more
>
> Used configuration :
> *CI config* tcwg_gnu_native_check_glibc armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard
> --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
> --with-fpu=neon-fp-armv8
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1918. (Require Linaro login)
> Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-arm-buil…
> 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_check_glibc--master-arm-buil…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-arm-buil…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-arm-buil…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-arm-buil…
>
> 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
Hi,
This test is incorrect.
I apologize for the false detection.
The criteria used in the test are inappropriate. Therefore, we will correct the test.
It may take some time due to our internal release process, sorry.
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 年 5 月 20 日 (水曜日) 20:15
宛先: 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>; jacob.crawley(a)arm.com <jacob.crawley(a)arm.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-15894-g304d077d4324: 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_vls-lto-lld, after:
| commit llvmorg-23-init-15894-g304d077d4324
| Author: Jacob Crawley <jacob.crawley(a)arm.com>
| Date: Tue May 19 10:47:58 2026 +0100
|
| [AArch64] Add missing FSub case to isLegalToVectorizeReduction (#198302)
|
| Adds missing RecurKind::Fsub case to lower to partial reduction.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0022 ...
| FAIL: test-suite :: Fujitsu/C/0022/Fujitsu-C-0022_0039.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2221. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/304d077d43240d43408dc5595a00374…
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 v11.0.0-1575-gc9349965ce4
| Author: Richard Henderson <richard.henderson(a)linaro.org>
| Date: Wed May 20 14:51:39 2026 +0200
|
| tcg: Optimize INDEX_op_mul[us]2 for 0 and 1
|
| Zero operands produce a zero high and low product. One operands produce
| a copy of the other operand and a zero or sign extension in the high
| half.
| ... 8 lines of the commit log omitted.
Produces 6 regressions:
|
| regressions.sum:
| Running gcc:gcc.c-torture/execute/execute.exp ...
| FAIL: gcc.c-torture/execute/pr64006.c -O1 execution test
| FAIL: gcc.c-torture/execute/pr64006.c -O2 execution test
| FAIL: gcc.c-torture/execute/pr64006.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
| FAIL: gcc.c-torture/execute/pr64006.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
| ... and 2 more
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-1919. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-arm-build/b…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-arm-build/b…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-arm-build/b…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-arm-build/b…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_check_gcc--master-arm-build/b…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/…
Full commit : https://gitlab.com/qemu-project/qemu/commit/c9349965ce4a1548a0b19dc3cf859a4…
> lld-link: error: failed to write output 'bin\liblldb.dll': permission denied
Looks like a stuck process, can someone reboot the machine?
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.
Fixed with https://gcc.gnu.org/pipermail/gcc-cvs/2026-May/454624.html
On Fri, May 29, 2026 at 2:26 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-m55 hard, after:
> | commit gcc-17-761-g44c5f9a37aa
> | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com>
> | Date: Mon May 25 12:44:48 2026 -0700
> |
> | match: Fix up `(smaller)a ==/!= (smaller) b` pattern for pointers [PR125453]
> |
> | While reviewing r17-632-g1c9808a71207eb, I missed that it was valid (in gimple)
> | to cast from a pointer to a smaller integral type. That meant with that
> | pattern we would get `ptr ^ ptr` which is invalid gimple.
> | ... 16 lines of the commit log omitted.
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/torture/dg-torture.exp ...
> | FAIL: gcc.dg/torture/pr125453-1.c -O2 (test for excess errors)
> | FAIL: gcc.dg/torture/pr125453-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors)
> | FAIL: gcc.dg/torture/pr125453-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
> | FAIL: gcc.dg/torture/pr125453-1.c -O3 -g (test for excess errors)
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m55
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1915. (Require Linaro login) Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The full lists of regressions and improvements as well as configure and make commands are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> 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
On Tue, 26 May 2026 at 23:58, <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:
> | commit gcc-17-808-ge309e09187c
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu May 21 17:09:47 2026 +0100
> |
> | libstdc++: Deprecate std::memory_order::consume
> |
> | This implements P3475R2, "Defang and deprecate memory_order::consume",
> | approved in Hagenberg, 2025.
> |
> | ... 33 lines of the commit log omitted.
>
> Produces 21 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 29 not found: " *inlined from [^\n\r]+.C:23:.*"
> | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 44 not found: " *inlined from [^\n\r]+.C:36:.*"
> | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 46 not found: " *inlined from [^\n\r]+.C:39:.*"
> | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 74 not found: " *inlined from [^\n\r]+.C:66:.*"
> | ... and 17 more
>
> 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
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1912. (Require Linaro login) Please let us know if you have a fix.
This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125465
>
> 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-build/builds/…
> 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-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
Hi,
Probably this error is false detections caused by precision errors in floating-point arithmetic.
Please ignore the mail. We'll update the test.
I 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年5月24日 17:20
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: jason.van-beusekom(a)hpe.com <jason.van-beusekom(a)hpe.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-15954-g998d8e87daf3: 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-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-23-init-15954-g998d8e87daf3
| Author: Jason Van Beusekom <jason.van-beusekom(a)hpe.com>
| Date: Tue May 19 11:13:42 2026 -0500
|
| [Flang][Fir] Set default alignment of array globals to 64 bytes (#194969)
|
| This commit implements the proposal from the RFC:
| https://discourse.llvm.org/t/rfc-alignment-of-global-arrays/90397/13
|
| ... 3 lines of the commit log omitted.
Produces 2 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0679 ...
| FAIL: test-suite :: Fujitsu/Fortran/0679/Fujitsu-Fortran-0679_0248.test
| FAIL: test-suite :: Fujitsu/Fortran/0679/Fujitsu-Fortran-0679_0249.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2224. (Require Linaro login) Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/998d8e87daf371b51822ce97e360467…
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.43.9000-347-gb75ad99d45
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Fri May 22 14:08:13 2026 -0300
|
| elf: Initialize TCB and stack-protector before static IFUNC resolvers (BZ 20680, BZ 27582, BZ 28817)
|
| In static linking the IFUNC IPLT (apply_irel for non-PIE, the IRELATIVE
| phase inside _dl_relocate_static_pie for static-pie) ran before
| __libc_setup_tls and before _dl_setup_stack_chk_guard. When a resolver
| ... 45 lines of the commit log omitted.
Produces 170 regressions:
|
| regressions.sum:
| Running glibc:ctype ...
| FAIL: ctype/tst-ctype-tls-dlopen-static
| Running glibc:debug ...
| FAIL: debug/tst-sprintf-fortify-rdonly-static
| Running glibc:dlfcn ...
| ... and 180 more
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-1911. (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_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=b75ad99d45b7475eca46…
Hi,
Probably this error is false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the test.
I 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年5月19日 2:43
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: kese111(a)gmail.com <kese111(a)gmail.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-15486-gad7e6ca2b362: 1 regression 1 fix on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-23-init-15486-gad7e6ca2b362
| Author: hanbeom <kese111(a)gmail.com>
| Date: Fri May 15 15:06:39 2026 +0900
|
| [mlir][complex] Emit fma for contracted complex.mul lowering (#196248)
|
| When complex.mul has fastmath<contract>, lower it using explicit fused
| multiply-add operations for the real and imaginary components.
|
| ... 15 lines of the commit log omitted.
Produces 1 regression 1 fix:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0672 ...
| FAIL: test-suite :: Fujitsu/Fortran/0672/Fujitsu-Fortran-0672_0048.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/0289 ...
| FAIL: test-suite :: Fujitsu/Fortran/0289/Fujitsu-Fortran-0289_0033.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2220. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/ad7e6ca2b3624319b86543010961959…
On Sun, May 24, 2026 at 10:23 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 binutils_check master-aarch64, after:
> | binutils patch https://patchwork.sourceware.org/patch/135507
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Sat May 23 05:12:10 2026 +0800
> |
> | [PATCH v3] alpha: Don't assert elf_hash_table (info)->tls_sec != NULL
> |
> | When processing TLS relocations, elf_hash_table (info)->tls_sec can be
> | NULL if all TLS symbols are weak, hidden and undefined. Don't assert
> | elf_hash_table (info)->tls_sec != NULL. Since the undefined TLS symbol
> | ... 29 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | ee4da5f3ae2 Automatic date update in version.in
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running ld:ld-elf/tls.exp ...
> | FAIL: pr34165
This exposed an aarch64 linker bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=34165
--
H.J.
On Tue, May 19, 2026 at 2:22 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 aarch64 native, after:
> | commit gcc-17-570-g79e29562907b
> | Author: Avi Kivity <avi(a)scylladb.com>
> | Date: Thu Feb 26 19:59:41 2026 +0200
> |
> | libstdc++: optimize std::uninitialized_move{,_n}() to memcpy when
> possible [PR121789]
> |
> | std::uninitialized_move{,_n} delegates to the corresponding
> | std::uninitialized_copy() variant after wrapping with a move
> | iterator, but the std::uninitialized_copy() doesn't unwrap the
> | ... 17 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running g++:g++.dg/torture/dg-torture.exp ...
> | FAIL: g++.dg/torture/pr118521.C -O1 (test for excess errors)
>
I'll take a look.
>
> 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
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1906. Please let us know if you
> have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> 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-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
Hi,
With the https://github.com/llvm/llvm-project/commit/3def12d2a418f8e49f0b88ddf9070af… , the result of `ieee_support_rounding()` for `ieee_other` has been corrected so that `.false.` is now the correct value.
This test expects `.true.`, but following the correction above, the correct result is now `.false.`. Therefore, this test is incorrect.
I apologize for the false detection.
We'll correct this test. It may take some time due to our internal release process, sorry.
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年5月16日 14:38
宛先: 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>; kwyatt.external(a)hpe.com <kwyatt.external(a)hpe.com>
件名: [Linaro-TCWG-CI] llvmorg-23-init-15424-g3def12d2a418: 1 regression on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-23-init-15424-g3def12d2a418
| Author: kwyatt-ext <kwyatt.external(a)hpe.com>
| Date: Thu May 14 13:17:40 2026 -0500
|
| [flang] Corrected constant folding for IEEE_OTHER in IEEE_SUPPORT_ROUNDING (#197534)
|
| Modified to report expected value of FALSE for constant folded
| IEEE_OTHER support.
|
| ... 1 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0923 ...
| FAIL: test-suite :: Fujitsu/Fortran/0923/Fujitsu-Fortran-0923_0004.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2219. 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/3def12d2a418f8e49f0b88ddf9070af…
Hello -
I believe this test is in error. The Flang source was modified to correctly report that IEEE_OTHER is not supported (see flang/docs/Extensions.md). Otherwise, what processor was this running on? Does it support IEEE_OTHER?
Thanks
Kevin Wyatt
kwyatt-ext(a)hpe.com
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Saturday, May 16, 2026 12:39 AM
To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com
Cc: maxim.kuvyrkov(a)linaro.org; Wyatt, Kevin <kwyatt(a)hpe.com>
Subject: [Linaro-TCWG-CI] llvmorg-23-init-15424-g3def12d2a418: 1 regression on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after:
| commit llvmorg-23-init-15424-g3def12d2a418
| Author: kwyatt-ext <kwyatt.external(a)hpe.com>
| Date: Thu May 14 13:17:40 2026 -0500
|
| [flang] Corrected constant folding for IEEE_OTHER in IEEE_SUPPORT_ROUNDING (#197534)
|
| Modified to report expected value of FALSE for constant folded
| IEEE_OTHER support.
|
| ... 1 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0923 ...
| FAIL: test-suite :: Fujitsu/Fortran/0923/Fujitsu-Fortran-0923_0004.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
We track this bug report under https://urldefense.com/v3/__https://linaro.atlassian.net/browse/LLVM-2219__… . Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-…
The full lists of regressions and improvements as well as configure and make commands are in
* https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-…
The list of [ignored] baseline and flaky failures are in
* https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-…
Reference build : https://urldefense.com/v3/__http://54.172.246.49:9090/jobs/tcwg_flang_test-…
Instruction to reproduce the build : https://urldefense.com/v3/__https://gitlab.com/LinaroLtd/tcwg/ci/interestin…
Full commit : https://github.com/llvm/llvm-project/commit/3def12d2a418f8e49f0b88ddf9070af…
Hi,
These tests are incorrect.
Details are as follows:
OpenMP 6.0 : 7.1.1 Variables Referenced in a Construct
The loop-iteration variable in any affected loop of a loop-nest-associated directive may be listed in a private or lastprivate clause.
->Therefore, a shared clause cannot be specified.
I apologize for the false detection.
We'll correct these tests. It may take some time due to our internal release process, sorry.
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年5月3日 8:11
宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com>
CC: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>
件名: [Linaro-TCWG-CI] llvmorg-23-init-13786-gc549abab5d18: 5 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-23-init-13786-gc549abab5d18
| Author: Krzysztof Parzyszek <Krzysztof.Parzyszek(a)amd.com>
| Date: Fri May 1 08:09:36 2026 -0500
|
| [flang][OpenMP] Check conflicts between predetermined/explicit DSA (#194961)
|
| Improve checks for loop iteration variables with predetermined DSA
| appearing in DSA clauses. Show both the location of the variable in the
| offending clause, and in the loop.
| ... 3 lines of the commit log omitted.
Produces 5 regressions:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0162 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0162/Fujitsu-Fortran-0162_0024.test
| Running test-suite:Fujitsu/Fortran/0165 ...
| NOEXE: test-suite :: Fujitsu/Fortran/0165/Fujitsu-Fortran-0165_0026.test
| NOEXE: test-suite :: Fujitsu/Fortran/0165/Fujitsu-Fortran-0165_0027.test
| ... and 2 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="-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-2214. 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/c549abab5d18bae56ef9b91d5991fa6…
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In aarch64 cross, after:
| commit binutils-2_41-release-10810-g520c7eefed7
| Author: Simon Marchi <simon.marchi(a)efficios.com>
| Date: Thu May 7 15:23:12 2026 -0400
|
| binutils/configure: look for msgpack-c.pc (in addition to msgpack.pc)
|
| msgpack.pc was renamed to msgpack-c.pc in this commit [1]. This means
| that we now find both in the wild. For example Debian Bookworm has
| msgpack.pc [2] while Debian Trixie has msgpack-c.pc [3].
| ... 7 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| # FAILED
| # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a:
| # build_abe linux:
| # build_abe glibc:
| # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a:
| # build_abe gdb:
| # build_abe qemu:
| # First few build errors in logs:
| # 00:01:19 configure: error: Package requirements (msgpack) were not met:
| # 00:01:19 make[1]: *** [Makefile:4066: configure-binutils] Error 1
| # 00:01:19 make: *** [Makefile:1033: all] Error 2
|
| From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe binutils:
| 1
| # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a:
| 2
| # build_abe linux:
| 3
| # build_abe glibc:
| 4
| # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a:
| 5
| # build_abe gdb:
| 6
| # build_abe qemu:
| 7
Used configuration :
*CI config* tcwg_gnu_cross_build aarch64-linux-gnu cross
*configure and test flags:* --target aarch64-linux-gnu --disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a
We track this bug report under https://linaro.atlassian.net/browse/GNU-1903. 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_cross_build--master-aarch64-build/b…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_gnu_cross_build--master-aarch64-build/b…
Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_build--master-aarch64-build/b…
Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_build--master-aarch64-build/b…
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=520c7eefed7f9…
On Thu, May 14, 2026 at 7:43 PM <ci_notify(a)linaro.org> wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | commit gcc-17-496-gda540dc6d763
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Wed May 13 14:51:02 2026 +0200
> |
> | libstdc++: Test for unsupported engine range for 128bits floating
> points [PR119739]
> |
> | This patch add test illustrating, that after implementing P0952 "A
> new specification for
> | std::generate_canonical", generators, that emit range of
> non-power-of-two size, that
> | span over B bits, are not supported in combination with 128bits
> integer are not
> | ... 16 lines of the commit log omitted.
>
> Produces 7 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL:
> 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc
> -std=gnu++20 (test for errors, line 57)
> | FAIL:
> 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc
> -std=gnu++20 (test for errors, line 58)
> | FAIL:
> 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc
> -std=gnu++20 (test for errors, line 65)
> | FAIL:
> 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc
> -std=gnu++20 (test for errors, line 66)
> | ... and 3 more
>
> Used configuration :
> *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard
> --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
> --with-fpu=neon-fp-armv8
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1902. Please let us know if you
> have a fix.
>
Thanks for the report. This should already be fixed on trunk by
https://gcc.gnu.org/cgit/gcc/commit/?id=5d17eec7d83445ba4f960c81c386be33bae…
libstdc++: Mark gencanon_eng_neg test as unsupported if __float128 is not
available
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020…
>
> 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
>
Hi,
Probably these errors are false detections caused by precision errors in floating-point arithmetic.
Please ignore the mail. We'll update the tests. I apologize for the false detection.
Details are as follows.
The primary purpose of this TP (https://github.com/fujitsu/compiler-test-suite/blob/main/Fortran/0683/0683_…) is to verify OpenMP SIMD reduction.
However, since -fopenmp is not specified, !$omp simd is treated as a comment.
Consequently, we are currently verifying the results of sequential calculations for single-precision complex numbers.
In this TP, we determine whether the result is OK or NG by calculating the size of the complex difference in the accumulation results for single-precision complex numbers.
Due to SLP vectorization, a difference arose in the accumulation results, and the difference between the calculated value and the expected value was 3 ULP in the real part and 5 ULP in the imaginary part.
Consequently, the size of the complex difference is 5.8309517, which exceeds the threshold of 5.0, resulting in an NG.
Since the difference is approximately 5 ULP, it is considered to be within the range of rounding errors associated with single-precision complex integration.
if (abs(ss-result) < 5.0) then
print *, "PASS"
else
print *, ss, abs(ss-result)
endif
Expected values: (-15069242.0, -9596797.00)
Actual values: (-15069245.0, -9596802.00)
Therefore, we make the following two corrections.
・To verify OpenMP SIMD reduction, which is the original objective, specify the -fopenmp option.
・Due to vectorization, a difference of 3 ULP in the real part and 5 ULP in the imaginary part has arisen in the single-precision complex multiplication. In this test, the size of the complex difference is calculated as abs(ss - result)\
, but the current threshold of 5.0 does not allow for a complex difference of 5.8309517. To allow for rounding errors of approximately 5 ULP as complex differences, the threshold will be relaxed from 5.0 to 6.0.
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 年 4 月 30 日 (木曜日) 0:41
宛先: 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-23-init-12953-g1348766d1d68: 1 regression on aarch64
[Some people who received this message don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
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-23-init-12953-g1348766d1d68
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Sat Apr 25 07:27:36 2026 -0400
|
| [SLP]Initial support for non-power-of-2 vectorization
|
| Enables non-power-of-2 vectorization within the SLP tree. The root nodes
| are still required to be power-of-2, will be addressed in a follow-up
| patches.
| ... 4 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/Fortran/0683 ...
| FAIL: test-suite :: Fujitsu/Fortran/0683/Fujitsu-Fortran-0683_0101.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-2211. 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/1348766d1d686b8825bdaa2f6638c17…
Typo in this email :
We track this bug report under https://linaro.atlassian.net/browse/GNU-1898
. Please let us know if you have a fix.
On Tue, 5 May 2026 at 23:21, <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-m55 hard, after:
> | commit gcc-17-277-gc0c911821ba
> | Author: Xi Ruoyao <xry111(a)xry111.site>
> | Date: Sat May 2 02:15:42 2026 +0800
> |
> | testsuite: don't link top-level asm tests as PIE [PR 70150]
> |
> | If these tests are linked as PIE, the linker ends up creating
> runtime
> | text relocation and warns or errors out.
> |
> | ... 8 lines of the commit log omitted.
>
> Produces 3 regressions 3 fixes:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/lto/lto.exp ...
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=1to1 -no-pie
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=cache -no-pie
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=max -no-pie
> |
> | fixes.sum:
> | Running gcc:gcc.dg/lto/lto.exp ...
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=1to1
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=cache
> | FAIL: gcc.dg/lto/toplevel-simple-asm-1
> c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2
> -flto -flto-toplevel-asm-heuristics -flto-partition=max
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb
> -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard
> -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard
> --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto
> qemu-cpu=cortex-m55
>
> We track this bug report under https://linaro.atlassian.net/browse/Please
> specify 'Project' and 'IssueType'.. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> 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
Typo in this email :
We track this bug report under https://linaro.atlassian.net/browse/GNU-1897
. Please let us know if you have a fix.
On Fri, 8 May 2026 at 17:49, <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 bootstrap_build master-aarch64-bootstrap_debug, after:
> | commit gcc-17-383-g1a06a37611e
> | Author: Roger Sayle <roger(a)nextmovesoftware.com>
> | Date: Thu May 7 18:46:37 2026 +0100
> |
> | PR middle-end/122871: Doubleword multiplication improvements
> |
> | This patch resolves PR middle-end/122871 by improving RTL
> expansion of
> | doubleword multiplications. The main change is to synth_mult
> adding
> | support for the case where the constant being multiplied has
> BITS_PER_WORD
> | ... 64 lines of the commit log omitted.
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap_debug:
> | # FAILED
> | # First few build errors in logs:
> | # 00:24:37
> /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/expmed.h:398:61:
> error: array subscript -1 is below array bounds of ‘int [64]’
> [-Werror=array-bounds=]
> | # 00:24:50 make[3]: *** [Makefile:1217: expmed.o] Error 1
> | # 00:24:50 make[2]: *** [Makefile:5182: all-stage2-gcc] Error 2
> | # 00:24:50 make[1]: *** [Makefile:26490: stage2-bubble] Error 2
> | # 00:24:50 make: *** [Makefile:1140: all] Error 2
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap_debug:
> | 1
>
> Used configuration :
> *CI config* tcwg_bootstrap_build master-aarch64-bootstrap_debug
> *configure and test flags:* none, autodetected on
> aarch64-unknown-linux-gnu
>
> We track this bug report under https://linaro.atlassian.net/browse/Please
> specify 'Project' and 'IssueType'.. 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_bootstrap_build--master-aarch64-bootstr…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr…
>
> 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
Typo in this email :
We track this bug report under https://linaro.atlassian.net/browse/GNU-1896
. Please let us know if you have a fix.
On Thu, 7 May 2026 at 18:52, <ci_notify(a)linaro.org> wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | commit gcc-17-359-g9a231dbb68ab
> | Author: David Malcolm <dmalcolm(a)redhat.com>
> | Date: Wed May 6 09:57:07 2026 -0400
> |
> | analyzer: add data flow events
> |
> | Analyzer warnings relating to problematic values (e.g. by division
> | by zero) can be difficult for the user to understand.
> |
> | ... 421 lines of the commit log omitted.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/analyzer/analyzer.exp ...
> | FAIL: gcc.dg/analyzer/divide-by-zero-6.c (test for warnings, line 17)
> | FAIL: gcc.dg/analyzer/divide-by-zero-6.c at line 18 (test for
> warnings, line 17)
> | FAIL: gcc.dg/analyzer/divide-by-zero-6.c (test for excess errors)
>
> Used configuration :
> *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard
> --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
> --with-fpu=neon-fp-armv8
>
> We track this bug report under https://linaro.atlassian.net/browse/Please
> specify 'Project' and 'IssueType'.. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017…
>
> 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
Hi,
Neither the reference nor the current build includes later fixes for
zero_padding.cc file, in particular:
> commit 3a41229f92022bfb388911854d597721fce76714
> Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> Date: Thu Mar 5 08:57:24 2026 +0100
>
> libstdc++: Fix atomic/cons/zero_padding.cc test for arm-none-eabi
[PR124124]
>
> The test uses dg-require-atomic-cmpxchg-word that checks if atomic
compare
> exchange is available for pointer sized integers, and then test types
that
> are eight bytes in size. This causes issue for targets for which
pointers
> are four byte and libatomic is not present, like arm-none-eabi.
> commit f3ba5ad088cebe117f857329a35b95d18d97a808
> Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> Date: Tue Feb 17 13:35:39 2026 +0100
>
> libstdc++: Correct requirements for atomic/cons/zero_padding.cc tests
again [PR124124]
>
> The requirements introduced in previous patch r16-7548-g060d7c2a9c1fe1,
> were not sufficient for types of size bigger than 64B (Ctor or long
double),
> as dg-add-options of libatomic, links libatomic only if it is required
to
> handle atomics of 64B types or pointers.
Are issue still present on thunk build?
On Mon, Apr 20, 2026 at 10:28 PM <ci_notify(a)linaro.org> wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please
> find some details below.
>
> In arm-eabi cortex-m55 hard, after:
> | commit gcc-16-7460-g682c95b80872
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Wed Feb 11 15:05:00 2026 +0100
> |
> | libstdc++: Add test for atomic with padding on heap [PR123875]
> |
> | C++26 makes the values of uninitialized stack object erroneous,
> | de-facto requiring their initialization, so adding a test for
> | variable on heap.
> | ... 8 lines of the commit log omitted.
>
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb
> -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard
> -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard
> --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto
> qemu-cpu=cortex-m55
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1877. Please let us know if you
> have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h…
>
> 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
>
ci_notify(a)linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In armv8l-unknown-linux-gnueabihf native, after:
> | gcc patch https://patchwork.sourceware.org/patch/133402
> | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE>
> | Date: Mon Apr 20 18:29:40 2026 +0200
> |
> | [PATCH] testsuite: Check configured assembler in gcc.misc-tests/options.exp
> |
> | When I recently dropped --with-gnu-as from my builds which had become
> | unnecessary, several tests started to FAIL, e.g.
> |
> | ... 45 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 416fe77efb4 d: Fix ICE in must_pass_in_stack_var_size_or_pad with D enums [PR123411]
It's good to see you're running pre-commit checks. However, this report
is particularly confusing in its current form: while the Subject states
"no pregression/no fix on arm", the report starts with
Our automatic CI has detected problems related to your patch(es). Please find some details below.
^^^^^^^^^^^^^^^^^^^^^
That sent me looking for regressions, but I couldn't find any. At first
I thought I was beeing particularly stupid, but it seems that your CI
found no issues at all with the patch.
So please say so *prominently* in the body of the message, rather than
confusing contributors and wasting their time.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
Hello there,
According to the list of regressions below, all the failing tests are
for the C compiler. I am at a bit of a loss to know how to proceed
since the patch that you have fingered applies exclusively to fortran.
Best regards
Paul
---------- Forwarded message ---------
From: <ci_notify(a)linaro.org>
Date: Sun, 19 Apr 2026 at 23:05
Subject: [Linaro-TCWG-CI] gcc patch #133364: 113 regressions on aarch64
To: <paul.richard.thomas(a)gmail.com>
Cc: <pault(a)gcc.gnu.org>
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/133364
| Author: Paul Thomas <pault(a)gcc.gnu.org>
| Date: Sun Apr 19 15:00:14 2026 +0100
|
| [PATCH] Fortran: ICE due to allocatable component in hidden
type [PR117077]
|
| 2026-03-19 Paul Thomas <pault(a)gcc.gnu.org>
|
| gcc/fortran
| ... 8 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 68920b1f14d cse: Validate subreg replacements [PR124643]
Produces 113 regressions:
|
| regressions.sum:
| Running g++:g++.target/aarch64/aarch64.exp ...
| FAIL: g++.target/aarch64/pr117048.C scan-assembler
\\txar\\tv[0-9]+\\.2d, v[0-9]+\\.2d, v[0-9]+\\.2d, 32\\n
| Running g++:g++.target/aarch64/sme2/aarch64-sme2-acle-asm.exp ...
| FAIL: gcc.target/aarch64/sme2/acle-asm/svluti4_zt_1.c -std=c++11
-O0 -g -DTEST_FULL (test for excess errors)
| FAIL: gcc.target/aarch64/sme2/acle-asm/svluti4_zt_1.c -std=c++11
-O0 -g -DTEST_OVERLOADS (test for excess errors)
| ... and 120 more
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.
This test failure is pre-existing on master and is not introduced by this
series. I verified that vanilla master (commit d3e7d81adc8, the baseline
cited by the CI report) produces identical output to the patched build for
the Egypt walk in test_egypt() — the diff is empty.
The test's hardcoded expected output expects ambiguous local_info results
at certain EEST→EET fall-back transitions (2003, 2005, 2007, 2009, 2010),
but the current master code produces two consecutive
unique EET intervals instead (a 1-hour interval followed by the long winter
interval, same offset/save/abbrev). This looks like a pre-existing
consequence of the merge block in _M_get_sys_info being #if 0'd out.
--Álvaro.
On Sun, Apr 12, 2026 at 1:40 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 armv8l-unknown-linux-gnueabihf native, after:
> | 5 patches in gcc
> | Patchwork URL: https://patchwork.sourceware.org/patch/132945
> | 9c1142da97d [PATCH 5/5] libstdc++: Implement zic writezone merge
> optimization [PR 124854]
> | 4647ebca332 [PATCH 4/5] libstdc++: Cascade wall-time saves in lazy
> expansion seeding [PR 124853]
> | f5a3c3c82e2 [PATCH 3/5] libstdc++: Resolve named-rule UNTIL save
> adjustment [PR116110]
> | e31e5de33bb [PATCH 2/5] libstdc++: Support ON-format DAY in Zone UNTIL
> field [PR 124852]
> | a607854b476 [PATCH 1/5] libstdc++: Fix numeric save offset on Zone
> lines [PR 124851]
> | ... applied on top of baseline commit:
> | d3e7d81adc8 Daily bump.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: std/time/time_zone/get_info_local.cc -std=gnu++20 execution test
>
> Used configuration :
> *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf
> *configure and test flags:* none, autodetected on
> armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard
> --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a
> --with-fpu=neon-fp-armv8
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1008…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
On Sun, Apr 19, 2026 at 9:16 PM <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In glibc_check master-arm, after:
> | glibc patch https://patchwork.sourceware.org/patch/133360
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Mon Apr 13 08:23:05 2026 +0800
> |
> | [PATCH v4] elf: Support THP segment load with madvise enabled THP
> |
> | The current THP segment load approach works only when THP is enabled
> | with always in the kernel. If THP is enabled with madvise in the
> | kernel, to enable THP segment load in an application, madvise should
> | ... 36 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 0664c8e2761 localedata: Consistently use one space after 'category'
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running glibc:elf ...
> | FAIL: elf/tst-thp-1-no-s-code-pde
> | FAIL: elf/tst-thp-1-no-s-code-static
> | FAIL: elf/tst-thp-1-pde
> | FAIL: elf/tst-thp-1-static
What do they report, like in elf/tst-thp-1-pde.out? What is in
/sys/kernel/mm/transparent_hugepage/hpage_pmd_size?
> Used configuration :
> *CI config* tcwg_glibc_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> 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_glibc_check--master-arm-precommit/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_glibc_check--master-arm-precommit/build…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
--
H.J.
On Fri, 17 Apr 2026 at 06:03, <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/133193
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Apr 16 15:21:49 2026 +0100
> |
> | [PATCH v2] libstdc++: Add module initialization functions to the library [PR124268]
> |
> | This tries to ensure that the module init functions are present in
> | libstdc++.so and libstdc++.a, so that users of the std and std.compat
> | modules don't need to manually link to std.o and/or std.compat.o in
> | ... 32 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 20230911fca Daily bump.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ...
> | FAIL: libstdc++-prettyprinters/debug.cc print redirected
> | FAIL: libstdc++-prettyprinters/simple.cc print redirected
> | FAIL: libstdc++-prettyprinters/simple11.cc print redirected
>
> 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.
I don't understand how these failures can possibly be caused by the
patch, and I don't see them on cfarm185 (Ampere eMAG
aarch64-linux-gnu, almalinux 8.10) or on any other *-*-linux-gnu
targets, nor solaris.
>
> -----------------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.
The test fails on arm-eabi when testing with the following settings:
-mlittle-endian -mfloat-abi=hard -mcpu=cortex-a9 -mfpu=vfpv3
It only fails in the following torture option set:
-O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions
It also fails on numerous other 32-bit targets, but it depends on how
the memcpy-like loop gets vectorized and unrolled.
I hope we can live with the XPASSes.
On Apr 11, 2026, 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 thumb v8-a hard, after:
> | commit gcc-16-6952-g14cd2833b27a
> | Author: Alexandre Oliva <oliva(a)adacore.com>
> | Date: Wed Jan 21 00:30:24 2026 -0300
> |
> | testsuite: tolerate bogus warning in pr113026-1.c [PR113524]
> |
> | The bogus warning in pr113026-1.c is issued at some optimization
> | levels on various 32-bit targets.
> |
> | ... 6 lines of the commit log omitted.
> Produces 7 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.dg/torture/dg-torture.exp ...
> | XPASS: gcc.dg/torture/pr113026-1.c -O0 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O1 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O2 PR118504 (test for bogus messages, line 12)
> | XPASS: gcc.dg/torture/pr113026-1.c -O2 -flto
> | -fno-use-linker-plugin -flto-partition=none PR118504 (test for
> | bogus messages, line 12)
> | ... and 3 more
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb
> -march=armv8-a+simd -mfpu=auto -mfloat-abi=hard
> *configure and test flags:* --target arm-eabi --disable-multilib
> --with-mode=thumb --with-arch=armv8-a+simd
> --with-fpu=crypto-neon-fp-armv8 --with-float=hard
> --target_board=-mthumb/-march=armv8-a+simd/-mfpu=auto/-mfloat-abi=hard
> qemu_cpu=any
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1870. Please let us know if
> you have a fix.
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below contains the details of the failures, and the
> ways to reproduce a debug environment:
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> The full lists of regressions and improvements as well as configure
> and make commands are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h…
> 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
--
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!
Hi!
On 4/3/26 08:06, ci_notify--- via Gcc-regression wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In aarch64 native, after:
> | commit gcc-16-8401-g71033b1dfbd1
> | Author: Roger Sayle <roger(a)nextmovesoftware.com>
> | Date: Wed Apr 1 23:54:50 2026 +0100
> |
> | PR target/123238: VCOND_MASK regression on aarch64.
> |
> | This patch fixes the regression PR target/123238 on aarch64, using the
> | changes to aarch64's aarch64_rtx_costs proposed by Tamar Christina.
> |
> | ... 38 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/aarch64.exp ...
> | FAIL: gcc.target/aarch64/pr123238.c scan-assembler-not not
>
This was fixed by Andrew in:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9c694b3ecd0eb5308e85a0eac69c4…
Thanks,
Christophe
> 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
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1868. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> 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-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
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,
Probably these errors are false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the tests.
I 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 年 4 月 12 日 (日曜日) 17:45
宛先: 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-23-init-11166-g8ac9461e48e0: 1 regression 1 fix on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
| commit llvmorg-23-init-11166-g8ac9461e48e0
| Author: Alexey Bataev <a.bataev(a)outlook.com>
| Date: Sat Apr 11 08:18:36 2026 -0400
|
| [SLP] Reject 2-element vectorization when vector inst count exceeds scalar
|
| The LLVM cost model uses integer-valued throughput costs which cannot
| represent fractional costs. For 2-element vectors, this rounding can
| make vectorization appear profitable when it actually produces more
| ... 15 lines of the commit log omitted.
Produces 1 regression 1 fix:
|
| regressions.sum:
| Running test-suite:Fujitsu/C/0121 ...
| FAIL: test-suite :: Fujitsu/C/0121/Fujitsu-C-0121_0259.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/0640 ...
| FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0216.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2210. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/8ac9461e48e024448a2b6493b7c5b50…
Hi there,
I got a notification about a build failure on the flang-arm64-windows-msvc buildbot earlier today, I’ve included the original email below.
The commit in question that caused the failure added some new intrinsics, touching some tablegen files, which then caused some tests for unrelated intrinsics to fail: https://github.com/llvm/llvm-project/commit/9ba774566e27b76b9c7c2b2ddd108c1…https://lab.llvm.org/buildbot/#/builders/207/builds/15865
But the buildbot went back to green in https://lab.llvm.org/buildbot/#/builders/207/builds/15869 when another PR changed some other tablegen files in the llvm project. I didn’t revert or commit any fixes in the meantime.
Is there maybe some issue with the build cache and how tablegen files interact with it? Just thought I’d flag this to you anyway.
Many thanks
Luke
> Begin forwarded message:
>
> From: llvm.buildmaster(a)lab.llvm.org
> Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed test (failure) (main)
> Date: 9 April 2026 at 16:03:07 GMT+8
> To: "Luke Lau" <luke(a)igalia.com>, "Nikita Popov" <npopov(a)redhat.com>
> Cc: llvm.buildmaster(a)lab.llvm.org
> Reply-To: llvm.buildmaster(a)lab.llvm.org
>
> The Buildbot has detected a new failure on builder flang-arm64-windows-msvc while building llvm.
>
> Full details are available at:
> https://lab.llvm.org/buildbot/#/builders/207/builds/15865
>
> Worker for this Build: linaro-armv8-windows-msvc-01
> Blamelist:
> Luke Lau <luke(a)igalia.com>,
> Nikita Popov <npopov(a)redhat.com>
>
> BUILD FAILED: failed test (failure)
>
> Step 6 (test-build-unified-tree-check-mlir) failure: test (failure)
> ******************** TEST 'MLIR :: mlir-runner/test-expand-math-approx.mlir' FAILED ********************
> Exit Code: 2
>
> Command Output (stdout):
> --
> # RUN: at line 1
> c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir -pass-pipeline="builtin.module(func.func(math-expand-ops),convert-vector-to-scf,convert-scf-to-cf,convert-vector-to-llvm,convert-to-llvm,reconcile-unrealized-casts)" | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe -e main -entry-point-result=void -O0 -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_c_runner_utils.dll -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_runner_utils.dll -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_float16_utils.dll | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-ms
> vc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir
> # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir' '-pass-pipeline=builtin.module(func.func(math-expand-ops),convert-vector-to-scf,convert-scf-to-cf,convert-vector-to-llvm,convert-to-llvm,reconcile-unrealized-casts)'
> # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe' -e main -entry-point-result=void -O0 '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_c_runner_utils.dll' '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_runner_utils.dll' '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_float16_utils.dll'
> # .---command stderr------------
> # | LLVM ERROR: Cannot select: intrinsic %llvm.aarch64.neon.ushl
> # | PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace and instructions to reproduce the bug.
> # | Stack dump:
> # | 0. Program arguments: c:\\users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir-runner.exe -e main -entry-point-result=void -O0 -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_c_runner_utils.dll -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_runner_utils.dll -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_float16_utils.dll
> # | 1. Running pass 'Function Pass Manager' on module 'LLVMDialectModule'.
> # | 2. Running pass 'AArch64 Instruction Selection' on function '@"func_roundeven32$vector"'
> # | Exception Code: 0xC000001D
> # | #0 0x00007ff674c89e4c mlir::detail::FallbackTypeIDResolver::registerImplicitTypeID(class llvm::StringRef) (c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe+0x309e4c)
> # | #1 0x00007ffec74aae50 (C:\WINDOWS\System32\ucrtbase.dll+0x7ae50)
> # | #2 0xa25cfffec74aba5c
> # `-----------------------------
> # error: command failed with exit status: 0xc000001d
> # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir'
> # .---command stderr------------
> # | FileCheck error: '<stdin>' is empty.
> # | FileCheck command line: c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir
> # `-----------------------------
> # error: command failed with exit status: 2
>
> --
>
> ********************
>
>
> Sincerely,
> LLVM Buildbot
>
This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124828.
On Fri, Apr 10, 2026 at 1:15 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 aarch64 native, after:
> | commit gcc-16-8510-g395e5cef29d9
> | Author: Tomasz Kamiński <tkaminsk(a)redhat.com>
> | Date: Wed Apr 1 14:32:21 2026 +0200
> |
> | libstdc++: Export explicit instantiations for C++20 members of
> std::string
> |
> | The C++20 standard added new starts_with and ends_with members to
> | std::basic_string, which were not previously instantiated in the
> library.
> | This meant that the extern template declarations had to be
> disabled for
> | ... 31 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running g++:g++.dg/lto/lto.exp ...
> | FAIL: g++.dg/lto/20091022-2
> cp_lto_20091022-2_0.o-cp_lto_20091022-2_0.o link, -O3 -flto -Winline
>
> 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
>
> We track this bug report under
> https://linaro.atlassian.net/browse/GNU-1869. Please let us know if you
> have a fix.
>
> If you have any questions regarding this report, please ask on
> linaro-toolchain(a)lists.linaro.org mailing list.
>
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways
> to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> 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-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> *
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build :
> http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
>
On Thu, 2 Apr 2026 at 06:27, <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:
> | commit gcc-16-8385-gc9525a790291
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Mon Mar 30 12:13:39 2026 +0100
> |
> | libstdc++: Rename saturation arithmetic for C++26 (P4052R0)
> |
> | Last week in Croydon we approved P4052R0 to rename std::add_sat etc. for
> | C++26
> |
> | ... 16 lines of the commit log omitted.
>
> Produces 3 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/modules/modules.exp ...
> | FAIL: g++.dg/modules/compile-std1.C -std=c++26 (test for excess errors)
> | FAIL: g++.dg/modules/compile-std1.C module-cmi std (gcm.cache/std.gcm)
> | FAIL: g++.dg/modules/compile-std1.C module-cmi std.compat (gcm.cache/std.compat.gcm)
>
> 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
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1867. Please let us know if you have a fix.
It's fixed now
>
> 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-build/builds/…
> 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-build/builds/…
> The list of [ignored] baseline and flaky failures are in
> * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
> Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/…
>
> 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
Hi,
These errors are caused by incorrect test programs. Please ignore the mail. We'll update the tests.
I apologize for the false detection.
Best regards,
Shunsuke Watanabe
Software Development Div.,
Advanced Technology Development Unit,
Fujitsu Research, Fujitsu Limited, JAPAN.
-----Original Message-----
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Wednesday, April 1, 2026 2:37 AM
To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com
Cc: aidengrossman(a)google.com; maxim.kuvyrkov(a)linaro.org
Subject: [Linaro-TCWG-CI] llvmorg-23-init-9791-g12319b373a5f: 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_vls-lto-lld, after:
| commit llvmorg-23-init-9791-g12319b373a5f
| Author: Aiden Grossman <aidengrossman(a)google.com>
| Date: Mon Mar 30 16:34:37 2026 -0700
|
| [Clang] More aggressively mark this* dead_on_return in destructors (#183347)
|
| Now also mark the this pointer dead_on_return for classes with a
| non-zero number of base classes. We saw a limited number of failures
| internally due to this change, so it doesn't seem like there are too
| ... 1 lines of the commit log omitted.
Produces 1 regression:
|
| regressions.sum:
| Running test-suite:Fujitsu/C++/0032 ...
| FAIL: test-suite :: Fujitsu/C++/0032/Fujitsu-C++-0032_1052.test
| # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
Used configuration :
* Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
* Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite"
We track this bug report under https://linaro.atlassian.net/browse/LLVM-2208. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
You can find the failure logs in *.log.1.xz files in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The full lists of regressions and improvements as well as configure and make commands are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
The list of [ignored] baseline and flaky failures are in
* http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/
Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-…
Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/…
Full commit : https://github.com/llvm/llvm-project/commit/12319b373a5f4b36c09165ed7f8e967…