linaro-toolchain May 2026

linaro-toolchain@lists.linaro.org

8 participants
18 discussions

Re: [Linaro-TCWG-CI] gcc-17-761-g44c5f9a37aa: 4 regressions on master-thumb_m55_hard_eabi

by Andrew Pinski

Fixed with https://gcc.gnu.org/pipermail/gcc-cvs/2026-May/454624.html On Fri, May 29, 2026 at 2:26 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 cortex-m55 hard, after: > | commit gcc-17-761-g44c5f9a37aa > | Author: Andrew Pinski <andrew.pinski(a)oss.qualcomm.com> > | Date: Mon May 25 12:44:48 2026 -0700 > | > | match: Fix up `(smaller)a ==/!= (smaller) b` pattern for pointers [PR125453] > | > | While reviewing r17-632-g1c9808a71207eb, I missed that it was valid (in gimple) > | to cast from a pointer to a smaller integral type. That meant with that > | pattern we would get `ptr ^ ptr` which is invalid gimple. > | ... 16 lines of the commit log omitted. > > Produces 4 regressions: > | > | regressions.sum: > | Running gcc:gcc.dg/torture/dg-torture.exp ... > | FAIL: gcc.dg/torture/pr125453-1.c -O2 (test for excess errors) > | FAIL: gcc.dg/torture/pr125453-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors) > | FAIL: gcc.dg/torture/pr125453-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) > | FAIL: gcc.dg/torture/pr125453-1.c -O3 -g (test for excess errors) > > 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-1915. (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-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

4 days, 2 hours

Re: [Linaro-TCWG-CI] gcc-17-808-ge309e09187c: 21 regressions on aarch64

by Jonathan Wakely

On Tue, 26 May 2026 at 23:58, <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-808-ge309e09187c > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu May 21 17:09:47 2026 +0100 > | > | libstdc++: Deprecate std::memory_order::consume > | > | This implements P3475R2, "Defang and deprecate memory_order::consume", > | approved in Hagenberg, 2025. > | > | ... 33 lines of the commit log omitted. > > Produces 21 regressions: > | > | regressions.sum: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 29 not found: " *inlined from [^\n\r]+.C:23:.*" > | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 44 not found: " *inlined from [^\n\r]+.C:36:.*" > | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 46 not found: " *inlined from [^\n\r]+.C:39:.*" > | FAIL: g++.dg/warn/Winvalid-memory-model-2.C -std=gnu++11 dg-regexp 74 not found: " *inlined from [^\n\r]+.C:66:.*" > | ... and 17 more > > 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-1912. (Require Linaro login) Please let us know if you have a fix. This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125465 > > 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

6 days, 9 hours

Re: [Linaro-TCWG-CI] llvmorg-23-init-15954-g998d8e87daf3: 2 regressions on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, Probably this error is false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the test. I apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信日時: 2026年5月24日 17:20 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> CC: jason.van-beusekom(a)hpe.com <jason.van-beusekom(a)hpe.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> 件名: [Linaro-TCWG-CI] llvmorg-23-init-15954-g998d8e87daf3: 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-15954-g998d8e87daf3 | Author: Jason Van Beusekom <jason.van-beusekom(a)hpe.com> | Date: Tue May 19 11:13:42 2026 -0500 | | [Flang][Fir] Set default alignment of array globals to 64 bytes (#194969) | | This commit implements the proposal from the RFC: | https://discourse.llvm.org/t/rfc-alignment-of-global-arrays/90397/13 | | ... 3 lines of the commit log omitted. Produces 2 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0679 ... | FAIL: test-suite :: Fujitsu/Fortran/0679/Fujitsu-Fortran-0679_0248.test | FAIL: test-suite :: Fujitsu/Fortran/0679/Fujitsu-Fortran-0679_0249.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-2224. (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/998d8e87daf371b51822ce97e360467…

6 days, 17 hours

[Linaro-TCWG-CI] glibc-2.43.9000-347-gb75ad99d45: 170 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-347-gb75ad99d45 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Fri May 22 14:08:13 2026 -0300 | | elf: Initialize TCB and stack-protector before static IFUNC resolvers (BZ 20680, BZ 27582, BZ 28817) | | In static linking the IFUNC IPLT (apply_irel for non-PIE, the IRELATIVE | phase inside _dl_relocate_static_pie for static-pie) ran before | __libc_setup_tls and before _dl_setup_stack_chk_guard. When a resolver | ... 45 lines of the commit log omitted. Produces 170 regressions: | | regressions.sum: | Running glibc:ctype ... | FAIL: ctype/tst-ctype-tls-dlopen-static | Running glibc:debug ... | FAIL: debug/tst-sprintf-fortify-rdonly-static | Running glibc:dlfcn ... | ... and 180 more 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-1911. (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=b75ad99d45b7475eca46…

1 week, 1 day

[Linaro-TCWG-CI] binutils-2_41-release-10873-gffea43122dc: 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 binutils_check master-aarch64, after: | commit binutils-2_41-release-10873-gffea43122dc | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Sat May 23 05:12:10 2026 +0800 | | alpha: Properly handle local weak undefined symbols | | Since the local undefined TLS symbol address isn't mapped to any TLS | storage, it isn't usable. Set its value to 0 to avoid relocation overflow. | When processing TLS relocations, elf_hash_table (info)->tls_sec can be | ... 36 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running ld:ld-elf/tls.exp ... | FAIL: pr34165 Used configuration : *CI config* tcwg_binutils_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-1910. (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_binutils_check--master-aarch64-build/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_binutils_check--master-aarch64-build/bu… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… Current build : http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… Reference build : http://54.172.246.49:9090/jobs/tcwg_binutils_check--master-aarch64-build/bu… 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=ffea43122dc5d…

1 week, 1 day

Re: [Linaro-TCWG-CI] llvmorg-23-init-15486-gad7e6ca2b362: 1 regression 1 fix on aarch64

by Yasuyuki Ohno (Fujitsu)

Hi, Probably this error is false detections caused by precision errors in floating-point arithmetic. Please ignore the mail. We'll update the test. I apologize for the false detection. Best regards, Yasuyuki Ohno Software Development Div., Advanced Technology Development Unit, Fujitsu Research, Fujitsu Limited, JAPAN. ________________________________ 差出人: ci_notify(a)linaro.org <ci_notify(a)linaro.org> 送信日時: 2026年5月19日 2:43 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> CC: kese111(a)gmail.com <kese111(a)gmail.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> 件名: [Linaro-TCWG-CI] llvmorg-23-init-15486-gad7e6ca2b362: 1 regression 1 fix 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-15486-gad7e6ca2b362 | Author: hanbeom <kese111(a)gmail.com> | Date: Fri May 15 15:06:39 2026 +0900 | | [mlir][complex] Emit fma for contracted complex.mul lowering (#196248) | | When complex.mul has fastmath<contract>, lower it using explicit fused | multiply-add operations for the real and imaginary components. | | ... 15 lines of the commit log omitted. Produces 1 regression 1 fix: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0672 ... | FAIL: test-suite :: Fujitsu/Fortran/0672/Fujitsu-Fortran-0672_0048.test | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one | | fixes.sum: | Running test-suite:Fujitsu/Fortran/0289 ... | FAIL: test-suite :: Fujitsu/Fortran/0289/Fujitsu-Fortran-0289_0033.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-2220. 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/ad7e6ca2b3624319b86543010961959…

1 week, 2 days

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.

1 week, 2 days

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

1 week, 6 days

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

2 weeks

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…

2 weeks

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain May 2026