linaro-toolchain May 2026

linaro-toolchain@lists.linaro.org

6 participants
12 discussions

Re: [Linaro-TCWG-CI] binutils patch #135507: 1 regression on aarch64

by H.J. Lu

On Sun, May 24, 2026 at 10:23 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 binutils_check master-aarch64, after: > | binutils patch https://patchwork.sourceware.org/patch/135507 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Sat May 23 05:12:10 2026 +0800 > | > | [PATCH v3] alpha: Don't assert elf_hash_table (info)->tls_sec != NULL > | > | When processing TLS relocations, elf_hash_table (info)->tls_sec can be > | NULL if all TLS symbols are weak, hidden and undefined. Don't assert > | elf_hash_table (info)->tls_sec != NULL. Since the undefined TLS symbol > | ... 29 lines of the commit log omitted. > | ... applied on top of baseline commit: > | ee4da5f3ae2 Automatic date update in version.in > > Produces 1 regression: > | > | regressions.sum: > | Running ld:ld-elf/tls.exp ... > | FAIL: pr34165 This exposed an aarch64 linker bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34165 -- H.J.

19 hours, 37 minutes

Re: [Linaro-TCWG-CI] gcc-17-570-g79e29562907b: 1 regression on aarch64

by Jonathan Wakely

I'm not sure yet another bug about these middle end warnings is useful! I'll let somebody else decide that. You can ignore it though, your patch isn't the problem here, it just revealed it. On Wed, 20 May 2026, 09:17 Avi Kivity, <avi(a)scylladb.com> wrote: > > > On Tue, May 19, 2026 at 4:03 PM Jonathan Wakely <jwakely.gcc(a)gmail.com> > wrote: > >> On Tue, 19 May 2026 at 11:57, Jonathan Wakely <jwakely.gcc(a)gmail.com> >> wrote: >> > >> > On Tue, 19 May 2026 at 10:29, Avi Kivity <avi(a)scylladb.com> wrote: >> > > >> > > >> > > >> > > On Tue, May 19, 2026 at 11:03 AM Avi Kivity <avi(a)scylladb.com> wrote: >> > >> >> > >> >> > >> >> > >> On Tue, May 19, 2026 at 2:22 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-17-570-g79e29562907b >> > >>> | Author: Avi Kivity <avi(a)scylladb.com> >> > >>> | Date: Thu Feb 26 19:59:41 2026 +0200 >> > >>> | >> > >>> | libstdc++: optimize std::uninitialized_move{,_n}() to >> memcpy when possible [PR121789] >> > >>> | >> > >>> | std::uninitialized_move{,_n} delegates to the corresponding >> > >>> | std::uninitialized_copy() variant after wrapping with a move >> > >>> | iterator, but the std::uninitialized_copy() doesn't unwrap >> the >> > >>> | ... 17 lines of the commit log omitted. >> > >>> >> > >>> Produces 1 regression: >> > >>> | >> > >>> | regressions.sum: >> > >>> | Running g++:g++.dg/torture/dg-torture.exp ... >> > >>> | FAIL: g++.dg/torture/pr118521.C -O1 (test for excess errors) >> > >> >> > >> >> > >> I'll take a look. >> > > >> > > >> > > In file included from /mnt/gcc.bin/include/c++/17.0.0/vector:67, >> > > from ./gcc/testsuite/g++.dg/torture/pr118521.C:5: >> > > In function ‘_ForwardIterator >> std::uninitialized_fill_n(_ForwardIterator, _Size, const _Tp&) [with >> _ForwardIterator = char*; _Size = long unsigned int; _Tp = char]’, >> > > inlined from ‘constexpr _ForwardIterator >> std::__uninitialized_fill_n_a(_ForwardIterator, _Size, const _Tp&, >> allocator<_Tp>&) [with _ForwardIterator = char*; _Size = long unsigned int; >> _Tp = char; _Tp2 = char]’ at >> /mnt/gcc.bin/include/c++/17.0.0/bits/stl_uninitialized.h:778:39, >> > > inlined from ‘constexpr void std::vector<_Tp, >> _Alloc>::_M_fill_append(size_type, const value_type&) [with _Tp = char; >> _Alloc = std::allocator<char>]’ at >> /mnt/gcc.bin/include/c++/17.0.0/bits/vector.tcc:776:36, >> > > inlined from ‘constexpr void std::vector<_Tp, >> _Alloc>::_M_fill_insert(iterator, size_type, const value_type&) [with _Tp = >> char; _Alloc = std::allocator<char>]’ at >> /mnt/gcc.bin/include/c++/17.0.0/bits/vector.tcc:668:20, >> > > inlined from ‘constexpr std::vector<_Tp, _Alloc>::iterator >> std::vector<_Tp, _Alloc>::insert(const_iterator, size_type, const >> value_type&) [with _Tp = char; _Alloc = std::allocator<char>]’ at >> /mnt/gcc.bin/include/c++/17.0.0/bits/stl_vector.h:1565:16, >> > > inlined from ‘void foo()’ at >> ./gcc/testsuite/g++.dg/torture/pr118521.C:12:11: >> > > /mnt/gcc.bin/include/c++/17.0.0/bits/stl_uninitialized.h:577:39: >> warning: ‘void* __builtin_memset(void*, int, long unsigned int)’ writing 2 >> bytes into a region of size 0 overflows the destination >> [-Wstringop-overflow=] >> > > 577 | __builtin_memset(__dest, (unsigned >> char)__x, __n); >> > > | >> ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> > > >> > > I think it's a victim of an existing (and very annoying) misdetection >> of memory overwrites (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125187). >> It's not directly related to my patch (which optimizes moving a range, not >> filling it), but my patch changes the detection logic causing gcc to think >> the region is of size 0 (where it should be 4). >> > >> > Yes, these middle-end warnings are a plague, but I don't see why your >> > patch (which I pushed yesterday) changes the >> > __uninitialized_fill_n_a() path which uses memset. Your patch only >> > affects the uninitialized_copy() path which uses memcpy. >> >> The __uninitialized_fill_n_a function on line 776 is only used when >> there's enough room for it: >> >> if (size_type(this->_M_impl._M_end_of_storage >> - this->_M_impl._M_finish) >= __n) >> { >> _GLIBCXX_ASAN_ANNOTATE_GROW(__n); >> this->_M_impl._M_finish = >> std::__uninitialized_fill_n_a(this->_M_impl._M_finish, __n, __x, >> _M_get_Tp_allocator()); >> >> But the poxy warning decides maybe there's some way to reach it where >> (end_of_storage - finish) == 0. >> >> As Avi said, it's likely that the else branch for the condition above >> got simplified by the patch, which allowed GCC to make better (and >> then eventually, much worse) analysis for the call above. >> >> >> > How to proceed? > > I suggest to file a bug and mark the failure as XFAIL. > > > >> >> >> >> >> > >> > >> > >> > >> > > >> > > I enhanced the test code to be a full program and verified it works >> with asan. >> > > >> > > I'm not sure how to proceed. I don't want to patch pr118521.C to >> disable -Wstringop-overflow, since that's what it's testing. >> > > >> > > Copying Richard, the original author of the test >> (a2755339c6c9832467c573d956e91565943ecdc1). >> > > >> > >> >> > >> >> > >>> >> > >>> >> > >>> 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-1906. 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, 13 hours

Re: [Linaro-TCWG-CI] gcc-17-570-g79e29562907b: 1 regression on aarch64

by Jonathan Wakely

On Tue, 19 May 2026 at 10:29, Avi Kivity <avi(a)scylladb.com> wrote: > > > > On Tue, May 19, 2026 at 11:03 AM Avi Kivity <avi(a)scylladb.com> wrote: >> >> >> >> On Tue, May 19, 2026 at 2:22 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-17-570-g79e29562907b >>> | Author: Avi Kivity <avi(a)scylladb.com> >>> | Date: Thu Feb 26 19:59:41 2026 +0200 >>> | >>> | libstdc++: optimize std::uninitialized_move{,_n}() to memcpy when possible [PR121789] >>> | >>> | std::uninitialized_move{,_n} delegates to the corresponding >>> | std::uninitialized_copy() variant after wrapping with a move >>> | iterator, but the std::uninitialized_copy() doesn't unwrap the >>> | ... 17 lines of the commit log omitted. >>> >>> Produces 1 regression: >>> | >>> | regressions.sum: >>> | Running g++:g++.dg/torture/dg-torture.exp ... >>> | FAIL: g++.dg/torture/pr118521.C -O1 (test for excess errors) >> >> >> I'll take a look. > > > In file included from /mnt/gcc.bin/include/c++/17.0.0/vector:67, > from ./gcc/testsuite/g++.dg/torture/pr118521.C:5: > In function ‘_ForwardIterator std::uninitialized_fill_n(_ForwardIterator, _Size, const _Tp&) [with _ForwardIterator = char*; _Size = long unsigned int; _Tp = char]’, > inlined from ‘constexpr _ForwardIterator std::__uninitialized_fill_n_a(_ForwardIterator, _Size, const _Tp&, allocator<_Tp>&) [with _ForwardIterator = char*; _Size = long unsigned int; _Tp = char; _Tp2 = char]’ at /mnt/gcc.bin/include/c++/17.0.0/bits/stl_uninitialized.h:778:39, > inlined from ‘constexpr void std::vector<_Tp, _Alloc>::_M_fill_append(size_type, const value_type&) [with _Tp = char; _Alloc = std::allocator<char>]’ at /mnt/gcc.bin/include/c++/17.0.0/bits/vector.tcc:776:36, > inlined from ‘constexpr void std::vector<_Tp, _Alloc>::_M_fill_insert(iterator, size_type, const value_type&) [with _Tp = char; _Alloc = std::allocator<char>]’ at /mnt/gcc.bin/include/c++/17.0.0/bits/vector.tcc:668:20, > inlined from ‘constexpr std::vector<_Tp, _Alloc>::iterator std::vector<_Tp, _Alloc>::insert(const_iterator, size_type, const value_type&) [with _Tp = char; _Alloc = std::allocator<char>]’ at /mnt/gcc.bin/include/c++/17.0.0/bits/stl_vector.h:1565:16, > inlined from ‘void foo()’ at ./gcc/testsuite/g++.dg/torture/pr118521.C:12:11: > /mnt/gcc.bin/include/c++/17.0.0/bits/stl_uninitialized.h:577:39: warning: ‘void* __builtin_memset(void*, int, long unsigned int)’ writing 2 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=] > 577 | __builtin_memset(__dest, (unsigned char)__x, __n); > | ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > I think it's a victim of an existing (and very annoying) misdetection of memory overwrites (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125187). It's not directly related to my patch (which optimizes moving a range, not filling it), but my patch changes the detection logic causing gcc to think the region is of size 0 (where it should be 4). Yes, these middle-end warnings are a plague, but I don't see why your patch (which I pushed yesterday) changes the __uninitialized_fill_n_a() path which uses memset. Your patch only affects the uninitialized_copy() path which uses memcpy. > > I enhanced the test code to be a full program and verified it works with asan. > > I'm not sure how to proceed. I don't want to patch pr118521.C to disable -Wstringop-overflow, since that's what it's testing. > > Copying Richard, the original author of the test (a2755339c6c9832467c573d956e91565943ecdc1). > >> >> >>> >>> >>> 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-1906. 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

5 days, 9 hours

Re: [Linaro-TCWG-CI] llvmorg-23-init-15424-g3def12d2a418: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, With the https://github.com/llvm/llvm-project/commit/3def12d2a418f8e49f0b88ddf9070af… , the result of `ieee_support_rounding()` for `ieee_other` has been corrected so that `.false.` is now the correct value. This test expects `.true.`, but following the correction above, the correct result is now `.false.`. Therefore, this test is incorrect. I apologize for the false detection. We'll correct this 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月16日 14:38 宛先: 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>; kwyatt.external(a)hpe.com <kwyatt.external(a)hpe.com> 件名: [Linaro-TCWG-CI] llvmorg-23-init-15424-g3def12d2a418: 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-15424-g3def12d2a418 | Author: kwyatt-ext <kwyatt.external(a)hpe.com> | Date: Thu May 14 13:17:40 2026 -0500 | | [flang] Corrected constant folding for IEEE_OTHER in IEEE_SUPPORT_ROUNDING (#197534) | | Modified to report expected value of FALSE for constant folded | IEEE_OTHER support. | | ... 1 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0923 ... | FAIL: test-suite :: Fujitsu/Fortran/0923/Fujitsu-Fortran-0923_0004.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-2219. 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/3def12d2a418f8e49f0b88ddf9070af…

5 days, 17 hours

Re: [Linaro-TCWG-CI] llvmorg-23-init-13786-gc549abab5d18: 5 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, These tests are incorrect. Details are as follows: OpenMP 6.0 : 7.1.1 Variables Referenced in a Construct The loop-iteration variable in any affected loop of a loop-nest-associated directive may be listed in a private or lastprivate clause. ->Therefore, a shared clause cannot be specified. I apologize for the false detection. We'll correct these 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年5月3日 8:11 宛先: 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> 件名: [Linaro-TCWG-CI] llvmorg-23-init-13786-gc549abab5d18: 5 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O0-debug, after: | commit llvmorg-23-init-13786-gc549abab5d18 | Author: Krzysztof Parzyszek <Krzysztof.Parzyszek(a)amd.com> | Date: Fri May 1 08:09:36 2026 -0500 | | [flang][OpenMP] Check conflicts between predetermined/explicit DSA (#194961) | | Improve checks for loop iteration variables with predetermined DSA | appearing in DSA clauses. Show both the location of the variable in the | offending clause, and in the loop. | ... 3 lines of the commit log omitted. Produces 5 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0162 ... | NOEXE: test-suite :: Fujitsu/Fortran/0162/Fujitsu-Fortran-0162_0024.test | Running test-suite:Fujitsu/Fortran/0165 ... | NOEXE: test-suite :: Fujitsu/Fortran/0165/Fujitsu-Fortran-0165_0026.test | NOEXE: test-suite :: Fujitsu/Fortran/0165/Fujitsu-Fortran-0165_0027.test | ... and 2 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="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2214. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-O0-debug-build… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/c549abab5d18bae56ef9b91d5991fa6…

6 days, 15 hours

[Linaro-TCWG-CI] binutils-2_41-release-10810-g520c7eefed7: Failure 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 cross, after: | commit binutils-2_41-release-10810-g520c7eefed7 | Author: Simon Marchi <simon.marchi(a)efficios.com> | Date: Thu May 7 15:23:12 2026 -0400 | | binutils/configure: look for msgpack-c.pc (in addition to msgpack.pc) | | msgpack.pc was renamed to msgpack-c.pc in this commit [1]. This means | that we now find both in the wild. For example Debian Bookworm has | msgpack.pc [2] while Debian Trixie has msgpack-c.pc [3]. | ... 7 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | # FAILED | # build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a: | # build_abe linux: | # build_abe glibc: | # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a: | # build_abe gdb: | # build_abe qemu: | # First few build errors in logs: | # 00:01:19 configure: error: Package requirements (msgpack) were not met: | # 00:01:19 make[1]: *** [Makefile:4066: configure-binutils] Error 1 | # 00:01:19 make: *** [Makefile:1033: 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=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--enable-fix-cortex-a53-835769 --set gcc_override_configure=--enable-fix-cortex-a53-843419 --set gcc_override_configure=--with-arch=armv8-a: | 5 | # build_abe gdb: | 6 | # build_abe qemu: | 7 Used configuration : *CI config* tcwg_gnu_cross_build aarch64-linux-gnu cross *configure and test flags:* --target aarch64-linux-gnu --disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a We track this bug report under https://linaro.atlassian.net/browse/GNU-1903. 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 * http://54.172.246.49:9090/jobs/tcwg_gnu_cross_build--master-aarch64-build/b… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_gnu_cross_build--master-aarch64-build/b… Current build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_build--master-aarch64-build/b… Reference build : http://54.172.246.49:9090/jobs/tcwg_gnu_cross_build--master-aarch64-build/b… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/binut… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=520c7eefed7f9…

1 week, 2 days

Re: [Linaro-TCWG-CI] gcc-17-496-gda540dc6d763: 7 regressions on arm

by Tomasz Kaminski

On Thu, May 14, 2026 at 7:43 PM <ci_notify(a)linaro.org> wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In armv8l-unknown-linux-gnueabihf native, after: > | commit gcc-17-496-gda540dc6d763 > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Wed May 13 14:51:02 2026 +0200 > | > | libstdc++: Test for unsupported engine range for 128bits floating > points [PR119739] > | > | This patch add test illustrating, that after implementing P0952 "A > new specification for > | std::generate_canonical", generators, that emit range of > non-power-of-two size, that > | span over B bits, are not supported in combination with 128bits > integer are not > | ... 16 lines of the commit log omitted. > > Produces 7 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: > 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc > -std=gnu++20 (test for errors, line 57) > | FAIL: > 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc > -std=gnu++20 (test for errors, line 58) > | FAIL: > 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc > -std=gnu++20 (test for errors, line 65) > | FAIL: > 26_numerics/random/uniform_real_distribution/operators/gencanon_eng_neg.cc > -std=gnu++20 (test for errors, line 66) > | ... and 3 more > > Used configuration : > *CI config* tcwg_gcc_check armv8l-unknown-linux-gnueabihf > *configure and test flags:* none, autodetected on > armv8l-unknown-linux-gnueabihf--disable-multilib --with-float=hard > --with-mode=thumb --with-tune=cortex-a9 --with-arch=armv7-a > --with-fpu=neon-fp-armv8 > > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1902. Please let us know if you > have a fix. > Thanks for the report. This should already be fixed on trunk by https://gcc.gnu.org/cgit/gcc/commit/?id=5d17eec7d83445ba4f960c81c386be33bae… libstdc++: Mark gencanon_eng_neg test as unsupported if __float128 is not available > 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-arm-build/builds/1020… > 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-arm-build/builds/1020… > The list of [ignored] baseline and flaky failures are in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1020… > > 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, 2 days

Re: [Linaro-TCWG-CI] llvmorg-23-init-12953-g1348766d1d68: 1 regression on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, Probably these errors are false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the tests. I apologize for the false detection. Details are as follows. The primary purpose of this TP (https://github.com/fujitsu/compiler-test-suite/blob/main/Fortran/0683/0683_…) is to verify OpenMP SIMD reduction. However, since -fopenmp is not specified, !$omp simd is treated as a comment. Consequently, we are currently verifying the results of sequential calculations for single-precision complex numbers. In this TP, we determine whether the result is OK or NG by calculating the size of the complex difference in the accumulation results for single-precision complex numbers. Due to SLP vectorization, a difference arose in the accumulation results, and the difference between the calculated value and the expected value was 3 ULP in the real part and 5 ULP in the imaginary part. Consequently, the size of the complex difference is 5.8309517, which exceeds the threshold of 5.0, resulting in an NG. Since the difference is approximately 5 ULP, it is considered to be within the range of rounding errors associated with single-precision complex integration. if (abs(ss-result) < 5.0) then print *, "PASS" else print *, ss, abs(ss-result) endif Expected values: (-15069242.0, -9596797.00) Actual values: (-15069245.0, -9596802.00) Therefore, we make the following two corrections. ・To verify OpenMP SIMD reduction, which is the original objective, specify the -fopenmp option. ・Due to vectorization, a difference of 3 ULP in the real part and 5 ULP in the imaginary part has arisen in the single-precision complex multiplication. In this test, the size of the complex difference is calculated as abs(ss - result)\ , but the current threshold of 5.0 does not allow for a complex difference of 5.8309517. To allow for rounding errors of approximately 5 ULP as complex differences, the threshold will be relaxed from 5.0 to 6.0. 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 年 4 月 30 日 (木曜日) 0:41 宛先: 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> 件名: [Linaro-TCWG-CI] llvmorg-23-init-12953-g1348766d1d68: 1 regression on aarch64 [Some people who received this message don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-Ofast-sve_vla, after: | commit llvmorg-23-init-12953-g1348766d1d68 | Author: Alexey Bataev <a.bataev(a)outlook.com> | Date: Sat Apr 25 07:27:36 2026 -0400 | | [SLP]Initial support for non-power-of-2 vectorization | | Enables non-power-of-2 vectorization within the SLP tree. The root nodes | are still required to be power-of-2, will be addressed in a follow-up | patches. | ... 4 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0683 ... | FAIL: test-suite :: Fujitsu/Fortran/0683/Fujitsu-Fortran-0683_0101.test | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;clang-tools-extra" "-DLLVM_ENABLE_RUNTIMES=openmp" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH} cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin2/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin2/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin2/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu -DTEST_SUITE_FUJITSU_WITH_FAST_MATH=ON "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-2211. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… Reference build : http://54.172.246.49:9090/jobs/tcwg_flang_test--main-aarch64-Ofast-sve_vla-… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/llvm/… Full commit : https://github.com/llvm/llvm-project/commit/1348766d1d686b8825bdaa2f6638c17…

1 week, 3 days

[Linaro-TCWG-CI] glibc-2.43.9000-304-g1cc165baed2: 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-304-g1cc165baed2 | Author: Frédéric Bérat <fberat(a)redhat.com> | Date: Wed Apr 29 13:26:38 2026 +0200 | | test: Add gconv refcount leak test for swscanf | | Add a new internal test, `tst-wcsmbs-clone-overflow`, to verify correct | gconv module reference counting. The Makefile is updated to include this | test in the `tests-internal` list and ensure it runs with generated locales. | ... 9 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:wcsmbs ... | FAIL: wcsmbs/tst-wcsmbs-clone-overflow 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-1900. 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=1cc165baed20b6589ef2…

1 week, 5 days

Re: [Linaro-TCWG-CI] gcc-17-277-gc0c911821ba: 3 regressions 3 fixes on master-thumb_m55_hard_eabi

by Laurent Alfonsi

Typo in this email : We track this bug report under https://linaro.atlassian.net/browse/GNU-1898 . Please let us know if you have a fix. On Tue, 5 May 2026 at 23:21, <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-17-277-gc0c911821ba > | Author: Xi Ruoyao <xry111(a)xry111.site> > | Date: Sat May 2 02:15:42 2026 +0800 > | > | testsuite: don't link top-level asm tests as PIE [PR 70150] > | > | If these tests are linked as PIE, the linker ends up creating > runtime > | text relocation and warns or errors out. > | > | ... 8 lines of the commit log omitted. > > Produces 3 regressions 3 fixes: > | > | regressions.sum: > | Running gcc:gcc.dg/lto/lto.exp ... > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=1to1 -no-pie > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=cache -no-pie > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=max -no-pie > | > | fixes.sum: > | Running gcc:gcc.dg/lto/lto.exp ... > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=1to1 > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=cache > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=max > > 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/Please > specify 'Project' and 'IssueType'.. 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-thumb_m55_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_m55_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_m55_h… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_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

1 week, 5 days

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain May 2026