linaro-toolchain September 2026

linaro-toolchain@lists.linaro.org

6 participants
14 discussions

[Linaro-TCWG-CI] glibc-2.44.9000-140-ged0c137b97e: 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-140-ged0c137b97e | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Mon Aug 17 15:15:32 2026 -0300 | | elf: Open the normalized $\ORIGIN rpath in AT_SECURE programs (BZ 34360) | | For AT_SECURE programs the loader honors $\ORIGIN in DT_RPATH only when the | expansion is rooted in a trusted directory, but it validated the lexically | normalized path while opening the raw expansion. As "a/b/../c" only names | ... 13 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-origin-secure 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-2016. (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=ed0c137b97eb940b4b64…

3 weeks, 2 days

[Linaro-TCWG-CI] glibc-2.44.9000-126-gd179e02998c: 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 native, after: | commit glibc-2.44.9000-126-gd179e02998c | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Tue Jul 28 18:13:22 2026 -0300 | | elf: Allow RPATH/RUNPATH for static-pie (BZ 33326) | | The initial static-pie support (commit 9d7a3741c9e59eba87fb) reused | ld.so ELF parsing logic, even though RPATH/RUNPATH should not appear | in the static-pie bootstrap. With static PIE, RPATH/RUNPATH on the | ... 15 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-pie-rpath-static Used configuration : *CI config* tcwg_gnu_native_check_glibc 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-2015. (Require Linaro login) Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_glibc--master-aarch64-… 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=d179e02998ce31c93436…

3 weeks, 2 days

Re: [Linaro-TCWG-CI] llvmorg-24-init-6091-g44ea65c07a60: 3 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, The failures were caused by re-applying the LLVM change introduced by commit(efd053f8ef306e6fa21ab0cd1bd185ef48f09fc0). Although the change had previously been reverted due to regression failures, it was later re-applied unchanged by commit(44ea65c07a600ca1c32912b5cd7356f6792b2b03). This reintroduced the same failures that had already been reported in LLVM-2266. The issue has already been addressed as part of the resolution for LLVM-2266, and the corresponding fix was committed in: https://dev.azure.com/miratech-soft/b6c3f009-db3a-422a-91be-d5c0809bb862/_g… Please ignore the mail. 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月28日 1:43 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> CC: rupprecht(a)google.com <rupprecht(a)google.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> 件名: [Linaro-TCWG-CI] llvmorg-24-init-6091-g44ea65c07a60: 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-6091-g44ea65c07a60 | Author: Jordan Rupprecht <rupprecht(a)google.com> | Date: Wed Aug 26 13:02:20 2026 -0500 | | Re-apply "[PromoteMemToReg] Insert store undef when removing lifetime markers" (#218935) | | Reapplies #191909 / reverts #218804 | | Re-apply as-is. The issues were downstream and have been since fixed. 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-2267. (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/44ea65c07a600ca1c32912b5cd7356f…

3 weeks, 2 days

Re: [Linaro-TCWG-CI] llvmorg-24-init-6257-gc47197af5327: 3 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, These tests are incorrect. Therefore, we will correct the tests. Details are as follows. Investigation shows that all failures are caused by assumptions in the test programs rather than compiler defects. Two independent issues were identified. Issue 1: Fujitsu-C-0060_0008.test and Fujitsu-C-0076_0009.test These tests use NaN/Infinity related computations while being compiled with -ffast-math. The source files explicitly enable: - -fhonor-nans but do not enable: - -fhonor-infinities As a result, optimizations assuming that infinities are not significant remain legal under -ffast-math. Fujitsu-C-0060_0008.test generates Inf and -Inf through division by zero and compares them against expected values. The test assumes IEEE infinity semantics are preserved, but the compilation options do not require that behavior. Fujitsu-C-0076_0009.test exhibits the same problem. Issue 2: Fujitsu-Fortran-0311_0026.test This test uses Cray pointers and an allocatable array that shares the same storage. However, the allocatable arrays participating in the aliasing relationship do not have the TARGET attribute. Under Flang's documented aliasing rules for Cray pointers, optimizations may assume that Cray-pointer targets do not alias ordinary variables unless the aliased variables are declared with the TARGET attribute. Consequently, the optimizer may legally treat the two objects as non-aliasing despite referring to the same storage at runtime. The failure therefore originates from the test program not expressing the required aliasing relationship. Please ignore the mail. We'll update the test. We apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信: 2026 年 8 月 29 日 (土曜日) 16:20 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: jfargnoli(a)nvidia.com <jfargnoli(a)nvidia.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> 件名: [Linaro-TCWG-CI] llvmorg-24-init-6257-gc47197af5327: 3 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: | commit llvmorg-24-init-6257-gc47197af5327 | Author: Justin Fargnoli <jfargnoli(a)nvidia.com> | Date: Thu Aug 27 13:03:39 2026 -0700 | | [LTO] Enable `PrepareForLTO` for loop unrolling in pre-link pipelines (#192155) | | Currently, the unroller will not unroll loops with inlineable calls. | However, calls that may not appear to be inlineable during the pre-link | phase may become inlineable during the post-link phase. The unroller's | ... 4 lines of the commit log omitted. Produces 3 regressions: | | regressions.sum: | Running test-suite:Fujitsu/C/0060 ... | FAIL: test-suite :: Fujitsu/C/0060/Fujitsu-C-0060_0008.test | Running test-suite:Fujitsu/C/0076 ... | FAIL: test-suite :: Fujitsu/C/0076/Fujitsu-C-0076_0009.test | Running test-suite:Fujitsu/Fortran/0311 ... | ... and 1 more | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2268. (Require Linaro login) Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/c47197af53270a4795040756c27802f…

3 weeks, 3 days

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain September 2026