linaro-toolchain June 2026

linaro-toolchain@lists.linaro.org

12 participants
15 discussions

[Linaro-TCWG-CI] glibc-2.43.9000-439-g53d909a283: 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.43.9000-439-g53d909a283 | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Mon Apr 13 08:23:05 2026 +0800 | | elf: Support THP segment load with madvise enabled THP | | The current THP segment load approach works only when THP is enabled | with always in the kernel. If THP is enabled with madvise in the | kernel, to enable THP segment load in an application, madvise should | ... 43 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-thp-1-no-s-code-static | FAIL: 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-1937. (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=53d909a283085c82bdcc…

8 hours, 30 minutes

[Linaro-TCWG-CI] glibc-2.43.9000-403-g9ed3576e61f: 118 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 native, after: | commit glibc-2.43.9000-403-g9ed3576e61f | Author: Yury Khrustalev <yury.khrustalev(a)arm.com> | Date: Tue May 26 11:19:53 2026 +0100 | | malloc: aarch64: Add ifuncs for malloc functions | | Introduce ifuncs and resolvers for functions pertinent to the | malloc interface on the AArch64 target: malloc, calloc, free, | realloc, memalign, valloc, pvalloc, posix_memalign, aligned_alloc, | ... 13 lines of the commit log omitted. Produces 118 regressions: | | regressions.sum: | Running gdb:gdb.base/call-strs.exp ... | FAIL: gdb.base/call-strs.exp: call str_func("a","b","c","d","e","f","g") | FAIL: gdb.base/call-strs.exp: print str_func("a","b","c","d","e","f","g") | Running gdb:gdb.base/callfuncs.exp ... | FAIL: gdb.base/callfuncs.exp: noproto: p t_char_array_values("carray 1","carray 2") | ... and 125 more Used configuration : *CI config* tcwg_gnu_native_check_gdb aarch64-linux-gnu *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a We track this bug report under https://linaro.atlassian.net/browse/GNU-1934. (Require Linaro login) Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu… Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu… Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_native_check_gdb--master-aarch64-bu… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=9ed3576e61f7a87eb83d…

2 days, 11 hours

[Linaro-TCWG-CI] glibc-2.43.9000-410-g3785d4c0d0f: 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.43.9000-410-g3785d4c0d0f | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Fri Jun 12 13:10:09 2026 -0300 | | elf: Propagate the pointer guard to ld.so loaded via static dlopen (BZ 34196) | | The static-dlopen does not initialize the pointer guard for ABIs that | define THREAD_SET_POINTER_GUARD. Besides not properly guard the | pointer if a libc.so symbol is called, this can lead to setjmp | ... 10 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:elf ... | FAIL: elf/tst-ptrguard-static-dlopen 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-1930. (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=3785d4c0d0f2d1b08c4f…

3 days, 12 hours

(no subject)

by Bouhaouel, Mohamed

Hi, I am reaching out regarding regression emails I received from your CI about the patch series I submitted recently. V1 (submitted on 18.05.2026): https://patchwork.sourceware.org/project/gdb/cover/20260518183316.127043-1-… V2 (submitted on 11.06.2026): https://patchwork.sourceware.org/project/gdb/cover/20260611153232.3011-1-mo… The regressions were reported for the V2 series, in which no functional changes were introduced (only commit message updates). I am wondering if your CI has been passing for V1 or was not triggered? I would appreciate your help in determining whether the reported regressions are legitimate or false positives. If they are indeed regressions introduced by my changes, I would greatly appreciate guidance on the reproduction steps. Thanks, --Mohamed Intel Deutschland GmbH Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany Tel: +49 89 991 430, www.intel.de Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell Chairperson of the Supervisory Board: Nicole Lau Registered Seat: Munich Commercial Register: Amtsgericht Muenchen HRB 186928

4 days, 1 hour

Re: [Linaro-TCWG-CI] gcc-17-1571-ga05a055bb2fb: 2 regressions on aarch64

by Andrew Pinski

On Tue, Jun 16, 2026 at 3:30 PM <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In aarch64 native, after: > | commit gcc-17-1571-ga05a055bb2fb > | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com> > | Date: Fri Jun 12 11:40:35 2026 -0700 > | > | phiopt: reorganize factoring/cselim-limited for phiopt > | > | This is in preparation for adding factoring out loads > | for phiopt were we want to loop over all 3 factoring > | cases if one of them made a change so that a load elimination > | ... 15 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/aarch64/aarch64.exp ... > | FAIL: gcc.target/aarch64/fuse_cmp_csel-1.c check-function-bodies f1 > | FAIL: gcc.target/aarch64/fuse_cmp_csel-1.c check-function-bodies f2 The check here is too restrictive. It is checking for gt but we now produce le. Both are valid. cmp w0, w1 csel w3, w4, w3, le add w0, w2, w3 I will make both fuse_cmp_csel.c and fuse_cmp_csel-1.c less restive when it comes to the le/gt issue. Thanks, Andrea > > Used configuration : > *CI config* tcwg_gcc_check aarch64-linux-gnu > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1928. (Require Linaro login) Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > The full lists of regressions and improvements as well as configure and make commands are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

4 days, 18 hours

Re: [Linaro-TCWG-CI] llvmorg-23-init-17574-g1872f06d60f3: 18 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, There are two issues with this issue. Regarding the first one, the testset was crashing during compilation, but the commit (ef4fb183a8d5c0d1910f7b5b6776ba669d6795ef) resolved the crash during compilation. Regarding the second issue, the testset (0737_0019.f90) is incorrect. It passes a function that returns a pointer array to an argument expecting a function that returns an allocatable array, and passes a function that returns an allocatable array to an argument expecting a function that returns a pointer array. Since this is an incorrect testset, we'll correct it. I apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信: 2026 年 6 月 4 日 (木曜日) 6:25 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; 47756807+khaki3(a)users.noreply.github.com <47756807+khaki3(a)users.noreply.github.com> 件名: [Linaro-TCWG-CI] llvmorg-23-init-17574-g1872f06d60f3: 18 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: | commit llvmorg-23-init-17574-g1872f06d60f3 | Author: khaki3 <47756807+khaki3(a)users.noreply.github.com> | Date: Tue Jun 2 04:55:05 2026 -0700 | | [flang][HLFIR] Add SeparateAllocatableAssign pass (#197814) | | Example: | ```fortran | !$\acc kernels | ... 17 lines of the commit log omitted. Produces 18 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0134 ... | NOEXE: test-suite :: Fujitsu/Fortran/0134/Fujitsu-Fortran-0134_0211.test | Running test-suite:Fujitsu/Fortran/0299 ... | NOEXE: test-suite :: Fujitsu/Fortran/0299/Fujitsu-Fortran-0299_0038.test | Running test-suite:Fujitsu/Fortran/0390 ... | ... and 21 more | # "NOEXE" means : the test program cannot be compiled | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2230. (Require Linaro login) Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/1872f06d60f35133bbc06e047c763b4…

5 days, 9 hours

Re: [Linaro-TCWG-CI] llvmorg-23-init-17879-gf02dd4afbac1: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, This test is incorrect. There is an error in how the volatile attribute of the variable k is handled when using setjmp and longjmp. Therefore, we'll correct testset. I apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信日時: 2026年6月6日 14:23 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> CC: npopov(a)redhat.com <npopov(a)redhat.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> 件名: [Linaro-TCWG-CI] llvmorg-23-init-17879-gf02dd4afbac1: 1 regression on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-23-init-17879-gf02dd4afbac1 | Author: Nikita Popov <npopov(a)redhat.com> | Date: Thu Jun 4 09:26:12 2026 +0200 | | [CaptureTracking] Volatile operations only capture address (#201316) | | The fact that a volatile access was performed on a certain address is an | observable effect in the abstract machine, so volatile operations | capture the address of the accessed pointer. However, they do not | ... 6 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/C/0094 ... | FAIL: test-suite :: Fujitsu/C/0094/Fujitsu-C-0094_0065.test | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2232. (Require Linaro login) Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O3-neoverse_v1… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/f02dd4afbac15705016a9a7962d8716…

5 days, 13 hours

[Linaro-TCWG-CI] v11.0.0-1483-gc8bea1276c8: 38358 regressions 21 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.0.0-1483-gc8bea1276c8 | Author: Philippe Mathieu-Daudé <philmd(a)linaro.org> | Date: Fri May 15 12:40:14 2026 +0200 | | target/arm: Build cpu32-system.o as common object | | cpu32.c only contains CPU types used in 32-bit system emulation: | rename it as cpu32-system.c; always compile the file but only | register the QOM types for the 32-bit binary. | ... 6 lines of the commit log omitted. Produces 38358 regressions 21 fixes: | | regressions.sum: | Running g++:g++.dg/compat/compat.exp ... | FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o execute | FAIL: g++.dg/compat/abi/bitfield2 cp_compat_x_tst.o-cp_compat_y_tst.o execute | FAIL: g++.dg/compat/abi/pr83487-1 cp_compat_x_tst.o-cp_compat_y_tst.o execute | FAIL: g++.dg/compat/abi/pr83487-2 cp_compat_x_tst.o-cp_compat_y_tst.o execute | ... and 38390 more | | fixes.sum: | Running g++:g++.dg/vect/vect.exp ... | UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++20 compilation failed to produce executable | UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++26 compilation failed to produce executable | UNRESOLVED: g++.dg/vect/pr95401.cc -std=c++98 compilation failed to produce executable | FAIL: g++.dg/vect/pr95401.cc -std=c++26 (test for excess errors) | ... and 19 more Used configuration : *CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9 We track this bug report under https://linaro.atlassian.net/browse/GNU-1925. (Require Linaro login) Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof… Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof… Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-arm_v7a_sof… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/qemu/… Full commit : https://gitlab.com/qemu-project/qemu/commit/c8bea1276c85855b2e088b740737d04…

1 week, 2 days

Re: [Linaro-TCWG-CI] 3 patches in gdb: 171 regressions on arm

by Guinevere Larsen

Hi! This seems to be an issue with your testing infrastructure. These patches have not touched anything that isn't related to record-full so there's no way they could be causing failures in gdb.arch tests. I guess this test is no longer reliable. -- Cheers, Guinevere Larsen It/she On 6/7/26 3:44 AM, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gdb_check master-arm, after: > | 3 patches in gdb > | Patchwork URL: https://patchwork.sourceware.org/patch/136305 > | 1f3856ef4e9 [PATCH v4 3/8] gdb/record: remove record_full_insn_num > | 9165d18a941 [PATCH v4 2/8] gdb/record: factor out reading and writing the execution log to corefile > | 85ad6ec91da [PATCH v4 1/8] gdb/record: Refactor record history > | ... applied on top of baseline commit: > | 4562eab73d3 Automatic date update in version.in > > Produces 171 regressions: > | > | regressions.sum: > | Running gdb:gdb.arch/skip-prologue.exp ... > | FAIL: gdb.arch/skip-prologue.exp: f2: $\bp_addr == $\prologue_end_addr (skipped too much) > | FAIL: gdb.arch/skip-prologue.exp: f4: $\bp_addr == $\prologue_end_addr (skipped too much) > | Running gdb:gdb.arch/thumb2-it.exp ... > | FAIL: gdb.arch/thumb2-it.exp: it_3, stepi 3 > | ... and 187 more > > Used configuration : > *CI config* tcwg_gdb_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/… > The full lists of regressions and improvements as well as configure and make commands are in > * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-precommit/builds/… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gdb_check--master-arm-build/builds/1021… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 week, 5 days

Re: [Linaro-TCWG-CI] llvmorg-23-init-16289-g9c26d8c30c19: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, This test is incorrect. I apologize for the false detection. The criteria used in the test are inappropriate. Therefore, we will correct the test. It may take some time due to our internal release process, sorry. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信: 2026 年 5 月 30 日 (土曜日) 13:36 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; a.bataev(a)outlook.com <a.bataev(a)outlook.com> 件名: [Linaro-TCWG-CI] llvmorg-23-init-16289-g9c26d8c30c19: 1 regression on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: | commit llvmorg-23-init-16289-g9c26d8c30c19 | Author: Alexey Bataev <a.bataev(a)outlook.com> | Date: Thu May 21 10:30:09 2026 -0400 | | [SLP] Unify IR flag and metadata propagation in vectorizeTree | | Replace scattered propagateIRFlags/propagateMetadata calls with a single | PropagateIRFlags lambda. Excludes copyable scalars from the flag | intersection set and drops nnan/ninf when a copyable lane cannot prove | ... 5 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0118 ... | FAIL: test-suite :: Fujitsu/Fortran/0118/Fujitsu-Fortran-0118_0266.test | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2228. (Require Linaro login) Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/9c26d8c30c1971881d710cf62d0f50b…

1 week, 5 days

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain June 2026