linaro-toolchain

linaro-toolchain@lists.linaro.org

16 participants
5736 discussions

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

by Yasuyuki Ohno (Fujitsu)

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

1 month, 1 week

[Linaro-TCWG-CI] glibc-2.43.9000-304-g1cc165baed2: 1 regression on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-arm, after: | commit glibc-2.43.9000-304-g1cc165baed2 | Author: Frédéric Bérat <fberat(a)redhat.com> | Date: Wed Apr 29 13:26:38 2026 +0200 | | test: Add gconv refcount leak test for swscanf | | Add a new internal test, `tst-wcsmbs-clone-overflow`, to verify correct | gconv module reference counting. The Makefile is updated to include this | test in the `tests-internal` list and ensure it runs with generated locales. | ... 9 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:wcsmbs ... | FAIL: wcsmbs/tst-wcsmbs-clone-overflow Used configuration : *CI config* tcwg_glibc_check master-arm *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1900. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The full lists of regressions and improvements as well as configure and make commands are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… The list of [ignored] baseline and flaky failures are in * http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Current build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Reference build : http://54.172.246.49:9090/jobs/tcwg_glibc_check--master-arm-build/builds/10… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=1cc165baed20b6589ef2…

1 month, 2 weeks

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

by Laurent Alfonsi

Typo in this email : We track this bug report under https://linaro.atlassian.net/browse/GNU-1898 . Please let us know if you have a fix. On Tue, 5 May 2026 at 23:21, <ci_notify(a)linaro.org> wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please > find some details below. > > In arm-eabi cortex-m55 hard, after: > | commit gcc-17-277-gc0c911821ba > | Author: Xi Ruoyao <xry111(a)xry111.site> > | Date: Sat May 2 02:15:42 2026 +0800 > | > | testsuite: don't link top-level asm tests as PIE [PR 70150] > | > | If these tests are linked as PIE, the linker ends up creating > runtime > | text relocation and warns or errors out. > | > | ... 8 lines of the commit log omitted. > > Produces 3 regressions 3 fixes: > | > | regressions.sum: > | Running gcc:gcc.dg/lto/lto.exp ... > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=1to1 -no-pie > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=cache -no-pie > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=max -no-pie > | > | fixes.sum: > | Running gcc:gcc.dg/lto/lto.exp ... > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=1to1 > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=cache > | FAIL: gcc.dg/lto/toplevel-simple-asm-1 > c_lto_toplevel-simple-asm-1_0.o-c_lto_toplevel-simple-asm-1_1.o link, -O2 > -flto -flto-toplevel-asm-heuristics -flto-partition=max > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb > -march=armv8.1-m.main+mve.fp+fp.dp -mtune=cortex-m55 -mfloat-abi=hard > -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib > --with-mode=thumb --with-arch=armv8.1-m.main+mve.fp+fp.dp --with-float=hard > --target_board=-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto > qemu-cpu=cortex-m55 > > We track this bug report under https://linaro.atlassian.net/browse/Please > specify 'Project' and 'IssueType'.. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on > linaro-toolchain(a)lists.linaro.org mailing list. > > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways > to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h… > The full lists of regressions and improvements as well as configure and > make commands are in > * > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h… > The list of [ignored] baseline and flaky failures are in > * > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h… > > Current build : > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h… > Reference build : > http://54.172.246.49:9090/jobs/tcwg_gnu_embed_check_gcc--master-thumb_m55_h… > > Instruction to reproduce the build : > https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

1 month, 2 weeks

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

1 month, 2 weeks

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

1 month, 2 weeks

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 >

2 months

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

2 months

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.

2 months

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.

2 months

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.

2 months, 1 week

← Newer
1
2
3
4
5
6
7
...
574
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain