linaro-toolchain

linaro-toolchain@lists.linaro.org

14 participants
5701 discussions

Potentially dodgy caching on flang-arm64-windows-msvc

by Luke Lau

Hi there, I got a notification about a build failure on the flang-arm64-windows-msvc buildbot earlier today, I’ve included the original email below. The commit in question that caused the failure added some new intrinsics, touching some tablegen files, which then caused some tests for unrelated intrinsics to fail: https://github.com/llvm/llvm-project/commit/9ba774566e27b76b9c7c2b2ddd108c1… https://lab.llvm.org/buildbot/#/builders/207/builds/15865 But the buildbot went back to green in https://lab.llvm.org/buildbot/#/builders/207/builds/15869 when another PR changed some other tablegen files in the llvm project. I didn’t revert or commit any fixes in the meantime. Is there maybe some issue with the build cache and how tablegen files interact with it? Just thought I’d flag this to you anyway. Many thanks Luke > Begin forwarded message: > > From: llvm.buildmaster(a)lab.llvm.org > Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed test (failure) (main) > Date: 9 April 2026 at 16:03:07 GMT+8 > To: "Luke Lau" <luke(a)igalia.com>, "Nikita Popov" <npopov(a)redhat.com> > Cc: llvm.buildmaster(a)lab.llvm.org > Reply-To: llvm.buildmaster(a)lab.llvm.org > > The Buildbot has detected a new failure on builder flang-arm64-windows-msvc while building llvm. > > Full details are available at: > https://lab.llvm.org/buildbot/#/builders/207/builds/15865 > > Worker for this Build: linaro-armv8-windows-msvc-01 > Blamelist: > Luke Lau <luke(a)igalia.com>, > Nikita Popov <npopov(a)redhat.com> > > BUILD FAILED: failed test (failure) > > Step 6 (test-build-unified-tree-check-mlir) failure: test (failure) > ******************** TEST 'MLIR :: mlir-runner/test-expand-math-approx.mlir' FAILED ******************** > Exit Code: 2 > > Command Output (stdout): > -- > # RUN: at line 1 > c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir -pass-pipeline="builtin.module(func.func(math-expand-ops),convert-vector-to-scf,convert-scf-to-cf,convert-vector-to-llvm,convert-to-llvm,reconcile-unrealized-casts)" | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe -e main -entry-point-result=void -O0 -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_c_runner_utils.dll -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_runner_utils.dll -shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_float16_utils.dll | c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-ms > vc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir > # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-opt.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir' '-pass-pipeline=builtin.module(func.func(math-expand-ops),convert-vector-to-scf,convert-scf-to-cf,convert-vector-to-llvm,convert-to-llvm,reconcile-unrealized-casts)' > # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe' -e main -entry-point-result=void -O0 '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_c_runner_utils.dll' '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_runner_utils.dll' '-shared-libs=C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir_float16_utils.dll' > # .---command stderr------------ > # | LLVM ERROR: Cannot select: intrinsic %llvm.aarch64.neon.ushl > # | PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace and instructions to reproduce the bug. > # | Stack dump: > # | 0. Program arguments: c:\\users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir-runner.exe -e main -entry-point-result=void -O0 -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_c_runner_utils.dll -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_runner_utils.dll -shared-libs=C:\\Users\\tcwg\\llvm-worker\\flang-arm64-windows-msvc\\build\\bin\\mlir_float16_utils.dll > # | 1. Running pass 'Function Pass Manager' on module 'LLVMDialectModule'. > # | 2. Running pass 'AArch64 Instruction Selection' on function '@"func_roundeven32$vector"' > # | Exception Code: 0xC000001D > # | #0 0x00007ff674c89e4c mlir::detail::FallbackTypeIDResolver::registerImplicitTypeID(class llvm::StringRef) (c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\mlir-runner.exe+0x309e4c) > # | #1 0x00007ffec74aae50 (C:\WINDOWS\System32\ucrtbase.dll+0x7ae50) > # | #2 0xa25cfffec74aba5c > # `----------------------------- > # error: command failed with exit status: 0xc000001d > # executed command: 'c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe' 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir' > # .---command stderr------------ > # | FileCheck error: '<stdin>' is empty. > # | FileCheck command line: c:\users\tcwg\llvm-worker\flang-arm64-windows-msvc\build\bin\filecheck.exe C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\mlir\test\mlir-runner\test-expand-math-approx.mlir > # `----------------------------- > # error: command failed with exit status: 2 > > -- > > ******************** > > > Sincerely, > LLVM Buildbot >

1 week, 1 day

Re: [Linaro-TCWG-CI] gcc-16-8510-g395e5cef29d9: 1 regression on aarch64

by Tomasz Kaminski

This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124828. On Fri, Apr 10, 2026 at 1:15 AM <ci_notify(a)linaro.org> wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In aarch64 native, after: > | commit gcc-16-8510-g395e5cef29d9 > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Wed Apr 1 14:32:21 2026 +0200 > | > | libstdc++: Export explicit instantiations for C++20 members of > std::string > | > | The C++20 standard added new starts_with and ends_with members to > | std::basic_string, which were not previously instantiated in the > library. > | This meant that the extern template declarations had to be > disabled for > | ... 31 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running g++:g++.dg/lto/lto.exp ... > | FAIL: g++.dg/lto/20091022-2 > cp_lto_20091022-2_0.o-cp_lto_20091022-2_0.o link, -O3 -flto -Winline > > Used configuration : > *CI config* tcwg_gcc_check aarch64-linux-gnu > *configure and test flags:* none, autodetected on > aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 > --enable-fix-cortex-a53-843419 --with-arch=armv8-a > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1869. Please let us know if you > have a fix. > > If you have any questions regarding this report, please ask on > linaro-toolchain(a)lists.linaro.org mailing list. > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways > to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > The full lists of regressions and improvements as well as configure and > make commands are in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > The list of [ignored] baseline and flaky failures are in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Instruction to reproduce the build : > https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git >

1 week, 4 days

Re: [Linaro-TCWG-CI] gcc-16-8385-gc9525a790291: 3 regressions on aarch64

by Jonathan Wakely

On Thu, 2 Apr 2026 at 06:27, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In aarch64 native, after: > | commit gcc-16-8385-gc9525a790291 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Mon Mar 30 12:13:39 2026 +0100 > | > | libstdc++: Rename saturation arithmetic for C++26 (P4052R0) > | > | Last week in Croydon we approved P4052R0 to rename std::add_sat etc. for > | C++26 > | > | ... 16 lines of the commit log omitted. > > Produces 3 regressions: > | > | regressions.sum: > | Running g++:g++.dg/modules/modules.exp ... > | FAIL: g++.dg/modules/compile-std1.C -std=c++26 (test for excess errors) > | FAIL: g++.dg/modules/compile-std1.C module-cmi std (gcm.cache/std.gcm) > | FAIL: g++.dg/modules/compile-std1.C module-cmi std.compat (gcm.cache/std.compat.gcm) > > Used configuration : > *CI config* tcwg_gcc_check aarch64-linux-gnu > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu--disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1867. Please let us know if you have a fix. It's fixed now > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > The full lists of regressions and improvements as well as configure and make commands are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

2 weeks, 5 days

RE: [Linaro-TCWG-CI] llvmorg-23-init-9791-g12319b373a5f: 1 regression on aarch64

by Shunsuke Watanabe (Fujitsu)

Hi, These errors are caused by incorrect test programs. Please ignore the mail. We'll update the tests. I apologize for the false detection. Best regards, Shunsuke Watanabe Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Wednesday, April 1, 2026 2:37 AM To: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com Cc: aidengrossman(a)google.com; maxim.kuvyrkov(a)linaro.org Subject: [Linaro-TCWG-CI] llvmorg-23-init-9791-g12319b373a5f: 1 regression on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after: | commit llvmorg-23-init-9791-g12319b373a5f | Author: Aiden Grossman <aidengrossman(a)google.com> | Date: Mon Mar 30 16:34:37 2026 -0700 | | [Clang] More aggressively mark this* dead_on_return in destructors (#183347) | | Now also mark the this pointer dead_on_return for classes with a | non-zero number of base classes. We saw a limited number of failures | internally due to this change, so it doesn't seem like there are too | ... 1 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/C++/0032 ... | FAIL: test-suite :: Fujitsu/C++/0032/Fujitsu-C++-0032_1052.test | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2208. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vls-… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/12319b373a5f4b36c09165ed7f8e967…

2 weeks, 6 days

Re: [Linaro-TCWG-CI] gcc-16-7434-g6b550d69fe7c: 2 regressions on master-thumb_m55_hard_eabi

by Tomasz Kaminski

I think this is the same issue as reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124124, that was addressed by: commit r16-7911-g3a41229f92022bfb388911854d597721fce76714 <https://gcc.gnu.org/cgit/gcc/commit/?id=3a41229f92022bfb388911854d597721fce…> Author: Tomasz KamiÅski <tkaminsk(a)redhat.com> Date: Thu Mar 5 08:57:24 2026 +0100 libstdc++: Fix atomic/cons/zero_padding.cc test for arm-none-eabi [PR124124 <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124124>] The test uses dg-require-atomic-cmpxchg-word that checks if atomic compare exchange is available for pointer sized integers, and then test types that are eight bytes in size. This causes issue for targets for which pointers are four byte and libatomic is not present, like arm-none-eabi. This patch addresses by using short member in TailPadding and MidPadding, instead of int. This reduces the size of types to four bytes, while keeping padding bytes present. PR libstdc++/124124 <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124124> libstdc++-v3/ChangeLog: * testsuite/29_atomics/atomic/cons/zero_padding.cc: Limit size of test types to four bytes. On Sun, Mar 22, 2026 at 9:01 PM <ci_notify(a)linaro.org> wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In arm-eabi cortex-m55 hard, after: > | commit gcc-16-7434-g6b550d69fe7c > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Thu Jan 29 18:14:47 2026 +0100 > | > | libstdc++: Allow constant initialization of std::atomic of types > with padding [PR123875] > | > | Currently for the types T that contains padding bits, > std::atomic<T>(T) > | constructor was not usable at compile-time in C++14 or later > modes. This > | regression caused by use of __builtin_clear_padding introduced in > | ... 49 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 29_atomics/atomic/cons/static_zero_padding.cc -std=gnu++20 (test > for excess errors) > | UNRESOLVED: 29_atomics/atomic/cons/static_zero_padding.cc -std=gnu++20 > compilation failed to produce executable > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb > -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard > -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib > --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard > --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto > qemu-cpu=cortex-m55 > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1865. Please let us know if you > have a fix. > > If you have any questions regarding this report, please ask on > linaro-toolchain(a)lists.linaro.org mailing list. > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways > to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > Current build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > Reference build : > https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > 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 weeks, 1 day

[Fortran, PR124484, v1] Fix testing caf_shmem on aarch64-*-linux was: [Linaro-TCWG-CI] gcc-16-7727-gaa09298cb017: 157 regressions on aarch64

by Andre Vehreschild

Hi all, the linaro CI reported test errors for aarch64 targets. I figured that for aarch64 on linux the compile flags -pthread and -lrt are needed to link caf_shmem and produce an executable. The attached patch addresses this by special case for aarch64-*-linux* similiar to freebsd. Regtested ok on aarch64-unknown-linux-gnu (cfarm185) and x86_64-linux-gnu / F43. Ok for master? Regards, Andre On Thu, 12 Mar 2026 04:46:24 +0000 (UTC) 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 master-aarch64, after: > | commit gcc-16-7727-gaa09298cb017 > | Author: Andre Vehreschild <vehre(a)gcc.gnu.org> > | Date: Wed Jun 18 09:26:22 2025 +0200 > | > | Fortran: Enable coarray tests for multi image use [PR88076] > | > | Change some of regression tests to run on single and multiple images. > | Add some new tests. > | > | ... 29 lines of the commit log omitted. > > Produces 157 regressions: > | > | regressions.sum: > | Running gfortran:gfortran.dg/coarray/caf.exp ... > | FAIL: gfortran.dg/coarray/alloc_comp_1.f90 -fcoarray=lib -O2 > -lcaf_shmem (test for excess errors) | UNRESOLVED: > gfortran.dg/coarray/alloc_comp_1.f90 -fcoarray=lib -O2 -lcaf_shmem > compilation failed to produce executable | FAIL: > gfortran.dg/coarray/alloc_comp_10.f90 -fcoarray=lib -O2 -lcaf_shmem (test > for excess errors) | UNRESOLVED: gfortran.dg/coarray/alloc_comp_10.f90 > -fcoarray=lib -O2 -lcaf_shmem compilation failed to produce executable | > ... and 153 more > > Used configuration : > *CI config* tcwg_gnu_cross_check_gcc master-aarch64 > *configure and test flags:* --target aarch64-linux-gnu > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1860. > Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on > linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to > reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > The full lists of regressions and improvements as well as configure and make > commands are in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > > Current build : > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > Reference build : > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > > 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 -- Andre Vehreschild * Email: vehre ad gmx dot de

1 month

Re: [Linaro-TCWG-CI] gcc-16-7569-gc94fdc1590d: 2 regressions on arm

by Christophe Lyon

Hi, On 3/11/26 04:19, ci_notify--- via Gcc-regression wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In master-arm, after: > | commit gcc-16-7569-gc94fdc1590d > | Author: Torbjörn SVENSSON <torbjorn.svensson(a)foss.st.com> > | Date: Tue Feb 17 16:08:58 2026 +0100 > | > | testsuite: arm: Use effective-target for aes-fuse-[12].c > | > | gcc/testsuite/ChangeLog: > | > | * gcc.target/arm/aes-fuse-1.c: Use effective-target > | ... 6 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | ERROR: gcc.target/arm/aes-fuse-1.c: unknown effective target keyword `arm_cpu_cortex_a53' for " dg-require-effective-target 3 arm_cpu_cortex_a53 " > | ERROR: gcc.target/arm/aes-fuse-2.c: unknown effective target keyword `arm_cpu_cortex_a53' for " dg-require-effective-target 3 arm_cpu_cortex_a53 " > I believe this was fixed by https://gcc.gnu.org/pipermail/gcc-patches/2026-March/709997.html https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=41aba0b725e942f65d59b719c… Thanks, Christophe > Used configuration : > *CI config* tcwg_gnu_cross_check_gcc master-arm > *configure and test flags:* --target arm-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1859. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2652/a… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2652/a… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2652/a… > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2652/a… > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2649/a… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

1 month, 1 week

Re: [Linaro-TCWG-CI] gcc-16-7439-g1ced019ad9d: 4 regressions on aarch64

by Christophe Lyon

Hi, On Sun, Mar 8, 2026 at 2:21 PM ci_notify--- via Gcc-regression < gcc-regression(a)gcc.gnu.org> wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In master-aarch64, after: > | commit gcc-16-7439-g1ced019ad9d > | Author: Alice Carlotti <alice.carlotti(a)arm.com> > | Date: Wed Jan 14 13:48:35 2026 +0000 > | > | aarch64: Disable shrink-wrap for locally-streaming functions [PR > 123624] > | > | The meaning of poly_int values changes depending on whether we are > in > | streaming or non-streaming mode, but this dependency is not > explicitly > | tracked. Locally-streaming functions can change streaming state > in the > | ... 17 lines of the commit log omitted. > > Produces 4 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/aarch64/sme/aarch64-sme.exp ... > | UNRESOLVED: gcc.target/aarch64/sme/sme-shrinkwrap.c > check-function-bodies bar > | UNRESOLVED: gcc.target/aarch64/sme/sme-shrinkwrap.c > check-function-bodies baz > | UNRESOLVED: gcc.target/aarch64/sme/sme-shrinkwrap.c > check-function-bodies foo > | FAIL: gcc.target/aarch64/sme/sme-shrinkwrap.c execution test > > Used configuration : > *CI config* tcwg_gnu_cross_check_gcc master-aarch64 > *configure and test flags:* --target aarch64-linux-gnu > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1856. Please let us know if you > have a fix. > This is hopefully fixed by https://gcc.gnu.org/pipermail/gcc-patches/2026-March/710145.html https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=24d41d10f28bfae6461003994… Thanks, Christophe > > If you have any questions regarding this report, please ask on > linaro-toolchain(a)lists.linaro.org mailing list. > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways > to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > > Current build : > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > Reference build : > https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/26… > > 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, 1 week

Re: [Linaro-TCWG-CI] gcc-16-7919-g1b404c574450: 1 regression on arm

by Nathan Myers

Fixed in 2bfaa218b066.

1 month, 2 weeks

Re: [Linaro-TCWG-CI] gcc-16-7262-gf7f2b73b9c1e: 2 regressions 2 fixes on master-thumb_m55_hard_eabi

by Christophe Lyon

Hi, On 3/5/26 15:16, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In arm-eabi cortex-m55 hard, after: > | commit gcc-16-7262-gf7f2b73b9c1e > | Author: Christophe Lyon <christophe.lyon(a)arm.com> > | Date: Tue Feb 3 13:07:10 2026 +0000 > | > | testsuite: arm: Make arm_neon_ok_nocache consistent with other effective-targets > | > | A recent patch updated arm_neon_ok_nocache with an improved list of > | flags to try, but was not consistent with > | arm_v8_3a_complex_neon_ok,_nocache arm_v8_2a_fp16_neon_ok_nocache, > | ... 14 lines of the commit log omitted. > > Produces 2 regressions 2 fixes: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: experimental/simd/pr109261_constexpr_simd.cc -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors) > | FAIL: experimental/simd/pr115454_find_last_set.cc -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors) > | > | fixes.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: experimental/simd/pr109261_constexpr_simd.cc -mfloat-abi=softfp -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors) > | FAIL: experimental/simd/pr115454_find_last_set.cc -mfloat-abi=softfp -mcpu=unset -march=armv7-a+simd -mfpu=auto -ffast-math -O2 -Wno-psabi (test for excess errors) > This does not look like a "real" regression: the same tests are still failing, using different options. Thanks, Christophe > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m55 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1853. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_e… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

1 month, 2 weeks

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain