linaro-toolchain

linaro-toolchain@lists.linaro.org

6 participants
5799 discussions

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)

1 month, 2 weeks

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…

1 month, 2 weeks

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…

1 month, 2 weeks

[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…

1 month, 2 weeks

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.

1 month, 2 weeks

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…

1 month, 3 weeks

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.

1 month, 3 weeks

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…

1 month, 4 weeks

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

[committed] Fix signed char test assumption [Was Re: [Linaro-TCWG-CI] gcc-17-2261-g649b2a6d9f9f: 7 regressions on arm]

by Jeffrey Law

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

2 months

← Newer
1
2
3
4
5
6
7
...
580
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain