linaro-toolchain

linaro-toolchain@lists.linaro.org

15 participants
5760 discussions

Re: [Linaro-TCWG-CI] gcc-17-1905-g70e630b6d29b: 5 regressions 5 fixes on master-thumb_m33_hard_eabi

by Jonathan Wakely

On Thu, 2 Jul 2026 at 23:45, <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-m33 hard, after: > | commit gcc-17-1905-g70e630b6d29b > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Jun 25 12:59:04 2026 +0100 > | > | libstdc++: Update feature test macros and tests for C++29 > | > | With r17-1595-g0c5c6249a2e9a7 G++ supports -std=c++29 so update our > | feature test macro generation and testsuite to know about it. > | > | ... 19 lines of the commit log omitted. > > Produces 5 regressions 5 fixes: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++29 execution test > | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++29 execution test > | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++29 execution test > | FAIL: 27_io/print/2.cc -std=gnu++29 (test for excess errors) > | ... and 1 more > | > | fixes.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 execution test > | FAIL: 19_diagnostics/stacktrace/output.cc -std=gnu++26 execution test > | FAIL: 19_diagnostics/stacktrace/stacktrace.cc -std=gnu++26 execution test > | FAIL: 27_io/print/2.cc -std=gnu++26 (test for excess errors) > | ... and 1 more > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m33 --with-float=hard --target_board=-mthumb/-march=armv8-m.main+dsp+fp/-mtune=cortex-m33/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m33 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1942. (Require Linaro login) Please let us know if you have a fix. This isn't really a regression, it's because the tests switched from being run with -std=gnu++26 to -std=gnu++29, but they still FAIL the same way. > > 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-thumb_m33_h… > 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-thumb_m33_h… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m33_h… > > 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

3 weeks, 4 days

Re: [Linaro-TCWG-CI] gcc-17-2047-gb12fdd95251: Failure on master-thumb_m33_hard_eabi

by Jonathan Wakely

On Wed, 1 Jul 2026 at 18:38, <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-m33 hard, after: > | commit gcc-17-2047-gb12fdd95251 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Mon Jun 22 14:41:02 2026 +0100 > | > | libstdc++: Remove dependency on std::atomic<unsigned> in tzdb.cc > | > | My r17-471-ge79f0f818c0e42 change to optimize handling of leap seconds > | introduced a hard dependency on std::atomic<unsigned>, which causes > | problems for targets without atomic word operations, like Cortex-M0.: > | ... 23 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe binutils: > | 1 > | # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m33 --set gcc_override_configure=--with-float=hard: > | 2 > | # build_abe newlib: > | 4 > | # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m33 --set gcc_override_configure=--with-float=hard: > | # FAILED > | # build_abe gdb: > | # build_abe qemu: > | # First few build errors in logs: > | # 00:05:41 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++20/tzdb.cc:1612:22: error: ‘struct std::chrono::tzdb_list::_Node::NumLeapSeconds’ has no member named ‘set_locked’ > | # 00:05:43 make[5]: *** [Makefile:575: tzdb.lo] Error 1 > | # 00:05:43 make[4]: *** [Makefile:802: all-recursive] Error 1 > | # 00:05:43 make[3]: *** [Makefile:580: all-recursive] Error 1 > | # 00:05:43 make[2]: *** [Makefile:505: all] Error 2 > | # 00:05:43 make[1]: *** [Makefile:12318: all-target-libstdc++-v3] Error 2 > | # 00:05:43 make: *** [Makefile:1093: all] Error 2 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe binutils: > | 1 > | # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m33 --set gcc_override_configure=--with-float=hard: > | 2 > | # build_abe newlib: > | 4 > | # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m33 --set gcc_override_configure=--with-float=hard: > | 5 > | # build_abe gdb: > | 6 > | # build_abe qemu: > | 7 > > Used configuration : > *CI config* tcwg_gnu_embed_build arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m33 --with-float=hard --target_board=-mthumb/-march=armv8-m.main+dsp+fp/-mtune=cortex-m33/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m33 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1941. (Require Linaro login) Please let us know if you have a fix. Already fixed on trunk, with r17-2061-gadb4f4a064c009 > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in > * http://54.172.246.49:9090/jobs/tcwg_gnu_embed_build--master-thumb_m33_hard_… > 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_build--master-thumb_m33_hard_… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_build--master-thumb_m33_hard_… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_embed_build--master-thumb_m33_hard_… > > 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

3 weeks, 5 days

[Linaro-TCWG-CI] glibc-2.43.9000-441-g07c24f35392: 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 glibc_check master-aarch64, after: | commit glibc-2.43.9000-441-g07c24f35392 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Tue Apr 14 10:50:37 2026 -0300 | | posix: Fix stack overflow in wordexp tilde expansion (BZ 34091, CVE-2026-6791) | | The parse_tilde function previously used strndupa to allocate memory | for the parsed username on the stack, and since the input is | user-defined, this can lead to a stack overflow. | ... 8 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:posix ... | FAIL: posix/tst-wordexp-tilde Used configuration : *CI config* tcwg_glibc_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1940. (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-aarch64-build/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_glibc_check--master-aarch64-build/build… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build… Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build… Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-aarch64-build/build… 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=07c24f35392b727e6100…

4 weeks

Re: [Linaro-TCWG-CI] llvmorg-23-init-19659-g3fee6e5ab45d: 18533 regressions on aarch64

by Michael Kruse

I think this is a misattribution of the failure. #203481 is a change of the CMake build system, it does not change anything functional in the flang compiler. #203481 had a build problem which was fixed in #204438. But since Flang built successfully, it cannot be the problem of that CI problem. Michael Am Fr., 19. Juni 2026 um 13:56 Uhr schrieb <ci_notify(a)linaro.org>: > > 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-19659-g3fee6e5ab45d > | Author: Michael Kruse <llvm-project(a)meinersbur.de> > | Date: Wed Jun 17 16:13:40 2026 +0200 > | > | [Flang] Add mock flang driver (#203481) > | > | Add a mock driver to pass CMake's compiler introspection for > | CMake_Fortran_COMPILER. It's purpose is to not having to build the full > | flang compiler for the runtimes-configure phase in > | ... 59 lines of the commit log omitted. > > Produces 18533 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0004 ... > | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0001.test > | NOEXE: test-suite :: Fujitsu/Fortran/0004/Fujitsu-Fortran-0004_0002.test > | Running test-suite:Fujitsu/Fortran/0005 ... > | NOEXE: test-suite :: Fujitsu/Fortran/0005/Fujitsu-Fortran-0005_0001.test > | ... and 19173 more > | # "NOEXE" means : the test program cannot be compiled > > Used configuration : > * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld > * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} > cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-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-2235. (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/3fee6e5ab45d1d352f995ae4eafa510… -- Tardyzentrismus verboten!

4 weeks

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

1 month

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

1 month

Re: [Linaro-TCWG-CI] llvmorg-23-init-18988-g9ce63d09cff0: 2 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, This test is incorrect. I apologize for the false detection. This issue involves the emergence of precision errors due to a change in the evaluation path for complex number division. Therefore, we will correct the tests. 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年6月15日 14:56 宛先: 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>; carlo.bertolli(a)amd.com <carlo.bertolli(a)amd.com> 件名: [Linaro-TCWG-CI] llvmorg-23-init-18988-g9ce63d09cff0: 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_vls-lto-lld, after: | commit llvmorg-23-init-18988-g9ce63d09cff0 | Author: carlobertolli <carlo.bertolli(a)amd.com> | Date: Thu Jun 11 14:19:36 2026 -0500 | | [AMDGPU][SCEV] Tighten max backedge-taken count for shift recurrence loops. (#197292) | | Application code on AMDGPUs often uses the following pattern: | | for (int i = blockDim.x / 2; i >= 1; i >>= 1) | ... 19 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0640 ... | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0306.test | Running test-suite:Fujitsu/Fortran/0641 ... | FAIL: test-suite :: Fujitsu/Fortran/0641/Fujitsu-Fortran-0641_0279.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-2234. (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/9ce63d09cff0bf07da9623b75301011…

1 month

Re: [Linaro-TCWG-CI] gcc-17-1246-g341ad729c2c: 2 regressions on arm

by Tomasz Kaminski

This seem like a testplatform issue, as this test (and many others) fails with: qemu-arm: unable to find CPU model 'cortex-a9' On Mon, Jun 22, 2026 at 11:10 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 arm-eabi v7-a softfp, after: > | commit gcc-17-1246-g341ad729c2c > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Thu May 28 08:37:33 2026 +0200 > | > | libstdc++: Add (generic_)display_string and > (generic_)native_encoded_string to filesystem::path > | > | Furthermore string and generic_string method as marked as > deprecated > | in C++26 mode. > | > | ... 54 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 27_io/filesystem/path/generic/display_native_string.cc > -std=gnu++26 execution test > | FAIL: 27_io/filesystem/path/native/display_native_string.cc > -std=gnu++26 execution test > > 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-1938. (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/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git >

1 month

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

1 month, 1 week

(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

1 month, 1 week

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain