- linaro-toolchain - lists.linaro.org

[Linaro-TCWG-CI] v11.1.0-294-g3181e53c13a: 1 regression on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In aarch64 cross, after: | commit v11.1.0-294-g3181e53c13a | Author: Richard Henderson <richard.henderson(a)linaro.org> | Date: Tue Aug 11 15:51:33 2026 -0700 | | tcg/optimize: INDEX_op_mul is commutative | | Cc: qemu-stable(a)nongnu.org | Fixes: 7a2f7084525 ("tcg/optimize: Sink commutative operand swapping into fold functions") | Reviewed-by: Philippe Mathieu-Daudé <philmd(a)oss.qualcomm.com> | ... 1 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running gcc:gcc.c-torture/execute/execute.exp ... | FAIL: gcc.c-torture/execute/pr64006.c -O3 -g execution test 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-2009. (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/qemu/… Full commit : https://gitlab.com/qemu-project/qemu/commit/3181e53c13a1a68e2b54c94b1766f8e…

1 month, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-24-init-4794-gefd053f8ef30: 3 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

1 month, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.44.9000-91-gdfacfbbdbb2: 2 regressions on arm

by ci_notify＠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: | commit glibc-2.44.9000-91-gdfacfbbdbb2 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Mon Aug 24 13:45:53 2026 -0300 | | Revert "tests: Remove target-specific huge-page size definition for THP-aware load segment alignment" | | This reverts commit 224cb4a8ddd60d989790ab3da0e145c70be0a421. The | change broke the build of some THP tests on arc and or1k [1]. | | ... 1 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running glibc:elf ... | XPASS: elf/tst-thp-1-no-s-code-static | XPASS: elf/tst-thp-1-static 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-2007. (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=dfacfbbdbb2bb408e2c5…

1 month, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-17-3278-gb6477e6c4ef: 1 regression on aarch64

by Longjun Luo

Thanks for the report. I compared builds 10158 and 10159. The additional breakpoint is for _dl_relocate_static_pie_ifunc in static-reloc.c:28. Before b6477e6c4ef, the function and its symbol were already present, but its IPA-ICF wrapper had no address-bearing subprogram DIE. With the change, GDB can now see the function when minsyms=False and set a breakpoint on it. This is the behavior PR debug/126355 was intended to restore, so the result also provides useful confirmation that the GCC fix is effective. The failure comes from py-rbreak.exp using the unanchored regexp "func.*". It now also matches the "ifunc" suffix of _dl_relocate_static_pie_ifunc, changing the result from nine breakpoints to ten. GDB, glibc, binutils and Linux are unchanged between the two builds; the GCC revisions are this commit and its immediate parent. Changing the expected count to ten would make the test depend on the target startup objects. A more robust fix would be to narrow the two unscoped regexp uses in the exact-count and throttle checks, for example to "^e?func.*", so that they only select functions defined by the test. I therefore do not think this is a GCC regression. It looks like the GDB test needs to be made more specific. <ci_notify(a)linaro.org> 于2026年8月24日周一 11:47写道： > 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-3278-gb6477e6c4ef > | Author: Longjun Luo <luolongjuna(a)gmail.com> > | Date: Thu Jul 23 00:01:50 2026 +0800 > | > | debug/126355 - preserve debug info for IPA ICF wrappers > | > | When IPA ICF keeps a distinct symbol for an address-taken function > by > | replacing its body with a wrapper, cgraph_node::create_wrapper > reuses the > | original function declaration and its early debug DIE. > | ... 28 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running gdb:gdb.python/py-rbreak.exp ... > | FAIL: gdb.python/py-rbreak.exp: check number of returned breakpoints > is 9 > > 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-2005. (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/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

1 month, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] v11.1.0-302-g288d39e26d4: 14 regressions on arm

by ci_notify＠linaro.org

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…

1 month, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-11539-gb04b71c9f4b: 5 regressions on aarch64

by ci_notify＠linaro.org

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…

1 month, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.44.9000-78-g5d7828bd5e1: 1 regression on arm

by ci_notify＠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: | commit glibc-2.44.9000-78-g5d7828bd5e1 | Author: Yury Khrustalev <yury.khrustalev(a)arm.com> | Date: Mon Jul 20 16:37:10 2026 +0100 | | 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. | ... 4 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-valgrind-smoke Used configuration : *CI config* tcwg_glibc_check master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-2001. (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=5d7828bd5e1762c5d7ec…

1 month, 2 weeks

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-24-init-4536-g6a2d309c7d20: 2 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

1 month, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-11540-ge189bfd9b49: Failure on aarch64

by ci_notify＠linaro.org

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…

1 month, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-11541-g0f9faaebc91: 7 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In binutils_check master-aarch64, after: | commit binutils-2_41-release-11541-g0f9faaebc91 | Author: Nick Clifton <nickc(a)redhat.com> | Date: Mon Aug 17 09:51:30 2026 +0100 | | add_archive_element(): Record pointer to my_archive for later use in the function Produces 7 regressions: | | regressions.sum: | Running ld:ld-bootstrap/bootstrap.exp ... | FAIL: bootstrap | FAIL: bootstrap with strip | FAIL: bootstrap with -Wl,--traditional-format | FAIL: bootstrap with -Wl,--no-keep-memory | ... and 3 more Used configuration : *CI config* tcwg_binutils_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1998. (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_binutils_check--master-aarch64-build/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_binutils_check--master-aarch64-build/bu… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… Current build : http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… Reference build : http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… 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=0f9faaebc91bc…

1 month, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-24-init-1585-g3cf44478fcf5: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

1 month, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #141473: 2 regressions on aarch64

by Longjun Luo

Thanks for the report. This appears to be a false positive and unrelated to patch 141473. All six checks of the new pr126348 regression test pass in the reported AArch64 build. The reported gcc.misc-tests/gcov-39.c test is compiled with --coverage -fpath-coverage and without -flto, so it does not exercise lto_write_tree_1, which is the only compiler implementation code changed by this patch. Moreover, the identical 1/7-versus-1/8 failure occurs in nine consecutive AArch64 precommit builds (10755-10763), covering several unrelated patches and patch series, including C++ contracts changes and RISC-V-only backend changes unrelated to AArch64 code generation. The reference result reports 51 total prime paths, while the precommit result reports 50, suggesting a reference/precommit baseline or environment discrepancy rather than an effect of this patch. Could you please disregard the regression attribution to this patch and investigate or update the baseline/flaky-test filtering as appropriate? 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/… First build in the consecutive sequence: http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui… RISC-V-only example at the other end of the sequence: http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui…

1 month, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.44.9000-69-g40ddd85420c: 1 regression on arm

by ci_notify＠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: | commit glibc-2.44.9000-69-g40ddd85420c | Author: Florian Weimer <fweimer(a)redhat.com> | Date: Sat Aug 15 12:03:35 2026 +0200 | | resolv: Test case for accepting mismatching, corrupted packets | | The test skeleton was auto-generated. I think this is fine because | the harness is so specific to glibc. | | ... 2 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:resolv ... | FAIL: resolv/tst-resolv-querymatch-short 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-1997. (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=40ddd85420c11446d5b6…

1 month, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.44.9000-35-g666c2acb7d1: 1 regression on arm

by ci_notify＠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: | commit glibc-2.44.9000-35-g666c2acb7d1 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Thu Jul 9 14:48:14 2026 -0300 | | nss: Use test resolver for tst-getaddrinfo4 | | Rewrite the BZ#15339 test to use the resolv_test framework instead of | querying the network, so it can run as a regular test. | | ... 1 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:nss ... | FAIL: nss/tst-getaddrinfo4 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-1991. (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=666c2acb7d1cdc348a6d…

2 months

1
0
0 0

Smth strange with ci for glibc

by maxgoonfuture＠gmail.com

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?

2 months

2
2
0 0

Re: [Linaro-TCWG-CI] llvmorg-24-init-166-g0e877fd1a637: 3 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-17-2855-g75be6085674: 1 regression on arm

by Thiago Jung Bauermann

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)

2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-24-init-1860-g491f16472b0f: 2 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

2 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-23-init-22857-g308393ede14c: 4 regressions 1 fix on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

2 months, 1 week

1
0
0 0

[Linaro-TCWG-CI] v11.1.0-rc0-83-gb693da615a7: 21 regressions 38360 fixes on arm

by ci_notify＠linaro.org

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…

2 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] glibc patch #140108: 3 regressions 111 fixes on arm

by Yury Khrustalev

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.

2 months, 1 week

2
2
0 0

Re: [Linaro-TCWG-CI] llvmorg-24-init-787-gd9fff42ccd58: 3 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

2 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-17-2353-gee27c516c7b6: 1 regression on aarch64

by Dylan Rees

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.

2 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-23-init-20756-gd445267fbb56: 2 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

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…

2 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] glibc patch #139350: 1 regression 111 fixes on arm

by Artem Proskurnev

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.

2 months, 3 weeks

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain