- linaro-toolchain - lists.linaro.org

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

27 minutes

1
0
0 0

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 >

13 hours, 57 minutes

1
0
0 0

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

3 days

1
0
0 0

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

3 days, 7 hours

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-17-383-g1a06a37611e: Failure on aarch64

by Laurent Alfonsi

Typo in this email : We track this bug report under https://linaro.atlassian.net/browse/GNU-1897 . Please let us know if you have a fix. On Fri, 8 May 2026 at 17:49, <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 bootstrap_build master-aarch64-bootstrap_debug, after: > | commit gcc-17-383-g1a06a37611e > | Author: Roger Sayle <roger(a)nextmovesoftware.com> > | Date: Thu May 7 18:46:37 2026 +0100 > | > | PR middle-end/122871: Doubleword multiplication improvements > | > | This patch resolves PR middle-end/122871 by improving RTL > expansion of > | doubleword multiplications. The main change is to synth_mult > adding > | support for the case where the constant being multiplied has > BITS_PER_WORD > | ... 64 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap_debug: > | # FAILED > | # First few build errors in logs: > | # 00:24:37 > /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/expmed.h:398:61: > error: array subscript -1 is below array bounds of ‘int [64]’ > [-Werror=array-bounds=] > | # 00:24:50 make[3]: *** [Makefile:1217: expmed.o] Error 1 > | # 00:24:50 make[2]: *** [Makefile:5182: all-stage2-gcc] Error 2 > | # 00:24:50 make[1]: *** [Makefile:26490: stage2-bubble] Error 2 > | # 00:24:50 make: *** [Makefile:1140: all] Error 2 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap_debug: > | 1 > > Used configuration : > *CI config* tcwg_bootstrap_build master-aarch64-bootstrap_debug > *configure and test flags:* none, autodetected on > aarch64-unknown-linux-gnu > > 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 > * > http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr… > The full lists of regressions and improvements as well as configure and > make commands are in > * > http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_bootstrap_build--master-aarch64-bootstr… > > 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 days, 7 hours

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-17-359-g9a231dbb68ab: 3 regressions on arm

by Laurent Alfonsi

Typo in this email : We track this bug report under https://linaro.atlassian.net/browse/GNU-1896 . Please let us know if you have a fix. On Thu, 7 May 2026 at 18:52, <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-359-g9a231dbb68ab > | Author: David Malcolm <dmalcolm(a)redhat.com> > | Date: Wed May 6 09:57:07 2026 -0400 > | > | analyzer: add data flow events > | > | Analyzer warnings relating to problematic values (e.g. by division > | by zero) can be difficult for the user to understand. > | > | ... 421 lines of the commit log omitted. > > Produces 3 regressions: > | > | regressions.sum: > | Running gcc:gcc.dg/analyzer/analyzer.exp ... > | FAIL: gcc.dg/analyzer/divide-by-zero-6.c (test for warnings, line 17) > | FAIL: gcc.dg/analyzer/divide-by-zero-6.c at line 18 (test for > warnings, line 17) > | FAIL: gcc.dg/analyzer/divide-by-zero-6.c (test for excess errors) > > 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/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_gcc_check--master-arm-build/builds/1017… > 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/1017… > The list of [ignored] baseline and flaky failures are in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1017… > > 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 days, 7 hours

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-7460-g682c95b80872: no regression/no fix on master-thumb_m55_hard_eabi

by Tomasz Kaminski

Hi, Neither the reference nor the current build includes later fixes for zero_padding.cc file, in particular: > commit 3a41229f92022bfb388911854d597721fce76714 > Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > Date: Thu Mar 5 08:57:24 2026 +0100 > > libstdc++: Fix atomic/cons/zero_padding.cc test for arm-none-eabi [PR124124] > > The test uses dg-require-atomic-cmpxchg-word that checks if atomic compare > exchange is available for pointer sized integers, and then test types that > are eight bytes in size. This causes issue for targets for which pointers > are four byte and libatomic is not present, like arm-none-eabi. > commit f3ba5ad088cebe117f857329a35b95d18d97a808 > Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > Date: Tue Feb 17 13:35:39 2026 +0100 > > libstdc++: Correct requirements for atomic/cons/zero_padding.cc tests again [PR124124] > > The requirements introduced in previous patch r16-7548-g060d7c2a9c1fe1, > were not sufficient for types of size bigger than 64B (Ctor or long double), > as dg-add-options of libatomic, links libatomic only if it is required to > handle atomics of 64B types or pointers. Are issue still present on thunk build? On Mon, Apr 20, 2026 at 10:28 PM <ci_notify(a)linaro.org> wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In arm-eabi cortex-m55 hard, after: > | commit gcc-16-7460-g682c95b80872 > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Wed Feb 11 15:05:00 2026 +0100 > | > | libstdc++: Add test for atomic with padding on heap [PR123875] > | > | C++26 makes the values of uninitialized stack object erroneous, > | de-facto requiring their initialization, so adding a test for > | variable on heap. > | ... 8 lines of the commit log omitted. > > > 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-1877. 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 >

3 weeks, 3 days

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #133402: no regression/no fix on arm

by Rainer Orth

ci_notify(a)linaro.org writes: > 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: > | gcc patch https://patchwork.sourceware.org/patch/133402 > | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE> > | Date: Mon Apr 20 18:29:40 2026 +0200 > | > | [PATCH] testsuite: Check configured assembler in gcc.misc-tests/options.exp > | > | When I recently dropped --with-gnu-as from my builds which had become > | unnecessary, several tests started to FAIL, e.g. > | > | ... 45 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 416fe77efb4 d: Fix ICE in must_pass_in_stack_var_size_or_pad with D enums [PR123411] It's good to see you're running pre-commit checks. However, this report is particularly confusing in its current form: while the Subject states "no pregression/no fix on arm", the report starts with Our automatic CI has detected problems related to your patch(es). Please find some details below. ^^^^^^^^^^^^^^^^^^^^^ That sent me looking for regressions, but I couldn't find any. At first I thought I was beeing particularly stupid, but it seems that your CI found no issues at all with the patch. So please say so *prominently* in the body of the message, rather than confusing contributors and wasting their time. Rainer -- ----------------------------------------------------------------------------- Rainer Orth, Center for Biotechnology, Bielefeld University

3 weeks, 3 days

1
0
0 0

Fwd: [Linaro-TCWG-CI] gcc patch #133364: 113 regressions on aarch64

by Paul Richard Thomas

Hello there, According to the list of regressions below, all the failing tests are for the C compiler. I am at a bit of a loss to know how to proceed since the patch that you have fingered applies exclusively to fortran. Best regards Paul ---------- Forwarded message --------- From: <ci_notify(a)linaro.org> Date: Sun, 19 Apr 2026 at 23:05 Subject: [Linaro-TCWG-CI] gcc patch #133364: 113 regressions on aarch64 To: <paul.richard.thomas(a)gmail.com> Cc: <pault(a)gcc.gnu.org> Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In aarch64 native, after: | gcc patch https://patchwork.sourceware.org/patch/133364 | Author: Paul Thomas <pault(a)gcc.gnu.org> | Date: Sun Apr 19 15:00:14 2026 +0100 | | [PATCH] Fortran: ICE due to allocatable component in hidden type [PR117077] | | 2026-03-19 Paul Thomas <pault(a)gcc.gnu.org> | | gcc/fortran | ... 8 lines of the commit log omitted. | ... applied on top of baseline commit: | 68920b1f14d cse: Validate subreg replacements [PR124643] Produces 113 regressions: | | regressions.sum: | Running g++:g++.target/aarch64/aarch64.exp ... | FAIL: g++.target/aarch64/pr117048.C scan-assembler \\txar\\tv[0-9]+\\.2d, v[0-9]+\\.2d, v[0-9]+\\.2d, 32\\n | Running g++:g++.target/aarch64/sme2/aarch64-sme2-acle-asm.exp ... | FAIL: gcc.target/aarch64/sme2/acle-asm/svluti4_zt_1.c -std=c++11 -O0 -g -DTEST_FULL (test for excess errors) | FAIL: gcc.target/aarch64/sme2/acle-asm/svluti4_zt_1.c -std=c++11 -O0 -g -DTEST_OVERLOADS (test for excess errors) | ... and 120 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 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-precommit/bui… 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-precommit/bui… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui… Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui… Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.

3 weeks, 3 days

3
3
0 0

Re: [Linaro-TCWG-CI] 5 patches in gcc: 1 regression on arm

by Álvaro Begué

This test failure is pre-existing on master and is not introduced by this series. I verified that vanilla master (commit d3e7d81adc8, the baseline cited by the CI report) produces identical output to the patched build for the Egypt walk in test_egypt() — the diff is empty. The test's hardcoded expected output expects ambiguous local_info results at certain EEST→EET fall-back transitions (2003, 2005, 2007, 2009, 2010), but the current master code produces two consecutive unique EET intervals instead (a 1-hour interval followed by the long winter interval, same offset/save/abbrev). This looks like a pre-existing consequence of the merge block in _M_get_sys_info being #if 0'd out. --Álvaro. On Sun, Apr 12, 2026 at 1:40 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 armv8l-unknown-linux-gnueabihf native, after: > | 5 patches in gcc > | Patchwork URL: https://patchwork.sourceware.org/patch/132945 > | 9c1142da97d [PATCH 5/5] libstdc++: Implement zic writezone merge > optimization [PR 124854] > | 4647ebca332 [PATCH 4/5] libstdc++: Cascade wall-time saves in lazy > expansion seeding [PR 124853] > | f5a3c3c82e2 [PATCH 3/5] libstdc++: Resolve named-rule UNTIL save > adjustment [PR116110] > | e31e5de33bb [PATCH 2/5] libstdc++: Support ON-format DAY in Zone UNTIL > field [PR 124852] > | a607854b476 [PATCH 1/5] libstdc++: Fix numeric save offset on Zone > lines [PR 124851] > | ... applied on top of baseline commit: > | d3e7d81adc8 Daily bump. > > Produces 1 regression: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: std/time/time_zone/get_info_local.cc -std=gnu++20 execution test > > 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 > > 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-precommit/builds/… > The full lists of regressions and improvements as well as configure and > make commands are in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/… > The list of [ignored] baseline and flaky failures are in > * > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-precommit/builds/… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-arm-build/builds/1008… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

3 weeks, 3 days

2
1
0 0

Re: [Linaro-TCWG-CI] glibc patch #133360: 4 regressions on arm

by H.J. Lu

On Sun, Apr 19, 2026 at 9:16 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 glibc_check master-arm, after: > | glibc patch https://patchwork.sourceware.org/patch/133360 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Mon Apr 13 08:23:05 2026 +0800 > | > | [PATCH v4] 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 > | ... 36 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 0664c8e2761 localedata: Consistently use one space after 'category' > > Produces 4 regressions: > | > | regressions.sum: > | Running glibc:elf ... > | FAIL: elf/tst-thp-1-no-s-code-pde > | FAIL: elf/tst-thp-1-no-s-code-static > | FAIL: elf/tst-thp-1-pde > | FAIL: elf/tst-thp-1-static What do they report, like in elf/tst-thp-1-pde.out? What is in /sys/kernel/mm/transparent_hugepage/hpage_pmd_size? > Used configuration : > *CI config* tcwg_glibc_check master-arm > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/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-arm-precommit/build… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build… > > Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-precommit/build… > Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. -- H.J.

3 weeks, 4 days

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #133193: 3 regressions on aarch64

by Jonathan Wakely

On Fri, 17 Apr 2026 at 06:03, <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: > | gcc patch https://patchwork.sourceware.org/patch/133193 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Apr 16 15:21:49 2026 +0100 > | > | [PATCH v2] libstdc++: Add module initialization functions to the library [PR124268] > | > | This tries to ensure that the module init functions are present in > | libstdc++.so and libstdc++.a, so that users of the std and std.compat > | modules don't need to manually link to std.o and/or std.compat.o in > | ... 32 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 20230911fca Daily bump. > > Produces 3 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-prettyprinters/prettyprinters.exp ... > | FAIL: libstdc++-prettyprinters/debug.cc print redirected > | FAIL: libstdc++-prettyprinters/simple.cc print redirected > | FAIL: libstdc++-prettyprinters/simple11.cc print redirected > > 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 > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. I don't understand how these failures can possibly be caused by the patch, and I don't see them on cfarm185 (Ampere eMAG aarch64-linux-gnu, almalinux 8.10) or on any other *-*-linux-gnu targets, nor solaris. > > -----------------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-precommit/bui… > 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-precommit/bui… > The list of [ignored] baseline and flaky failures are in > * http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui… > > Current build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-precommit/bui… > Reference build : http://54.172.246.49:9090/jobs/tcwg_gcc_check--master-aarch64-build/builds/… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

3 weeks, 5 days

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-16-6952-g14cd2833b27a: 7 regressions on master-thumb_v8a_hard_eabi

by Alexandre Oliva

The test fails on arm-eabi when testing with the following settings: -mlittle-endian -mfloat-abi=hard -mcpu=cortex-a9 -mfpu=vfpv3 It only fails in the following torture option set: -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions It also fails on numerous other 32-bit targets, but it depends on how the memcpy-like loop gets vectorized and unrolled. I hope we can live with the XPASSes. On Apr 11, 2026, 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 thumb v8-a hard, after: > | commit gcc-16-6952-g14cd2833b27a > | Author: Alexandre Oliva <oliva(a)adacore.com> > | Date: Wed Jan 21 00:30:24 2026 -0300 > | > | testsuite: tolerate bogus warning in pr113026-1.c [PR113524] > | > | The bogus warning in pr113026-1.c is issued at some optimization > | levels on various 32-bit targets. > | > | ... 6 lines of the commit log omitted. > Produces 7 regressions: > | > | regressions.sum: > | Running gcc:gcc.dg/torture/dg-torture.exp ... > | XPASS: gcc.dg/torture/pr113026-1.c -O0 PR118504 (test for bogus messages, line 12) > | XPASS: gcc.dg/torture/pr113026-1.c -O1 PR118504 (test for bogus messages, line 12) > | XPASS: gcc.dg/torture/pr113026-1.c -O2 PR118504 (test for bogus messages, line 12) > | XPASS: gcc.dg/torture/pr113026-1.c -O2 -flto > | -fno-use-linker-plugin -flto-partition=none PR118504 (test for > | bogus messages, line 12) > | ... and 3 more > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb > -march=armv8-a+simd -mfpu=auto -mfloat-abi=hard > *configure and test flags:* --target arm-eabi --disable-multilib > --with-mode=thumb --with-arch=armv8-a+simd > --with-fpu=crypto-neon-fp-armv8 --with-float=hard > --target_board=-mthumb/-march=armv8-a+simd/-mfpu=auto/-mfloat-abi=hard > qemu_cpu=any > We track this bug report under > https://linaro.atlassian.net/browse/GNU-1870. 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_v8a_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_v8a_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_v8a_h… > Current build : > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_h… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_v8a_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 -- Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/ Free Software Activist FSFLA co-founder GNU Toolchain Engineer More tolerance and less prejudice are key for inclusion and diversity. Excluding neuro-others for not behaving ""normal"" is *not* inclusive!

4 weeks

2
3
0 0

Re: [Linaro-TCWG-CI] gcc-16-8401-g71033b1dfbd1: 1 regression on aarch64

by Christophe Lyon

Hi! On 4/3/26 08:06, ci_notify--- via Gcc-regression wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In aarch64 native, after: > | commit gcc-16-8401-g71033b1dfbd1 > | Author: Roger Sayle <roger(a)nextmovesoftware.com> > | Date: Wed Apr 1 23:54:50 2026 +0100 > | > | PR target/123238: VCOND_MASK regression on aarch64. > | > | This patch fixes the regression PR target/123238 on aarch64, using the > | changes to aarch64's aarch64_rtx_costs proposed by Tamar Christina. > | > | ... 38 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running gcc:gcc.target/aarch64/aarch64.exp ... > | FAIL: gcc.target/aarch64/pr123238.c scan-assembler-not not > This was fixed by Andrew in: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9c694b3ecd0eb5308e85a0eac69c4… Thanks, Christophe > 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-1868. 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 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

1 month

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-23-init-11166-g8ac9461e48e0: 1 regression 1 fix 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. 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 月 12 日 (日曜日) 17:45 宛先: contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com <contact-ci-compiler-test-suite(a)cs.jp.fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; a.bataev(a)outlook.com <a.bataev(a)outlook.com> 件名: [Linaro-TCWG-CI] llvmorg-23-init-11166-g8ac9461e48e0: 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-11166-g8ac9461e48e0 | Author: Alexey Bataev <a.bataev(a)outlook.com> | Date: Sat Apr 11 08:18:36 2026 -0400 | | [SLP] Reject 2-element vectorization when vector inst count exceeds scalar | | The LLVM cost model uses integer-valued throughput costs which cannot | represent fractional costs. For 2-element vectors, this rounding can | make vectorization appear profitable when it actually produces more | ... 15 lines of the commit log omitted. Produces 1 regression 1 fix: | | regressions.sum: | Running test-suite:Fujitsu/C/0121 ... | FAIL: test-suite :: Fujitsu/C/0121/Fujitsu-C-0121_0259.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/0640 ... | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0216.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-2210. 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/8ac9461e48e024448a2b6493b7c5b50…

1 month

1
0
0 0

LLVM Buildbot stuck

by Mehdi AMINI

Hi, Seems like this build is stuck for 3 days now: https://lab.llvm.org/buildbot/#/builders/121/builds/2250 Best, Mehdi

1 month

2
1
0 0

Potentially dodgy caching on flang-arm64-windows-msvc

by Luke Lau

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

1 month

2
1
0 0

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

by Tomasz Kaminski

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

1 month

1
0
0 0

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

by Jonathan Wakely

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

1 month, 1 week

1
0
0 0

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

by Shunsuke Watanabe (Fujitsu)

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

1 month, 2 weeks

1
0
0 0

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

by Tomasz Kaminski

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

1 month, 3 weeks

1
0
0 0

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

by Andre Vehreschild

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

1 month, 3 weeks

4
9
0 0

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

by Christophe Lyon

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

2 months

1
0
0 0

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

by Christophe Lyon

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

2 months

1
0
0 0

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

by Nathan Myers

Fixed in 2bfaa218b066.

2 months, 1 week

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain