- linaro-toolchain - lists.linaro.org

Re: [Linaro-TCWG-CI] llvmorg-21-init-14994-g163c67ad3d1b: 41 regressions on aarch64

by Peter Klausler

That patch was reverted. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Monday, June 23, 2025 at 07:20 To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-21-init-14994-g163c67ad3d1b: 41 regressions on aarch64 External email: Use caution opening links or attachments Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O0-debug, after: | commit llvmorg-21-init-14994-g163c67ad3d1b | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Tue Jun 10 14:44:19 2025 -0700 | | [flang][runtime] Replace recursion with iterative work queue (#137727) | | Recursion, both direct and indirect, prevents accurate stack size | calculation at link time for GPU device code. Restructure these | recursive (often mutually so) routines in the Fortran runtime with new | ... 15 lines of the commit log omitted. Produces 41 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0449 ... | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0000.test | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0001.test | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0002.test | FAIL: test-suite :: Fujitsu/Fortran/0449/Fujitsu-Fortran-0449_0003.test | ... and 41 more | # "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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-1708>. 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> The full lists of regressions and improvements as well as configure and make commands are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> The list of [ignored] baseline and flaky failures are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1042…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1041…> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…<https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/163c67ad3d1bf7af6590930d8f18700…>

1 week

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-450-g0dbbc44bfd2: 2 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit glibc-2.41.9000-450-g0dbbc44bfd2 | Author: Andreas Schwab <schwab(a)suse.de> | Date: Wed Jun 18 13:17:29 2025 +0200 | | Fix termios related targets | | Move Linux-specific termios headers and tests from misc to termios subdir | and install newly added bits/termios-cbaud.h. Produces 2 regressions: | | regressions.sum: | Running gdb:gdb.base/term.exp ... | FAIL: gdb.base/term.exp: initial: info terminal | Running gdb:gdb.reverse/test_ioctl_TCSETSW.exp ... | FAIL: gdb.reverse/test_ioctl_TCSETSW.exp: handle TCSETSW Used configuration : *CI config* tcwg_gnu_native_check_gdb 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-1610. 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_native_check_gdb--master-arm-build/2049/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2049/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2049/… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2049/… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/2048/… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=0dbbc44bfd256683705c…

1 week, 3 days

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

by Sam James

Could you file a glibc bug for this please? It needs some analysis to see if it's an FP or not. There's actually a suppression for -Os already there: if (elem < table_size) { /* Compare the byte sequence but only if this is not part of a range. */ /* The compiler might warn that idx may be used uninitialized, however it will be reached iff elem < table_size which means that it was properly set in the loop above. */ DIAG_PUSH_NEEDS_COMMENT; DIAG_IGNORE_Os_NEEDS_COMMENT (8, "-Wmaybe-uninitialized"); if (! is_range # if WIDE_CHAR_VERSION && __wmemcmp (n, &wextra[1], c1) == 0 # else && memcmp (n, &extra[idx + 1], c1) == 0 # endif ) { n += c1 - 1; goto matched; } DIAG_POP_NEEDS_COMMENT;

1 week, 3 days

3
2
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-14927-g007d29e30c6e: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, As discussed in https://github.com/llvm/llvm-project/issues/141928 , this is an error of the test program Fortran/0614/0614_0005.f. Please ignore the mail, sorry. We've fixed the test internally. It will be pushd to the GitHub. > 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-21-init-14927-g007d29e30c6e > | Author: Dominik Adamski <dominik.adamski(a)amd.com> > | Date: Tue Jun 10 16:46:13 2025 +0200 > | > | [Flang] Turn on alias analysis for locally allocated objects (#143489) > | > | Previously, a bug in the MemCptOpt LLVM IR pass caused issues with > | adding alias tags for locally allocated objects for Fortran code. > | > | ... 8 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0614 ... > | FAIL: test-suite :: Fujitsu/Fortran/0614/Fujitsu-Fortran-0614_0005.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1707. 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_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… > > Full commit : https://github.com/llvm/llvm-project/commit/007d29e30c6e311501ed97b7a368521…

1 week, 4 days

1
0
0 0

[PATCH] [arm] require armv7 support for [PR120424] (was: Re: [PATCH, FYI?] [arm] [vxworks] require thumb2 for pr120424.C)

by Alexandre Oliva

On Jun 19, 2025, Alexandre Oliva <oliva(a)adacore.com> wrote: > Or maybe the requirements for this testcase should be stated as > arm_arch_v7? I'd have to add arm_arch_v7 to > check_effective_target_arm_arch_FUNC_ok et al, if there aren't reasons > why it's not there, but I'd be happy to do that, and use dg-add-options > instead of an explicit -march=armv7, like pr117675.c, if that would be > preferred. It turned out that the regression report I got from linaro was related https://linaro.atlassian.net/browse/GNU-1599 While testing a configuration with -mfloat-abi=hard, -marmv7 is rejected because it doesn't have an FPU. Requiring thumb2 wouldn't have avoided this failure, but requiring armv7 is a proper fix for both problems. (sorry it me took so long; I'm still busy busy with other fp2sp-elimination-disabled-during-lra problems affecting arm) Without stating the architecture version required by the test, test runs with options that are incompatible with the required architecture version fail, e.g. -mfloat-abi=hard. armv7 was not covered by the long list of arm variants in target-supports.exp, so add it, and use it for the effective target requirement and for the option. Tested on arm-eabi, and also on arm-vx7r2 with gcc-14. Ok to install? for gcc/testsuite/ChangeLog PR rtl-optimization/120424 * lib/target-supports.exp (arm arches): Add arm_arch_v7. * g++.target/arm/pr120424.C: Require armv7 support. Use dg-add-options arm_arch_v7 instead of explicit -march=armv7. --- gcc/testsuite/g++.target/arm/pr120424.C | 4 +++- gcc/testsuite/lib/target-supports.exp | 1 + 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.target/arm/pr120424.C b/gcc/testsuite/g++.target/arm/pr120424.C index 4d0e49013c04a..40295ac80da93 100644 --- a/gcc/testsuite/g++.target/arm/pr120424.C +++ b/gcc/testsuite/g++.target/arm/pr120424.C @@ -1,5 +1,7 @@ /* { dg-do compile } */ -/* { dg-options "-march=armv7 -O2 -fstack-clash-protection -fnon-call-exceptions" } */ +/* { dg-require-effective-target arm_arch_v7_ok } */ +/* { dg-options "-O2 -fstack-clash-protection -fnon-call-exceptions" } */ +/* { dg-add-options arm_arch_v7 } */ /* { dg-final { scan-assembler-not {#-8} } } */ /* LRA register elimination gets confused when register spilling causes arm_frame_pointer_required to switch from false to true, and diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index dfffe3adfbdd0..858fa1787f19c 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -6073,6 +6073,7 @@ foreach { armfunc armflag armdefs } { v6z_arm "-march=armv6z+fp -marm" "__ARM_ARCH_6Z__ && !__thumb__" v6z_thumb "-march=armv6z+fp -mthumb -mfloat-abi=softfp" "__ARM_ARCH_6Z__ && __thumb__" v6m "-march=armv6-m -mthumb -mfloat-abi=soft" __ARM_ARCH_6M__ + v7 "-march=armv7" __ARM_ARCH_7__ v7a "-march=armv7-a+fp" __ARM_ARCH_7A__ v7a_arm "-march=armv7-a+fp -marm" "__ARM_ARCH_7A__ && !__thumb__" v7a_fp_hard "-march=armv7-a+fp -mfpu=auto -mfloat-abi=hard" __ARM_ARCH_7A__ -- 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!

1 week, 4 days

1
0
0 0

[automated CI mails] Need help with a regression Linaro CI notified me of

by Filip Kastl

Hi all. I got an automated mail about this GCC regression related to one of my commits. https://linaro.atlassian.net/browse/GNU-1578 The mail itself mentioned only a testsuite regression. I fixed that. However, this was also linked in the mail: https://ci.linaro.org/job/tcwg_bootstrap_build--master-arm-bootstrap_profil… That looks like a different regression. As far as I can tell, `make profiledbootstrap` is failing on arm. I have only very limited access to arm machines. I tried to reproduce this on an Aarch64 machine and didn't succeed. Could you check that this regression is still present on current trunk and/or help me reproduce it? Btw the "Instructions to reproduce the build" link doesn't work for me. I get "Request is not authorized". https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Thanks, Filip Kastl

1 week, 5 days

2
2
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-434-g5cf101a85aa: 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 master-aarch64, after: | commit glibc-2.41.9000-434-g5cf101a85aa | Author: H. Peter Anvin (Intel) <hpa(a)zytor.com> | Date: Wed Jun 11 18:35:36 2025 -0700 | | linux: implement arbitrary and split speeds in termios | | Linux has supported arbitrary speeds and split speeds in the kernel | since 2008 on all platforms except Alpha (fixed in 2020), but glibc | was never updated to match. This is further complicated by POSIX uses | ... 33 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | # FAILED | # build_abe gdb: | # build_abe qemu: | # First few build errors in logs: | # 00:12:17 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/aarch64-linux-gnu/libc/usr/include/bits/termios.h:54:10: fatal error: bits/termios-cbaud.h: No such file or directory | # 00:12:17 make[4]: *** [Makefile:627: sanitizer_platform_limits_posix.lo] Error 1 | # 00:12:17 make[3]: *** [Makefile:533: all-recursive] Error 1 | # 00:12:17 make[2]: *** [Makefile:420: all] Error 2 | # 00:12:17 make[1]: *** [Makefile:12801: all-target-libsanitizer] Error 2 | # 00:12:17 make: *** [Makefile:1065: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | 5 | # build_abe gdb: | 6 | # build_abe qemu: | 7 Used configuration : *CI config* tcwg_gnu_cross_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1607. 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 * https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1133/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_build--master-aarch64-build/1133/a… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1133/a… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1132/a… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=5cf101a85aae0d703cdd…

1 week, 6 days

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-14805-g112490f06abc: 2 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This is probably a false detection by a precision error of floating-point arithmetic. Please ignore the mail. > 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-21-init-14805-g112490f06abc > | Author: Craig Topper <craig.topper(a)sifive.com> > | Date: Mon Jun 9 12:38:08 2025 -0700 > | > | [ConstantFolding] Add support for llvm.atan in constant folding. (#143416) > | > | Fixes #143360 > > Produces 2 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0360 ... > | FAIL: test-suite :: Fujitsu/Fortran/0360/Fujitsu-Fortran-0360_0269.test > | FAIL: test-suite :: Fujitsu/Fortran/0360/Fujitsu-Fortran-0360_0272.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1704. 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_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… > > Full commit : https://github.com/llvm/llvm-project/commit/112490f06abca669eb3fe158739bf75…

2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-423-gcde5caa4bb2: 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.41.9000-423-gcde5caa4bb2 | Author: Cupertino Miranda <cupertino.miranda(a)oracle.com> | Date: Mon Jun 16 12:51:53 2025 +0000 | | malloc: add testing for large tcache support | | This patch adds large tcache support tests by re-executing malloc tests | using the tunable: glibc.malloc.tcache_max=1048576 | Test names are postfixed with "largetcache". | ... 2 lines of the commit log omitted. Produces 1 regression: | | regressions.sum: | Running glibc:. ... | FAIL: lint-makefiles 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-1606. 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_glibc_check--master-arm-build/2931/artifact/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2931/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2931/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2931/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2930/artifact/… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=cde5caa4bb21d5c474b9…

2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-417-gf3c82fc1b4: 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 glibc_build master-aarch64, after: | commit glibc-2.41.9000-417-gf3c82fc1b4 | Author: Radko Krkos <krkos(a)mail.muni.cz> | Date: Sat Jun 14 11:07:40 2025 +0200 | | io: Mark lockf() __wur [BZ #32800] | | In commit 0476597b28 flock() was marked __wur in posix/unistd.h, but not | in io/fcntl.h, the declarations must match. | | ... 1 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | # First few build errors in logs: | # 00:01:42 programs/locarchive.c:641:18: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 programs/locarchive.c:653:14: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 programs/locarchive.c:660:14: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 programs/locarchive.c:679:14: error: ignoring return value of ‘lockf64’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:42 make[2]: *** [../o-iterator.mk:9: /home/tcwg-buildslave/workspace/tcwg_gnu_3/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/locale/locarchive.o] Error 1 | # 00:01:42 make[1]: *** [Makefile:484: locale/others] Error 2 | # 00:01:42 make: *** [Makefile:20: all] Error 2 | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1 Used configuration : *CI config* tcwg_glibc_build master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1605. 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 * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2952/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2952/artif… Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2952/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2950/artif… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/glibc/sh… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f3c82fc1b41261f582f5…

2 weeks, 3 days

2
1
0 0

Re: [Linaro-TCWG-CI] glibc patch #113987: 1 regression on aarch64

by H.J. Lu

On Mon, Jun 9, 2025 at 10:02 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-aarch64, after: > | glibc patch https://patchwork.sourceware.org/patch/113987 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Mon Jun 9 05:22:10 2025 +0800 > | > | [PATCH] i386: Update ___tls_get_addr to preserve vector registers > | > | Compiler generates the following instruction sequence for dynamic TLS > | access: > | > | ... 44 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 0a027674a10 x86: Avoid GLRO(dl_x86_cpu_features) > > Produces 1 regression: > | > | regressions.sum: > | Running glibc:elf ... > | FAIL: elf/tst-tls23 So, this is a run-time failure. What happens if you run it by hand? > Used configuration : > *CI config* tcwg_glibc_check master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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_glibc_check--master-aarch64-precommit/3701/a… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/a… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/a… > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-precommit/3701/a… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2930/artif… > > 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

1
0
0 0

Fwd: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed build (failure) (main)

by Cameron McInally

Hi Linaro folks, It appears my latest commit has broken your BuildBot: fatal error: file 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\llvm\include\llvm\Support\Compiler.h' has been modified since the precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' was built: size changed (was 26948, now 27102) note: please rebuild precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' I'm not sure if it's possible for me to rebuild the precompiled header myself. Any suggestions on how to proceed? Thanks in advance, Cameron ---------- Forwarded message --------- From: <llvm.buildmaster(a)lab.llvm.org> Date: Fri, Jun 6, 2025 at 6:13 PM Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed build (failure) (main) To: Cameron McInally <cameron.mcinally(a)nyu.edu>, Thurston Dang <thurston(a)google.com> Cc: <llvm.buildmaster(a)lab.llvm.org> The Buildbot has detected a new failure on builder flang-arm64-windows-msvc while building clang. Full details are available at: https://urldefense.proofpoint.com/v2/url?u=https-3A__lab.llvm.org_buildbot_… Worker for this Build: linaro-armv8-windows-msvc-01 Blamelist: Cameron McInally <cameron.mcinally(a)nyu.edu>, Thurston Dang <thurston(a)google.com> BUILD FAILED: failed build (failure) Step 5 (build-unified-tree) failure: build (failure) ... 378.972 [2600/10/4115] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/char-set.cpp.obj 380.006 [2599/10/4116] Building CXX object tools/flang/lib/Evaluate/CMakeFiles/FortranEvaluate.dir/cmake_pch.cxx.obj 380.596 [2598/10/4117] Building AArch64GenInstrInfo.inc... 381.268 [2597/10/4118] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/char-buffer.cpp.obj 382.326 [2596/10/4119] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/debug-parser.cpp.obj 382.422 [2595/10/4120] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/characters.cpp.obj 382.547 [2594/10/4121] Building AArch64GenSubtargetInfo.inc... 383.755 [2593/10/4122] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/instrumented-parser.cpp.obj 385.992 [2592/10/4123] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/message.cpp.obj 388.630 [2591/10/4124] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj FAILED: tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj ccache C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\clang-cl.exe /nologo -TP -DFLANG_INCLUDE_TESTS=1 -DGTEST_HAS_RTTI=0 -DUNICODE -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_GLIBCXX_ASSERTIONS -D_HAS_EXCEPTIONS=0 -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -D_UNICODE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/lib/Parser -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/llvm/include -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/../mlir/include -imsvcC:/Users/tcw g/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/clang/include -imsvcC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/llvm/../clang/include /DWIN32 /D_WINDOWS /Zc:inline /Zc:__cplusplus /Oi /Brepro /bigobj /permissive- -Werror=unguarded-availability-new /W4 -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -Wctad-maybe-unsupported /Gw -Wno-deprecated-copy -Wno-string-conversion -Wno-ctad-maybe-unsupported -Xclang -fno-pch-timestamp /O2 /Ob2 -std:c++17 -MD /EHs-c- /GR- -UNDEBUG /YuC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/cmake_pch.hxx /FpC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/ lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch /FIC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/cmake_pch.hxx /showIncludes /Fotools/flang/lib/Parser/CMakeFiles/FortranParser.dir/preprocessor.cpp.obj /Fdtools\flang\lib\Parser\CMakeFiles\FortranParser.dir\FortranParser.pdb -c -- C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/flang/lib/Parser/preprocessor.cpp fatal error: file 'C:\Users\tcwg\llvm-worker\flang-arm64-windows-msvc\llvm-project\llvm\include\llvm\Support\Compiler.h' has been modified since the precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' was built: size changed (was 26948, now 27102) note: please rebuild precompiled header 'C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/./cmake_pch.cxx.pch' 1 error generated. 392.025 [2591/9/4125] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/prescan.cpp.obj 393.052 [2591/8/4126] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/parsing.cpp.obj 393.434 [2591/7/4127] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/parse-tree.cpp.obj 395.861 [2591/6/4128] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/expr-parsers.cpp.obj 402.121 [2591/5/4129] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/io-parsers.cpp.obj 408.915 [2591/4/4130] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/openacc-parsers.cpp.obj 412.795 [2591/3/4131] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/executable-parsers.cpp.obj 425.616 [2591/2/4132] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/Fortran-parsers.cpp.obj 437.843 [2591/1/4133] Building CXX object tools/flang/lib/Parser/CMakeFiles/FortranParser.dir/openmp-parsers.cpp.obj ninja: build stopped: subcommand failed. Sincerely, LLVM Buildbot

3 weeks, 1 day

2
2
0 0

RE: [Linaro-TCWG-CI] llvmorg-21-init-14077-g6f64a600649a: 125 regressions on aarch64

by Eli Friedman

I guess the issue is the following: clang: ../llvm/llvm/lib/Target/AArch64/AArch64FrameLowering.cpp:2857: StackOffset llvm::AArch64FrameLowering::resolveFrameOffsetReference(const MachineFunction &, int64_t, bool, bool, Register &, bool, bool) const: Assertion `-ObjectOffset > (int64_t)AFI->getSVECalleeSavedStackSize() && "Math isn't correct for CSRs with FPAfterSVECalleeSaves"' failed. PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script. I'll try to have a patch tomorrow. Thanks, -Eli -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Saturday, June 7, 2025 10:41 PM To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com Cc: maxim.kuvyrkov(a)linaro.org; Eli Friedman <efriedma(a)quicinc.com> Subject: [Linaro-TCWG-CI] llvmorg-21-init-14077-g6f64a600649a: 125 regressions on aarch64 WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O0-debug, after: | commit llvmorg-21-init-14077-g6f64a600649a | Author: Eli Friedman <efriedma(a)quicinc.com> | Date: Mon Jun 2 18:28:23 2025 -0700 | | [AArch64] Initial compiler support for SVE unwind on Windows. (#138609) | | Most bits of this are straightforward: when we emit SVE instructions in | the prologue/epilogue, emit corresponding opcodes. | | ... 7 lines of the commit log omitted. Produces 125 regressions: | | regressions.sum: | Running test-suite:Fujitsu/C/0003 ... | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0088.test | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0090.test | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0091.test | NOEXE: test-suite :: Fujitsu/C/0003/Fujitsu-C-0003_0092.test | ... and 122 more | # "NOEXE" means : the test program cannot be compiled Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1699. 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_flang_test--main-aarch64-O0-debug-build/1023… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1023… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1023… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1023… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/1022… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… Full commit : https://github.com/llvm/llvm-project/commit/6f64a600649a95141526043b170aa42…

3 weeks, 1 day

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-1247-gbdae7824cd9: 7 regressions on arm

by Jonathan Wakely

On Fri, 6 Jun 2025 at 18:17, <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 gcc_check master-arm, after: > | commit gcc-16-1247-gbdae7824cd9 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Wed Jun 4 15:53:20 2025 +0100 > | > | libstdc++: Optimize std::counting_semaphore for futex path > | > | Rename __semaphore_base to __semaphore_impl, because it's not used as a > | base class. Replace the three identical lambda expressions with a named > | class, __semaphore_impl::_Available, which stores the most recent > | ... 27 lines of the commit log omitted. > > Produces 7 regressions: > | > | regressions.sum: > | Running g++:g++.dg/modules/modules.exp ... > | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors) > | FAIL: g++.dg/modules/xtreme-header-5_b.C -std=c++26 (test for excess errors) > | FAIL: g++.dg/modules/xtreme-header-6_b.C -std=c++26 (test for excess errors) > | FAIL: g++.dg/modules/xtreme-header-7_b.C -std=c++26 (test for excess errors) > | ... and 3 more > > Used configuration : > *CI config* tcwg_gcc_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-1598. Please let us know if you have a fix. It should be fixed at r16-1270-g7407891a3d7c17 > > 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_gcc_check--master-arm-build/3946/artifact/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3946/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3945/artifact/ar… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

3 weeks, 3 days

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-427-g86627faec10d: 11 regressions on arm

by Jonathan Wakely

On Wed, 4 Jun 2025 at 02:50, <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-arm_eabi, after: > | commit gcc-16-427-g86627faec10d > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Fri Apr 25 21:09:18 2025 +0100 > | > | libstdc++: Rewrite atomic builtin checks [PR70560] > | > | Currently the GLIBCXX_ENABLE_ATOMIC_BUILTINS macro checks for a variety > | of __atomic built-ins for bool, short and int. If all those checks pass, > | then it defines _GLIBCXX_ATOMIC_BUILTINS and uses the definitions from > | ... 80 lines of the commit log omitted. > > Produces 11 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 (test for excess errors) > | FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++26 (test for excess errors) > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 (test for excess errors) > | FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++26 (test for excess errors) > | ... and 7 more > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc master-arm_eabi > *configure and test flags:* --target arm-eabi > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1595. Please let us know if you have a fix. I've opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120567 for this. > > 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-arm_eabi-build/1… > 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-arm_eabi-build/1… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/1… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=86627faec10da53d753280501…

3 weeks, 4 days

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-1041-g2da641d0170: 5105 regressions on master-thumb_m33_hard_eabi

by H.J. Lu

On Wed, Jun 4, 2025 at 10:39 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-m33 hard, after: > | commit gcc-16-1041-g2da641d0170 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Sun Jun 1 09:29:48 2025 +0800 > | > | Move get_call_rtx_from to final.c > | > | Move get_call_rtx_from to final.c and call call_from_call_insn. > | > | PR other/120493 > | ... 8 lines of the commit log omitted. > > Produces 5105 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/arm/cmse/cmse.exp ... > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler ands\tr0, r4 > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler ands\tr1, r4 > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler ands\tr2, r4 > | UNRESOLVED: gcc.target/arm/cmse/baseline/bitfield-4.c -mcpu=unset -march=armv8-m.base -mthumb -mfloat-abi=soft -O0 scan-assembler bl\t__gnu_cmse_nonsecure_call > | ... and 5101 more > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m33 --with-float=hard --target_board=-mthumb/-march=armv8-m.main+dsp+fp/-mtune=cortex-m33/-mfloat-abi=hard/-mfpu=auto qemu-cpu=cortex-m33 > Please try this. -- H.J.

3 weeks, 4 days

2
2
0 0

[Linaro-TCWG-CI] gcc-16-1028-g9739ae9384d: 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 tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig, after: | commit gcc-16-1028-g9739ae9384d | Author: Andrew Pinski <quic_apinski(a)quicinc.com> | Date: Thu May 29 23:50:08 2025 -0700 | | Have TODO_verify_* not set by any pass | | This is a follow up to the patch set starting at https://gcc.gnu.org/pipermail/gcc-patches/2014-April/386650.html. | | Currently TODO_verify_{il,all} is set by a few passes as TODOs afterwards but | ... 32 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 30 | # First few build errors in logs: | # 00:05:59 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:05:59 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:05:59 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 scripts/gcc-plugins/gcc-common.h:177:26: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 make[3]: *** [scripts/gcc-plugins/Makefile:54: scripts/gcc-plugins/latent_entropy_plugin.so] Error 1 | # 00:06:00 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 scripts/gcc-plugins/gcc-common.h:176:25: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:00 scripts/gcc-plugins/gcc-common.h:178:27: error: ‘TODO_verify_il’ was not declared in this scope; did you mean ‘TODO_verify_flow’? | # 00:06:01 make[3]: *** [scripts/gcc-plugins/Makefile:54: scripts/gcc-plugins/stackleak_plugin.so] Error 1 | # 00:06:03 make[2]: *** [scripts/Makefile.build:461: scripts/gcc-plugins] Error 2 | | From | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 36872 | # linux build successful: | all Used configuration : tcwg_kernel/gnu-master-aarch64-mainline-allmodconfig We track this bug report under https://linaro.atlassian.net/browse/GNU-1592. 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: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allmodco… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allmodco… Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/gcc/sha1… Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9739ae9384dd7cd3bb1c7683d…

4 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-13711-ga0d699a8e686: 2 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. We'll update the test. Sorry for the noise. > 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-21-init-13711-ga0d699a8e686 > | Author: Slava Zakharin <szakharin(a)nvidia.com> > | Date: Wed May 28 17:18:04 2025 -0700 > | > | Reland "[flang] Added noalias attribute to function arguments. (#140803)" > | > | This helps to disambiguate accesses in the caller and the callee > | after LLVM inlining in some apps. I did not see any performance > | changes, but this is one step towards enabling other optimizations > | ... 14 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0122 ... > | FAIL: test-suite :: Fujitsu/Fortran/0122/Fujitsu-Fortran-0122_0045.test > | FAIL: test-suite :: Fujitsu/Fortran/0122/Fujitsu-Fortran-0122_0048.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1691. 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_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/llvm/sha… > > Full commit : https://github.com/llvm/llvm-project/commit/a0d699a8e686cba99690cf28463d145…

4 weeks, 1 day

1
0
0 0

RE: [Linaro-TCWG-CI] llvmorg-21-init-11733-g2d12d31f44ac: 3 regressions on aarch64

by Slava Zakharin

Hello, I think there was an error in bisecting these regressions. I can reproduce the same failure with commit 6dc6ca3302edadad7d4b195a05038995b84606d0, which happened before mine. Thanks, Slava -----Original Message----- From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Wednesday, May 21, 2025 9:10 PM To: ohno.yasuyuki(a)fujitsu.com; itou.tetsuya(a)fujitsu.com; t-kawashima(a)fujitsu.com Cc: Slava Zakharin <szakharin(a)nvidia.com>; maxim.kuvyrkov(a)linaro.org Subject: [Linaro-TCWG-CI] llvmorg-21-init-11733-g2d12d31f44ac: 3 regressions on aarch64 [You don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] External email: Use caution opening links or attachments 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-21-init-11733-g2d12d31f44ac | Author: Slava Zakharin <szakharin(a)nvidia.com> | Date: Mon May 12 18:33:47 2025 -0700 | | [flang] Propagate contiguous attribute through HLFIR. (#138797) | | This change allows marking more designators producing an opaque | box with 'contiguous' attribute, e.g. like in test1 case | in flang/test/HLFIR/propagate-contiguous-attribute.fir. | ... 5 lines of the commit log omitted. Produces 3 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0105 ... | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0089.test | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0204.test | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0205.test | # "NOEXE" means : the test program cannot be compiled Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1686. 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_flang_test--main-aarch64-Ofast-sve_vls-lto-l… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/2d12d31f44acac54d7b2858624cb8a1…

1 month

3
3
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-12714-gd36028120a6e: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This regression is caused by a latent bug in the loop-interchange. I've confirmed https://github.com/llvm/llvm-project/pull/140709 fixes the bug. We'll wait for merge of https://github.com/llvm/llvm-project/pull/140709. You don't need to investigate this failure. Thanks. > 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-21-init-12714-gd36028120a6e > | Author: Sebastian Pop <spop(a)nvidia.com> > | Date: Wed May 21 08:27:39 2025 -0500 > | > | [flang] add -floop-interchange and enable it with opt levels (#140182) > | > | Enable the use of -floop-interchange from the flang driver. > | Enable in flang LLVM's loop interchange at levels -O2, -O3, -Ofast, and -Os. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0347 ... > | FAIL: test-suite :: Fujitsu/Fortran/0347/Fujitsu-Fortran-0347_0240.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1687. 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_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/d36028120a6ef6346bfaafe82d4d1a2…

1 month

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-12430-g70501ed2f0f9: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. Sorry for the noise. > 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-21-init-12430-g70501ed2f0f9 > | Author: Sam Tebbs <samuel.tebbs(a)arm.com> > | Date: Mon May 19 13:27:17 2025 +0100 > | > | [LoopVectorizer] Prune VFs based on plan register pressure (#132190) > | > | This PR moves the register usage checking to after the plans are > | created, so that any recipes that optimise register usage (such as > | partial reductions) can be properly costed and not have their VF pruned > | ... 3 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0340 ... > | FAIL: test-suite :: Fujitsu/Fortran/0340/Fujitsu-Fortran-0340_0076.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1684. 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_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/70501ed2f0f9dc06baffa7ee124845e…

1 month

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-11722-gcf3242f3b0f6: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, This failure is a false detection caused by a floating-point precision error in fast-math. Please ignore the mail. Sorry for the noise. > 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-21-init-11722-gcf3242f3b0f6 > | Author: Luke Lau <luke(a)igalia.com> > | Date: Tue May 13 02:11:55 2025 +0300 > | > | [InstCombine] Pull shuffles out of binops with splatted ops (#137948) > | > | Given a binary op on splatted vector and a splatted constant, > | InstCombine will normally pull the shuffle out in > | `InstCombinerImpl::foldVectorBinop`: > | ... 50 lines of the commit log omitted. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0639 ... > | FAIL: test-suite :: Fujitsu/Fortran/0639/Fujitsu-Fortran-0639_0140.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1681. 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_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/cf3242f3b0f6eec47786426777f6e0b…

1 month

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-372-g064cac730f8: 18 regressions on aarch64

by Sam James

See PR119930, PR120098, PR120101, PR120099.

1 month, 3 weeks

1
0
0 0

Windows builder issues

by Aaron Ballman

It looks like https://lab.llvm.org/buildbot/#/workers/149 is having problems: FAILED: bin/clang.exe C:\WINDOWS\system32\cmd.exe /C "cd . && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E vs_link_exe --intdir=tools\clang\tools\driver\CMakeFiles\clang.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests -- C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\lld-link.exe /nologo @CMakeFiles\clang.rsp /out:bin\clang.exe /implib:lib\clang.lib /pdb:bin\clang.pdb /version:0.0 /machine:ARM64 /STACK:10000000 /INCREMENTAL:NO /subsystem:console && C:\WINDOWS\system32\cmd.exe /C "cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang++.exe && cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang-cl.exe && cd /D C:\Users\tcwg\llvm-worker\clang-arm64-windows-msvc\build\tools\clang\tools\driver && C:\Users\tcwg\scoop\apps\cmake\3.30.1\bin\cmake.exe -E copy C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/bin/clang.exe C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/build/./bin/clang-cpp.exe"" LINK: command "C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\lld-link.exe /nologo @CMakeFiles\clang.rsp /out:bin\clang.exe /implib:lib\clang.lib /pdb:bin\clang.pdb /version:0.0 /machine:ARM64 /STACK:10000000 /INCREMENTAL:NO /subsystem:console /MANIFEST:EMBED,ID=1" failed (exit code 1) with the following output: lld-link: error: failed to write output 'bin\clang.exe': permission denied Any chance you can look into it? Thanks! ~Aaron

1 month, 3 weeks

2
2
0 0

Re: [Linaro-TCWG-CI] glibc patch #111247: 90 regressions on arm

by Stefan Liebler

Hi, For this V2-patch, I got the same "Operation not permitted" errors as for the V1 one: https://lists.linaro.org/archives/list/linaro-toolchain@lists.linaro.org/th… @Adhemerval: have you had a look? The only non-s390x changes of my patch are in: elf/Makefile elf/tst-glibc-hwcaps-cache.script => There the libmarkermod6 libraries are added. As I don't have an arm, I've checked on x86_64, that the testcase elf/tst-glibc-hwcaps-cache.c contains the libmarkermod6.so files in glibc-hwcaps/z13-z17 directories by adding a "ldconfig -p" to the test. Any idea why those "Operation not permitted" regressions hits my patch, but no others? Bye, Stefan On 4/30/25 20:19, 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/111247 > | Author: Stefan Liebler <stli(a)linux.ibm.com> > | Date: Tue Apr 29 13:28:58 2025 +0200 > | > | [PATCH v2] S390: Add new s390 platform z17. > | > | Hi, > | need a V2: stfle_bits on stack in init_cpu_features_no_tunables() needs to be > | zeroed before usage. If there is no more feedback, I will commit this patch shortly. > | ... 41 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 84977600dac math: Fix UB on sinpif (BZ 32925) > > Produces 90 regressions: > | > | regressions.sum: > | Running glibc:debug ... > | FAIL: debug/tst-fortify-syslog > | Running glibc:dirent ... > | FAIL: dirent/tst-readdir-long > | FAIL: dirent/tst-readdir-zero-inode > | ... and 99 more > > 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 > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3574/artif… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2743/artifact/… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

1 month, 4 weeks

2
1
0 0

Re: [Linaro-TCWG-CI] gdb patch #111028: 2 regressions on arm

by Tom de Vries

On 4/30/25 06:18, 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 gdb_check master-arm, after: > | gdb patch https://patchwork.sourceware.org/patch/111028 > | Author: Tom de Vries <tdevries(a)suse.de> > | Date: Fri Apr 25 17:13:32 2025 +0200 > | > | [PATCH v2] [gdb/testsuite] Simplify gdb.tui/tui-layout-asm.exp > | > | On x86_64-cygwin, with test-case gdb.tui/tui-layout-asm.exp I run into: > | ... > | WARNING: The following failure is probably due to the TUI window > | ... 49 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 48d0ac705c4 Handle base type without DW_AT_byte_size > > Produces 2 regressions: > | > | regressions.sum: > | Running gdb:gdb.python/py-missing-objfile.exp ... > | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_exec_var > | FAIL: gdb.python/py-missing-objfile.exp: initial sanity check: whatis global_lib_var > The FAILs are obviously unrelated to the patch which modifies a different test-case. But anyway, this a know PR ( https://sourceware.org/bugzilla/show_bug.cgi?id=32445 ). I've just committed a fix. Thanks, - Tom > Used configuration : > *CI config* tcwg_gdb_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 > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > > Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/4439/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/2666/artifact/ar… > > 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

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-16-142-g01e5ef3e8b9: 2 regressions on arm

by Tomasz Kaminski

Hi, I have just pushed the following fix on trunk, that fixes a similar issue for 32bit x86_64. https://gcc.gnu.org/cgit/gcc/commit/?id=2ca5725e104d432317a44ad45183a4f555d… Please let me know if the build failure is addressed. Regards, Tomasz On Wed, Apr 30, 2025 at 5:14 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 gcc_check master-arm, after: > | commit gcc-16-142-g01e5ef3e8b9 > | Author: Tomasz Kamiński <tkaminsk(a)redhat.com> > | Date: Wed Apr 23 13:17:09 2025 +0200 > | > | libstdc++: Minimalize temporary allocations when width is > specified [PR109162] > | > | When width parameter is specified for formatting range, tuple or > escaped > | presentation of string, we used to format characters to temporary > string, > | and write produce sequence padded according to the spec. However, > once the > | ... 53 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: std/format/debug.cc -std=gnu++23 execution test > | FAIL: std/format/debug.cc -std=gnu++26 execution test > > Used configuration : > *CI config* tcwg_gcc_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-1571. 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_gcc_check--master-arm-build/3771/artifact/ar… > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3771/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3771/artifact/ar… > > Current build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3771/artifact/ar… > Reference build : > https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3770/artifact/ar… > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=01e5ef3e8b91288f5d387a277…

2 months

1
0
0 0

Re: [Linaro-TCWG-CI] gdb-16-branchpoint-1244-g5ea1eec52f4: 4 regressions 4 fixes on arm

by Tom de Vries

On 4/26/25 22:38, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In master-arm, after: > | commit gdb-16-branchpoint-1244-g5ea1eec52f4 > | Author: Tom de Vries <tdevries(a)suse.de> > | Date: Wed Apr 9 08:59:42 2025 +0200 > | > | [gdb/tdep] Handle ldaex and stlex in {thumb,arm}_deal_with_atomic_sequence_raw > | > | The Linaro CI reported a regression [1] in test-case > | gdb.base/step-over-syscall.exp due to commit 674d4856730 ("[gdb/testsuite] Fix > | gdb.base/step-over-syscall.exp with glibc 2.41"). > | ... 100 lines of the commit log omitted. > > Produces 4 regressions 4 fixes: > | > | regressions.sum: > | Running gdb:gdb.base/step-over-syscall.exp ... > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: check_pc_after_cross_syscall: single step over fork final pc > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: pc after stepi matches insn addr after syscall > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: check_pc_after_cross_syscall: single step over fork final pc > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: pc after stepi matches insn addr after syscall > | > | fixes.sum: > | Running gdb:gdb.base/step-over-syscall.exp ... > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: continue to syscall insn fork (the program exited) > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: find syscall insn in fork > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: single step over fork (the program is no longer running) > | FAIL: gdb.base/step-over-syscall.exp: fork: displaced=off: break on syscall insn > Hi, I've looked at this, and AFAICT this is PR32817 ( https://sourceware.org/bugzilla/show_bug.cgi?id=32817 ). This is unrelated to the mentioned commit. Thanks, - Tom > Used configuration : > *CI config* tcwg_gnu_native_check_gdb 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-1570. 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_native_check_gdb--master-arm-build/1993/… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/… > > Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1993/… > Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-arm-build/1991/… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gdb/sh… > > Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5ea1eec52f47f…

2 months

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-275-ge04afb7177: 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 master-aarch64, after: | commit glibc-2.41.9000-275-ge04afb7177 | Author: H. Peter Anvin <hpa(a)zytor.com> | Date: Fri Apr 25 07:30:59 2025 +0200 | | linux/termio: remove <termio.h> and struct termio | | The <termio.h> interface is absolutely ancient: it was obsoleted by | <termios.h> already in the first version of POSIX (1988) and thus | predates the very first version of Linux. Unfortunately, some constant | ... 15 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | # FAILED | # build_abe gdb: | # build_abe qemu: | # First few build errors in logs: | # 00:08:58 /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:489:31: error: invalid application of ‘sizeof’ to incomplete type ‘__sanitizer::termio’ | # 00:08:58 make[4]: *** [Makefile:627: sanitizer_platform_limits_posix.lo] Error 1 | # 00:08:58 make[3]: *** [Makefile:533: all-recursive] Error 1 | # 00:08:58 make[2]: *** [Makefile:420: all] Error 2 | # 00:08:58 make[1]: *** [Makefile:12800: all-target-libsanitizer] Error 2 | # 00:08:58 make: *** [Makefile:1064: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe stage1 --: | 2 | # build_abe linux: | 3 | # build_abe glibc: | 4 | # build_abe stage2 --: | 5 | # build_abe gdb: | 6 | # build_abe qemu: | 7 Used configuration : *CI config* tcwg_gnu_cross_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1569. 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 * https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1084/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_build--master-aarch64-build/1084/a… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1084/a… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-aarch64-build/1083/a… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=e04afb71771710cdc602…

2 months

2
1
0 0

Adjust 'libgomp.c++/target-exceptions-pr118794-1.C' for 'targetm.arm_eabi_unwinder' [PR118794] (was: [Linaro-TCWG-CI] gcc-15-9463-gaa3e72f9430: 2 regressions on arm)

by Thomas Schwinge

Hi! On 2025-04-17T18:15:50+0000, ci_notify--- via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In bootstrap_check master-arm-check_bootstrap, after: > | commit gcc-15-9463-gaa3e72f9430 > | Author: Thomas Schwinge <tschwinge(a)baylibre.com> > | Date: Thu Mar 27 23:06:37 2025 +0100 > | > | Add test cases for exception handling constructs in dead code for GCN, nvptx target and OpenMP 'target' offloading [PR118794] > | > | PR target/118794 > | gcc/testsuite/ > | * g++.target/gcn/exceptions-pr118794-1.C: New. > | ... 7 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libgomp:libgomp.c++/c++.exp ... > | FAIL: libgomp.c++/target-exceptions-pr118794-1.C scan-tree-dump-times optimized "gimple_call <__builtin_eh_pointer, " 1 > | FAIL: libgomp.c++/target-exceptions-pr118794-1.C scan-tree-dump-times optimized "gimple_call <__builtin_unwind_resume, " 1 Ah, sorry for that. This is due to 'targetm.arm_eabi_unwinder', as per: gcc/config/arm/arm.cc:#define TARGET_ARM_EABI_UNWINDER true gcc/config/c6x/c6x.cc:#define TARGET_ARM_EABI_UNWINDER true ..., which for ARM is conditional to '#if ARM_UNWIND_INFO' (defined in 'gcc/config/arm/bpabi.h', used for various GCC configurations), and for C6x unconditional. This gets us: --- target-exceptions-pr118794-1.C.269t.optimized +++ target-exceptions-pr118794-1.C.270t.optimized [...] __attribute__((omp declare target)) void f () [...] gimple_call <__dt_comp , NULL, &c> - gimple_call <__builtin_eh_pointer, _7, 2> - gimple_call <__builtin_unwind_resume, NULL, _7> + gimple_call <__builtin_cxa_end_cleanup, NULL> } [...] There doesn't appear to be an effective-target keyword for 'targetm.arm_eabi_unwinder' specifically, do we need to add one? Or, other test cases appear to use effective-target 'arm_eabi' to disambiguate the two variants; is that the right thing to use here, too? (..., plus 'tic6x-*-*' in this case?) OK to push the attached "Adjust 'libgomp.c++/target-exceptions-pr118794-1.C' for 'targetm.arm_eabi_unwinder' [PR118794]"? (Could Arm/C6x maintainers please test this for me?) Grüße Thomas > Used configuration : > *CI config* tcwg_bootstrap_check master-arm-check_bootstrap > *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1562. 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_bootstrap_check--master-arm-check_bootstrap-… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > > Current build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > Reference build : https://ci.linaro.org/job/tcwg_bootstrap_check--master-arm-check_bootstrap-… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=aa3e72f943032e5f074b2bd2f…

2 months, 1 week

2
1
0 0

Re: [Linaro-TCWG-CI] glibc patch #110503: 90 regressions on arm

by Stefan Liebler

Hi, I've looked into tests.log.1.xz and there are plenty of "Operation not permitted" errors. I don't think that this has something to do with my patch? Can you please check on your side, if there was a change/issue on the build system? Bye, Stefan On 4/16/25 13:32, 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/110503 > | Author: Stefan Liebler <stli(a)linux.ibm.com> > | Date: Tue Apr 15 16:52:17 2025 +0200 > | > | [PATCH] S390: Add new s390 platform z17. > | > | The glibc-hwcaps subdirectories are extended by "z17". Libraries are loaded if > | the z17 facility bits are active: > | - Miscellaneous-instruction-extensions facility 4 > | ... 35 lines of the commit log omitted. > | ... applied on top of baseline commit: > | ceeffd970c5 aarch64: Add back non-temporal load/stores from oryon-1's memset > > Produces 90 regressions: > | > | regressions.sum: > | Running glibc:debug ... > | FAIL: debug/tst-fortify-syslog > | Running glibc:dirent ... > | FAIL: dirent/tst-readdir-long > | FAIL: dirent/tst-readdir-zero-inode > | ... and 99 more > > 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 > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artif… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artif… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artif… > > Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-precommit/3528/artif… > Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2681/artifact/… > > 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, 2 weeks

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-8019-g0ae9bb96d5af: 86 regressions 14 fixes on aarch64

by Peter Klausler

The HTML links in your mail aren’t usable in my locked-down corporate e-mail environment. If you could just send me a list of the names of the 83 failing Fujitsu tests, I’ll look at them immediately. (The initial ones that are quoted in the mail are working now with llvm-project/main, but I’d like to check the others.) From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Monday, April 14, 2025 at 20:36 To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-21-init-8019-g0ae9bb96d5af: 86 regressions 14 fixes on aarch64 External email: Use caution opening links or attachments Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-21-init-8019-g0ae9bb96d5af | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Wed Apr 9 12:30:33 2025 -0700 | | [flang][OpenMP] Fix regression in !$\ continuation (#134756) | | A recent patch that obviated the need to use -fopenmp when using the | compiler to preprocess in -E mode broke a case of Fortran line | continuation when using OpenMP conditional compilation lines (!$\) when | ... 1 lines of the commit log omitted. Produces 86 regressions 14 fixes: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/1008 ... | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0001.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0002.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0006.test | NOEXE: test-suite :: Fujitsu/Fortran/1008/Fujitsu-Fortran-1008_0008.test | ... and 84 more | # "NOEXE" means : the test program cannot be compiled | | fixes.sum: | Running test-suite:Fujitsu/Fortran/0213 ... | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0029.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0023.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0018.test | NOEXE: test-suite :: Fujitsu/Fortran/0213/Fujitsu-Fortran-0213_0024.test | ... and 10 more | # "NOEXE" means : the test program cannot be compiled Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-1665>. 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> The full lists of regressions and improvements as well as configure and make commands are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> The list of [ignored] baseline and flaky failures are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-us.li…<https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/0ae9bb96d5af47a2426596dbd0c35e3…>

2 months, 2 weeks

2
2
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-7332-g3295970d846b: 1 regression on aarch64

by Takahiro Kawashima (Fujitsu)

Dear contributor, This FAIL is a floating-point precision error. Please ignore this mail. We'll update the test. > 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-21-init-7332-g3295970d846b > | Author: Iris <0.0(a)owo.li> > | Date: Thu Apr 3 14:34:09 2025 +0800 > | > | [ConstantFolding] Add support for `sinh` and `cosh` intrinsics in constant folding (#132671) > | > | Closes #132503. > > Produces 1 regression: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0360 ... > | FAIL: test-suite :: Fujitsu/Fortran/0360/Fujitsu-Fortran-0360_0286.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1653. 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_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/3295970d846b0d820b863f9eeac559b…

2 months, 3 weeks

1
0
0 0

Re: [Patch, fortran] PR85836: Implement the F2018 reduce intrinsic

by Christophe Lyon

Hi! On Wed, 19 Mar 2025 at 19:22, Paul Richard Thomas <paul.richard.thomas(a)gmail.com> wrote: > > Hi Andre, > > Thanks for the review - I'll act on the points that you raised. > > The Linaro people reported a failure in reduce_1.f90 execution, which I believe is due to incorrect casting of 'dim' and a wrong specification of its kind. I am waiting to hear back from them as to whether or not I have fixed the failure. > Sorry I notice this message just today, so it's a bit outdated... I've looked at bugzilla, so I've noticed that the are proper bug reports about this now (and I've just checked, the problem is still present on arm). When you say you are "waiting to hear back from them as to whether or not I have fixed the failure", did you contact us directly? (I'm trying to understand if we missed your message, or how we could improve communication). Thanks, Christophe > Cheers > > Paul > > > On Wed, 19 Mar 2025 at 12:39, Andre Vehreschild <vehre(a)gmx.de> wrote: >> >> Hi Paul, >> >> I took a look at your patch and think I found some improvements needed. In >> >> +bool >> +gfc_check_reduce (gfc_expr *array, gfc_expr *operation, gfc_expr *dim, >> + gfc_expr *mask, gfc_expr *identity, gfc_expr *ordered) >> +{ >> >> ... >> >> + if (formal->sym->attr.allocatable || formal->sym->attr.allocatable >> + || formal->sym->attr.pointer || formal->sym->attr.pointer >> + || formal->sym->attr.optional || formal->sym->attr.optional >> + || formal->sym->ts.type == BT_CLASS || formal->sym->ts.type == BT_CLASS) >> + { >> + gfc_error ("Each argument of OPERATION at %L shall be a scalar, " >> + "non-allocatable, non-pointer, non-polymorphic and " >> + "nonoptional", &operation->where); >> + return false; >> + } >> >> The if is only looking at the first formal argument. The right-hand sides >> of the || miss a ->next-> to look at the second formal argument, right? >> >> May be you also want to extend the tests!? >> >> Without having looked at it, but can't you extract the whole block of >> >> + if (array->ts.type == BT_CHARACTER) >> + { >> + unsigned long actual_size, formal_size1, formal_size2, result_size; >> ... >> + return false; >> + } >> + } >> >> and share it with the checks for co_reduce? I figure way to many DRY principle >> violations are in gfortran. So when we can start this, why not do it? And a >> call to a routine, like check_char_arg_conformance() speaks way better, then >> having to read all that code ;-) >> >> In gfc_resolve_reduce() identity and ordered are marked as UNUSED. Should these >> not a least be resolved? >> >> Please run contrib/check_GNU_style on your patch. It reports several issues >> (haven't look into their validity). >> >> In the Changelog: >> >> - (gfc_check_rename): Add prototype for intrinsic with 6 arguments. >> + * gfortran.h: Add prototype for intrinsic with 6 arguments. >> >> s/discription/description/ >> >> I also encountered that nit with the executable stack when working in >> OpenCoarrays, but haven't had time (or desire) to look into it. I will put >> myself into CC of the pr Jerry mentioned. >> >> Besides the mentions above, this looks good to me. >> >> Thanks for the patch and >> >> Regards, >> Andre >> >> >> >> On Sun, 16 Mar 2025 17:26:55 +0000 >> Paul Richard Thomas <paul.richard.thomas(a)gmail.com> wrote: >> >> > Hi All, >> > >> > This version of the REDUCE intrinsic patch has evolved somewhat since the >> > posting on 2nd March. The most important changes are to the wrapper >> > function and the addition of two testsuite entries. >> > >> > The wrapper function now effects: >> > subroutine wrapper (a, b, c) >> > type_of_ARRAY, intent(inout) :: a, c >> > type_of_ARRAY, intent(inout), optional :: b >> > if (present (b)) then >> > c = OPERATION (a,b ) >> > else >> > c = a >> > end if >> > end subroutine >> > >> > The reason for wrapping OPERATION in a subroutine is to allow pointer >> > arithmetic to be used throughout in the library function. The only thing >> > that needs to be known about the type and kind of ARRAY is the element >> > size. The second branch in the wrapper allows deep copies to be done in the >> > library function, such that derived types with allocatable components do >> > not leak memory. This is needed at the final step of the algorithm to copy >> > the result from each iteration to the result and then nullify it. >> > >> > This is undoubtedly a bit heavy going for intrinsic types and so, one day >> > soon I will possibly do a bit of M4ery. That said, the present version >> > works for all types of ARRAY and I worry a bit about how much this >> > intrinsic will be used. Thoughts? >> > >> > A slight niggle is the linker error that comes up if compiled without any >> > optimization: >> > /usr/bin/ld: warning: /tmp/cc9cx9Rw.o: requires executable stack (because >> > the .note.GNU-stack section is executable) >> > I think that this is unlikely to present a security issue, however, since >> > it disappears at -O1, I went through each of the options triggered by -O1 >> > but couldn't make it go away. Does anybody know why this is? >> > >> > Regtests OK with FC41/x86_64 - OK for mainline? >> > >> > Regards >> > >> > Paul >> >> >> -- >> Andre Vehreschild * Email: vehre ad gmx dot de

2 months, 3 weeks

2
4
0 0

Re: [Linaro-TCWG-CI] gdb patch #109371: 5 regressions on aarch64

by Martin Simmons

>>>>> On Sun, 30 Mar 2025 23:58:18 +0000 (UTC), ci notify said: > ... > In gdb_check master-aarch64, after: > | gdb patch https://patchwork.sourceware.org/patch/109371 > ... > Used configuration : > *CI config* tcwg_gdb_check master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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_gdb_check--master-aarch64-precommit/4627/art… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/art… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/art… > > Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/art… > Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/2461/artifac… In https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/4627/art… it appears that the "info set" test started at line 1159 and failed with FAIL: gdb.base/default.exp: info set (timeout) at line 1533. Then a few more tests failed with timeout and finally over 100 tests failed with no obvious reason. Was this caused by a problem on the CI machine?

2 months, 4 weeks

3
3
0 0

Re: [Linaro-TCWG-CI] 5 patches in binutils: Success on arm

by Jens Remus

Hello! On 03.04.2025 14:32, ci_notify(a)linaro.org wrote: > Our automatic CI has detected problems related to your patch(es). Please find some details below. Could you please help me understand what the detected problem(s) are? The mail subject suggests that everything may actually be fine? > In binutils_build master-arm, after: > | 5 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/109718 > | cde90675110 [PATCH 5/8] s390: Represent FP without RA saved in SFrame > | fa5be46ad1a [PATCH 4/8] s390: Represent FP/RA saved in register in SFrame > | b029a0bbe60 [PATCH 3/8] s390: Initial support to generate .sframe from CFI directives in assembler > | d40f1518ae8 [PATCH 2/8] s390: Explicitly list linker dump tests > | 45da7966615 [PATCH 1/8] sframe: Ignore section padding when converting endianness > | ... applied on top of baseline commit: > | abf215a338f ld/testsuite/ld-pe: Escape dots in regular expressions My series consists of 8 patches. Could it be that they appeared in Patchworks in a bad order, e.g. due to in what order my company's mail server delivered them to the list, and this now confuses the CI? https://patchwork.sourceware.org/project/binutils/list/?series=45805 > Produces Success: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe binutils: > | 1 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe binutils: > | 1 The results appear to be unchanged to me. > Used configuration : > *CI config* tcwg_binutils_build 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 > * https://ci.linaro.org/job/tcwg_binutils_build--master-arm-precommit/3765/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_binutils_build--master-arm-precommit/3765/ar… > > Current build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-precommit/3765/ar… > Reference build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/2375/artifa… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files. Thanks and regards, Jens -- Jens Remus Linux on Z Development (D3303) +49-7031-16-1128 Office jremus(a)de.ibm.com IBM IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294 IBM Data Privacy Statement: https://www.ibm.com/privacy/

2 months, 4 weeks

2
1
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-229-g7f163bd2106: 1 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit glibc-2.41.9000-229-g7f163bd2106 | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Tue Apr 1 12:44:26 2025 +0000 | | Update syscall lists for Linux 6.14 | | Linux 6.14 has no new syscalls. Update the version number in | syscall-names.list to reflect that it is still current for 6.14. | | ... 1 lines of the commit log omitted. Produces 1 regressions: | | regressions.sum: | Running glibc:misc ... | FAIL: misc/tst-glibcsyscalls Used configuration : *CI config* tcwg_gnu_native_check_glibc 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-1557. 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_native_check_glibc--master-arm-build/112… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/112… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/112… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/112… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/111… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=7f163bd2106f96e2925e…

2 months, 4 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-9030-g78e0cf06c81: 5 regressions 4 improvements on master-thumb_m33_hard_eabi

by Sam James

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 arm-eabi cortex-m33 hard, after: > | commit gcc-15-9030-g78e0cf06c81 > | Author: Sam James <sam(a)gentoo.org> > | Date: Sat Mar 29 21:09:25 2025 +0000 > | > | testsuite: arm: fixup more dg-final syntax > | > | ... as Richard E mentioned on the ML. Followup to r15-8956-ge90d6c2639c392. > | > | gcc/testsuite/ChangeLog: > | ... 2 lines of the commit log omitted. > > Produces 5 regressions 4 improvements: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times sxth\\tr[0-9]+,r[0-9]+ 2 > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times vcvt\\.f32\\.s32\\ts[0-9]+,s[0-9]+ 2 > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times vcvt\\.s32\\.f32\\ts[0-9]+,s[0-9]+ 2 > | FAIL: gcc.target/arm/short-vfp-1.c scan-assembler-times vmov\\tr[0-9]+,s[0-9]+ 2 > | ... and 1 more This one may need an ARM person to take a look at. (The issue was latent, and the test wasn't being run fully before.)

3 months

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-6480-g529c5b71c608: 3 regressions 2 improvements on aarch64

by Kajetan Puchalski

Hi, I'm not familiar with the test suite in question, does it seem related to the test issue addressed in https://github.com/llvm/llvm-project/pull/133128? Or does it seem like it's caused by enabling the slp-vectorizer pass in the O3 pipeline where it was not enabled previously? ________________________________ Von: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Gesendet: Freitag, März 28, 2025 1:21:30 AM An: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: Kajetan Puchalski <Kajetan.Puchalski(a)arm.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> Betreff: [Linaro-TCWG-CI] llvmorg-21-init-6480-g529c5b71c608: 3 regressions 2 improvements on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-21-init-6480-g529c5b71c608 | Author: Kajetan Puchalski <kajetan.puchalski(a)arm.com> | Date: Wed Mar 26 16:10:35 2025 +0000 | | [flang] Add -f[no-]slp-vectorize flags (#132801) | | Add -f[no-]slp-vectorize to the flang driver. | Add corresponding -fvectorize-slp to the flang frontend. | | ... 6 lines of the commit log omitted. Produces 3 regressions 2 improvements: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0105 ... | NOEXE: test-suite :: Fujitsu/Fortran/0105/Fujitsu-Fortran-0105_0223.test | Running test-suite:Fujitsu/Fortran/0631 ... | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0051.test | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0054.test | # "NOEXE" means : the test program cannot be compiled | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one | | improvements.sum: | Running test-suite:Fujitsu/Fortran/0347 ... | FAIL: test-suite :: Fujitsu/Fortran/0347/Fujitsu-Fortran-0347_0083.test | Running test-suite:Fujitsu/Fortran/0675 ... | FAIL: test-suite :: Fujitsu/Fortran/0675/Fujitsu-Fortran-0675_0315.test | # "NOEXE" means : the test program cannot be compiled | # "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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1644. 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_flang_test--main-aarch64-O3-neoverse_v1-sve_… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/529c5b71c608c18141432e6fd0ae892… 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.

3 months

3
4
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-6604-gc6406c8dba33: 1 regressions on aarch64

by Takahiro Kawashima (Fujitsu)

Dear contributor, This FAIL is a floating-point precision error caused by the -ffast-math flag. Please ignore this mail. We'll update the test. > 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-21-init-6604-gc6406c8dba33 > | Author: David Green <david.green(a)arm.com> > | Date: Thu Mar 27 17:25:02 2025 +0000 > | > | [AArch64] Add getVectorInstrCost Codesize costs handling. (#130946) > | > | We have a lot of missing Codesize costs for vector operations. This > | patch starts things off by adding codesize costs for getVectorInstrCost, > | returning a single cost instead of the VectorInsertExtractBaseCost > | ... 2 lines of the commit log omitted. > > Produces 1 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0351 ... > | FAIL: test-suite :: Fujitsu/Fortran/0351/Fujitsu-Fortran-0351_0105.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1647. 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_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/c6406c8dba33d4cf8495257f70f52a2…

3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #109240: 2 regressions 2 improvements on arm

by Christophe Lyon

On Sat, 29 Mar 2025 at 22:07, <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 gcc_check master-arm, after: > | gcc patch https://patchwork.sourceware.org/patch/109240 > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Wed Mar 26 17:19:11 2025 +0000 > | > | [PATCH] arm: don't vectorize fmaxf() unless unsafe math opts are enabled > | > | This test has presumably been failing since vectorization was enabled > | at -O2. I suspect part of the reason this wasn't picked up sooner is > | that the test is a hybrid execution/scan-assembler test and the > | ... 29 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 876a521a198 OpenMP: Fix declaration in append-args-interop.c test case > > Produces 2 regressions 2 improvements: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vmaxnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vminnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | > | improvements.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vmaxnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vminnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > Hi Richard, I suspect the scripts were confused because there were some bugs in dg-directives during a few days, leading to random Tcl errors. You've committed your patch by now anyway, just mentioning in case you are confused. Thanks and sorry for the inconvenience, Christophe > Used configuration : > *CI config* tcwg_gcc_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 > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3611/artifact/ar… > > 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 months

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-15-8965-gb631ff45f23: 2 regressions 2 improvements on arm

by Richard Earnshaw (lists)

On 29/03/2025 23:18, 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-arm, after: > | commit gcc-15-8965-gb631ff45f23 > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Wed Mar 26 15:56:18 2025 +0000 > | > | arm: don't vectorize fmaxf() unless unsafe math opts are enabled > | > | This test has presumably been failing since vectorization was enabled > | at -O2. I suspect part of the reason this wasn't picked up sooner is > | that the test is a hybrid execution/scan-assembler test and the > | ... 29 lines of the commit log omitted. > > Produces 2 regressions 2 improvements: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vmaxnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vminnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1 > | Fixed with r15-9064-gf30e180194bfbc R. > | improvements.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vminnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vmaxnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1 > > 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-1553. 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/1998/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/1998/a… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a… > > Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a… > Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1997/a… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b631ff45f231db55b28b4c92c…

3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-8956-ge90d6c2639c: 8 regressions on aarch64

by Sam James

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 gcc_check master-aarch64, after: > | commit gcc-15-8956-ge90d6c2639c > | Author: Sam James <sam(a)gentoo.org> > | Date: Thu Mar 27 00:21:43 2025 +0000 > | > | testsuite: more (mostly cosmetic) dg- whitespace fixes > | > | Some of these are harmless but still inconsistent (and asking for trouble > | given it may give people the wrong idea about similar "style"). > | > | ... 9 lines of the commit log omitted. > > Produces 8 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/aarch64/aarch64.exp ... > | ERROR: tcl error code NONE > | ERROR: tcl error sourcing gcc.target/aarch64/aarch64.exp. > | UNRESOLVED: testcase gcc.target/aarch64/aarch64.exp' aborted due to Tcl error > | ERROR: unmatched open brace in list > | ... and 5 more Should be fixed with r15-8981-g176c7a2f751e04, thanks!

3 months

2
1
0 0

[committed] gcc/testsuite/g++.dg/gomp/append-args-8.C: Fix scan-dump-tree (was: [Linaro-TCWG-CI] gcc-15-8972-g7e286b56545: 3 regressions on aarch64)

by Tobias Burnus

The tree dump had bogus tailing numbers: interop.[0-9]+3, interop.[0-9]+2 This happened to work with x86-64 (-m32, -m64) but not with aarch64. I committed inr15-9033-ge0886d8ad4c519 the obvious fix: remove the 3 and 2 after the '+' Tobias ci_notify(a)linaro.org wrote: > In gcc_check master-aarch64, after: > | commit gcc-15-8972-g7e286b56545 > > We track this bug report underhttps://linaro.atlassian.net/browse/GNU-1554. Please let us know if you have a fix.

3 months

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-6198-g9694844d7e36: Failure on aarch64

by Nathan Chancellor

On Fri, Mar 28, 2025 at 03:28:46PM +0000, 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 tcwg_kernel/llvm-master-aarch64-stable-allmodconfig, after: > | commit llvmorg-21-init-6198-g9694844d7e36 > | Author: Henry Jiang <h243jian(a)uwaterloo.ca> > | Date: Mon Mar 24 09:49:31 2025 -0400 > | > | Reland "[Transforms] LoopIdiomRecognize recognize strlen and wcslen #108985" (#132572) > | > | Reland https://github.com/llvm/llvm-project/pull/108985 > | > | Extend `LoopIdiomRecognize` to find and replace loops of the form > | ... 12 lines of the commit log omitted. Thanks a lot for the report. I sent the third version of the patchset that should resolve this issue this morning so I hope it will be moved on soon: https://lore.kernel.org/20250328-string-add-wcslen-for-llvm-opt-v3-0-a180b4… Cheers, Nathan

3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-8947-g8ed2d5d219e: 5 regressions on master-thumb_m23_soft_eabi

by Christophe Lyon

Hi, On Fri, 28 Mar 2025 at 14:24, <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-m23 soft, after: > | commit gcc-15-8947-g8ed2d5d219e > | Author: Jørgen Kvalsvik <j(a)lambda.is> > | Date: Tue Jun 4 14:13:22 2024 +0200 > | > | Add prime path coverage to gcc/gcov > | > | This patch adds prime path coverage to gcc/gcov. First, a quick > | introduction to path coverage, before I explain a bit on the pieces of > | the patch. > | ... 404 lines of the commit log omitted. > > Produces 5 regressions: > | > | regressions.sum: > | Running g++:g++.dg/gcov/gcov.exp ... > | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++17 gcov failed: spawn failed > | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++26 gcov failed: spawn failed > | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++98 gcov failed: spawn failed > | Running gcc:gcc.misc-tests/gcov.exp ... > | ... and 2 more > I've given a quick look at the logs, and gcov-22.C says: spawn -ignore SIGHUP /home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/bin/gcov --prime-paths gcov-22.C FAIL: g++.dg/gcov/gcov-22.C -std=gnu++98 gcov failed: spawn failed I believe that rather than "dg-compile", it should use "dg-do run { target native }" like almost all other gcov tests? For the other errors: FAIL: gcc.misc-tests/gcov-31.c (test for excess errors) FAIL: gcc.misc-tests/gcov-32.c (test for excess errors) the log actually says: /gcov-31.c:12:8: error: unknown type name 'sigjmp_buf'; did you mean 'jmp_buf'? /gcov-31.c: In function 'run_pending_traps': /gcov-31.c:22:5: error: implicit declaration of function '__sigsetjmp' [-Wimplicit-function-declaration] /gcov-32.c:6:8: error: unknown type name 'sigjmp_buf'; did you mean 'jmp_buf'? /gcov-32.c:21:19: error: passing argument 1 of 'setjmp' makes pointer from integer without a cast [-Wint-conversion] I haven't looked further, but does this indicate a dependency on glibc? (this target "arm-none-eabi" uses newlib) Thanks, Christophe > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1551. 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_m23_soft_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_m23_soft_e… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=8ed2d5d219e999aee42015a0d…

3 months

2
2
0 0

[Linaro-TCWG-CI] binutils-2_41-release-6320-ga8373e160b7: 1 regressions 1 improvements 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 binutils_check master-arm, after: | commit binutils-2_41-release-6320-ga8373e160b7 | Author: Jens Remus <jremus(a)linux.ibm.com> | Date: Fri Mar 21 15:29:03 2025 +0100 | | ld: Correct test pr19719 naming mix-up | | The suffix "defined/undefined" in the ld test pr19719 name specifies | whether weak fun() is defined or undefined is mixed up. | | ... 19 lines of the commit log omitted. Produces 1 regressions 1 improvements: | | regressions.sum: | Running ld:ld-elf/shared.exp ... | XPASS: Run pr19719 fun defined | | improvements.sum: | Running ld:ld-elf/shared.exp ... | XPASS: Run pr19719 fun undefined Used configuration : *CI config* tcwg_binutils_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-1549. 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_binutils_check--master-arm-build/2383/artifa… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/2383/artifa… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/2383/artifa… Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/2383/artifa… Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-arm-build/2381/artifa… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=a8373e160b791…

3 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-8904-ge200f53a555: 2 regressions on aarch64

by Jonathan Wakely

On Wed, 26 Mar 2025 at 00:55, <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 gcc_check master-aarch64, after: > | commit gcc-15-8904-ge200f53a555 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Tue Mar 25 13:24:08 2025 +0000 > | > | libstdc++: Optimize std::vector construction from input iterators [PR108487] > | > | LWG 3291 make std::ranges::iota_view's iterator have input_iterator_tag > | as its iterator_category, even though it satisfies the C++20 > | std::forward_iterator concept. This means that the traditional > | ... 41 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/tree-ssa/initlist-opt1.C -std=c++26 scan-tree-dump gimple "_M_range_initialize<const char\\* const\\*>" > | FAIL: g++.dg/tree-ssa/initlist-opt2.C -std=c++26 scan-tree-dump gimple "_M_range_initialize<const char\\* const\\*>" > > Used configuration : > *CI config* tcwg_gcc_check master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1548. Please let us know if you have a fix. I have a fix: --- a/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C +++ b/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C @@ -4,7 +4,7 @@ // { dg-skip-if "requires hosted libstdc++ for string" { ! hostedlib } } // Test that we do range-initialization from const char *. -// { dg-final { scan-tree-dump {_M_range_initialize<const char\* const\*>} "gimple" } } +// { dg-final { scan-tree-dump {_M_range_initialize_n<const char\* const\*} "gimple" } } // { dg-final { scan-tree-dump {static const char.*72} "gimple" } } #include <string> > > 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_gcc_check--master-aarch64-build/3491/artifac… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3490/artifac… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e200f53a5556516ec831e6b7a…

3 months

1
2
0 0

Re: [Linaro-TCWG-CI] gcc patch #109136: Failure on aarch64

by Christophe Lyon

Hi, We had a "disk full" issue on that machine, sorry for the false alarm. We can manually retrigger the build if you wish? Thanks, Christophe On Tue, 25 Mar 2025 at 12:22, <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 gcc_build master-aarch64, after: > | gcc patch https://patchwork.sourceware.org/patch/109136 > | Author: Hu, Lin1 <lin1.hu(a)intel.com> > | Date: Tue Mar 25 15:44:51 2025 +0800 > | > | [PATCH] i386: Add "s_" as Saturation for AVX10.2 Converting Intrinsics. > | > | Hi, all > | > | This patch aims to add "s_" after 'cvt' represent saturation. > | ... 21 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | 1 > > Used configuration : > *CI config* tcwg_gcc_build master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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 > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17123/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17123/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17123/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac… > > 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 months, 1 week

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #109150: Failure on aarch64

by Christophe Lyon

Hi, We had a "disk full" issue on that machine, sorry for the false alarm. We can manually retrigger the build if you wish? Thanks, Christophe On Tue, 25 Mar 2025 at 12:10, <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 simplebootstrap_build master-aarch64-bootstrap, after: > | gcc patch https://patchwork.sourceware.org/patch/109150 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Tue Mar 25 10:24:01 2025 +0000 > | > | [committed] libstdc++: Cast -1 to size_t in <format> [PR119429] > | > | This avoids a runtime error from Clang's annoying -fsanitize=integer > | (even though it's not undefined and behaves correctly). > | > | ... 5 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 4d1b1969566 libstdc++: Fix handling of common cpp20-only ranges for flat sets [PR119415] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | 1 > > Used configuration : > *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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 > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > 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 months, 1 week

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #109141: Failure on aarch64

by Christophe Lyon

Hi, We had a "disk full" issue on that machine, sorry for the false alarm. We can manually retrigger the build if you wish? Thanks, Christophe On Tue, 25 Mar 2025 at 12:24, <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 gcc_build master-aarch64, after: > | gcc patch https://patchwork.sourceware.org/patch/109141 > | Author: Tobias Burnus <tburnus(a)baylibre.com> > | Date: Tue Mar 25 10:32:08 2025 +0100 > | > | [Patch] omp-general.cc: Remove 'if' around call to always 'true' returning function [PR118627] > | > | I intent to commit this a bit later today as obvious, > | unless there are comments. > | > | ... 35 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | 1 > > Used configuration : > *CI config* tcwg_gcc_build master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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 > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac… > > 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 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #109137: Failure on aarch64

by Christophe Lyon

Hi, We had a "disk full" issue on that machine, sorry for the false alarm. We can manually retrigger the build if you wish? Thanks, Christophe On Tue, 25 Mar 2025 at 12:22, <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 gcc_build master-aarch64, after: > | gcc patch https://patchwork.sourceware.org/patch/109137 > | Author: Sam James <sam(a)gentoo.org> > | Date: Tue Mar 25 07:54:09 2025 +0000 > | > | [PATCH] testsuite: add testcase for recent alias fix > | > | r15-7961-gdc47161c1f32c3 fixes a typo in ao_compare::compare_ao_refs > | but there wasn't a testcase available at the time. Now there is. > | > | ... 8 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | 1 > > Used configuration : > *CI config* tcwg_gcc_build master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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 > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac… > > 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 months, 1 week

1
0
0 0

Request to update Clang in libc++ pre-commit CI

by Mark de Wever

Hi, Clang 20 has been released and per libc++ policy we want to remove support for Clang 18. While testing a patch to remove Clang 18 support [1] I noticed the ARM buildbots you maintain failed [2] since they use Clang 18. Would it be possible to update these bots to Clang 20 or Clang 19? [1] https://github.com/llvm/llvm-project/pull/130142 [2] https://buildkite.com/llvm-project/libcxx-ci/builds/41081 Kind regards, Mark

3 months, 1 week

2
3
0 0

https://github.com/llvm/llvm-project/pull/131921

by Louis Dionne

Hi, We have encountered a CI failure on a libc++ CI bot owned by this list. I am seeking assistance to help debug the issue since it's a bit difficult to do without having access to that platform. This is time sensitive for us, since the patch fixes a real issue we encountered and we'd like to get it fixed in the LLVM 20 release. See https://github.com/llvm/llvm-project/pull/131921#issuecomment-2737539434 for more details. Thanks, Louis

3 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-8649-g1d2257dc850: 1 regressions on arm

by Richard Earnshaw (lists)

On 21/03/2025 20:36, 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 gcc_check master-arm, after: > | commit gcc-15-8649-g1d2257dc850 > | Author: Richard Earnshaw <rearnsha(a)arm.com> > | Date: Fri Mar 21 15:20:03 2025 +0000 > | > | arm: testsuite: make unaligned-memcpy-*.c executable tests [PR91614] > | > | These tests have been looking for a very specific instruction sequence > | which has the tendency to be fairly unstable as a result. But what is > | more interesting is that the the tests must not contain instructions > | ... 22 lines of the commit log omitted. > > Produces 1 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/arm/arm.exp ... > | FAIL: gcc.target/arm/unaligned-memcpy-4.c scan-assembler-not unaligned Should be fixed now. The scanner was matching 'unaligned' in a .file directive containing the test name. R. > > Used configuration : > *CI config* tcwg_gcc_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-1545. 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_gcc_check--master-arm-build/3580/artifact/ar… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3579/artifact/ar… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… > > Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=1d2257dc850d088f6d9267b46…

3 months, 1 week

2
1
0 0

[Linaro-TCWG-CI] gcc-15-8650-g94fa9f4d27b: 6 regressions on arm

by Paul Richard Thomas

Hello there, You had previously warned me of the problem with the pre-commit patch, from which I was able to identify the problem. Unfortunately, I screwed up by only correcting the cast of 'dim' in three out of four places. Hans-Peter Nilsson has put it right and I believe that the regression will disappear. Thanks for your help on this. Paul

3 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-8035-g7ee31bc9276: 2 regressions on master-thumb_m23_soft_eabi

by Jonathan Wakely

On Sun, 16 Mar 2025 at 13:16, <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-m23 soft, after: > | commit gcc-15-8035-g7ee31bc9276 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Mar 13 13:34:55 2025 +0000 > | > | libstdc++: Implement <stdbit.h> for C++26 (P3370R1) > | > | This is the first part of the P3370R1 proposal just approved by the > | committee in Wrocław. This adds C++ equivalents of the functions added > | to C23 by WG14 N3022. > | ... 16 lines of the commit log omitted. > > Produces 2 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors) > | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to produce executable > > Used configuration : > *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto > *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33 > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1543. Please let us know if you have a fix. All the errors are of the form: error: 'ULLONG_MAX' was not declared in this scope but the test includes <limits.h>. So this target doesn't support long long? Or just doesn't define ULLONG_MAX?

3 months, 1 week

2
5
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-4020-gf01e760c0836: 6235 regressions on aarch64

by Ricardo Jesus

Hi, Sorry for this issue, I've reverted this in: https://github.com/llvm/llvm-project/commit/21610e3ecc8bc727f99047e544186b3… Before I start digging into it further, could you please let me know what hardware is used to run these tests? I just thought I'd double-check that the requested -msve-vector-bits=256 does match the hardware SVE length. Thanks very much, Ricardo On 3/7/25 09:03, ci_notify(a)linaro.org wrote: > [You 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_vls-lto-lld, after: > | commit llvmorg-21-init-4020-gf01e760c0836 > | Author: Ricardo Jesus <rjj(a)nvidia.com> > | Date: Thu Mar 6 09:27:07 2025 +0000 > | > | [AArch64][SVE] Improve fixed-length addressing modes. (#129732) > | > | When compiling VLS SVE, the compiler often replaces VL-based offsets > | with immediate-based ones. This leads to a mismatch in the allowed > | addressing modes due to SVE loads/stores generally expecting immediate > | ... 29 lines of the commit log omitted. > > Produces 6235 regressions: > | > | regressions.sum: > | Running test-suite:Fujitsu/C/0000 ... > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0003.test > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0004.test > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0008.test > | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0009.test > | ... and 6513 more > | # "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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1592 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_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/>> > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…>> > Full commit : https://github.com/llvm/llvm-project/commit/f01e760c08365426de95f02dc2c2dc6…>

3 months, 2 weeks

2
6
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-173-g997f49fbadf: 1 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-aarch64, after: | commit glibc-2.41.9000-173-g997f49fbadf | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Mon Mar 17 19:08:22 2025 +0000 | | elf: Fix tst-origin make rules | | Add tests-special before include Rules and compile liborigin.os with | MODULE_NAME set to testsuite instead of libc. Produces 1 regressions: | | regressions.sum: | Running glibc:. ... | FAIL: lint-makefiles Used configuration : *CI config* tcwg_glibc_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1544. 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_glibc_check--master-aarch64-build/2594/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2594/artif… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2594/artif… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2594/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2592/artif… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=997f49fbadf892136c77…

3 months, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-168-g9b646f5dc93: 3 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-arm, after: | commit glibc-2.41.9000-168-g9b646f5dc93 | Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org> | Date: Tue Feb 18 15:58:16 2025 -0500 | | elf: Canonicalize $\ORIGIN in an explicit ld.so invocation [BZ 25263] | | When an executable is invoked directly, we calculate $\ORIGIN by calling | readlink on /proc/self/exe, which the Linux kernel resolves to the | target of any symlinks. However, if an executable is run through ld.so, | ... 24 lines of the commit log omitted. Produces 3 regressions: | | regressions.sum: | Running glibc:elf ... | UNRESOLVED: elf/tst-origin | Running glibc:malloc ... | FAIL: malloc/tst-mallocfork2 | FAIL: malloc/tst-mallocfork3 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-1540. 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_glibc_check--master-arm-build/2551/artifact/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2551/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2551/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2551/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2550/artifact/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=9b646f5dc933dfa019f2…

3 months, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] gcc-15-8025-g7dae3f64c069: 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 tcwg_kernel/gnu-master-aarch64-lts-defconfig, after: | commit gcc-15-8025-g7dae3f64c069 | Author: Richard Sandiford <richard.sandiford(a)arm.com> | Date: Thu Mar 13 12:03:04 2025 +0000 | | match.pd: Fold ((X >> C1) & C2) * (1 << C1) | | Using a combination of rules, we were able to fold | | ((X >> C1) & C2) * (1 << C1) --> X & (C2 << C1) | ... 22 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 8743 | | From | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 10059 | # linux build successful: | all | # linux boot successful: | boot Used configuration : tcwg_kernel/gnu-master-aarch64-lts-defconfig We track this bug report under https://linaro.atlassian.net/browse/GNU-1539. 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: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh… Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=7dae3f64c069b942b9abd768f…

3 months, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-149-g77261698b4e: 8 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-aarch64, after: | commit glibc-2.41.9000-149-g77261698b4e | Author: Joseph Myers <josmyers(a)redhat.com> | Date: Fri Mar 7 19:15:26 2025 +0000 | | Implement C23 rsqrt | | C23 adds various <math.h> function families originally defined in TS | 18661-4. Add the rsqrt functions (1/sqrt(x)). The test inputs are | taken from those for sqrt. | ... 2 lines of the commit log omitted. Produces 8 regressions: | | regressions.sum: | Running glibc:math ... | FAIL: math/test-double-rsqrt | FAIL: math/test-float-rsqrt | FAIL: math/test-float128-rsqrt | FAIL: math/test-float32-rsqrt | ... and 4 more Used configuration : *CI config* tcwg_glibc_check master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1533. 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_glibc_check--master-aarch64-build/2559/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2559/artif… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2559/artif… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2559/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-aarch64-build/2557/artif… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=77261698b4e938020a1b…

3 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-7765-g3866ca796d5: 8 regressions on master-thumb_m7_hard_eabi

by Jonathan Wakely

On Sun, 2 Mar 2025 at 02:42, <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-m7 hard, after: > | commit gcc-15-7765-g3866ca796d5 > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Thu Feb 27 13:27:17 2025 +0000 > | > | libstdc++: Fix ranges::move and ranges::move_backward to use iter_move [PR105609] > | > | The ranges::move and ranges::move_backward algorithms are supposed to > | use ranges::iter_move(iter) instead of std::move(*iter), which matters > | for an iterator type with an iter_move overload findable by ADL. > | ... 16 lines of the commit log omitted. > > Produces 8 regressions: > | > | regressions.sum: > | Running libstdc++:libstdc++-dg/conformance.exp ... > | FAIL: 25_algorithms/move/constrained.cc -std=gnu++20 (test for excess errors) > | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++20 compilation failed to produce executable > | FAIL: 25_algorithms/move/constrained.cc -std=gnu++26 (test for excess errors) > | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++26 compilation failed to produce executable > | ... and 4 more It looks like thumb has some unusual linking requirements that I'm not familiar with, so undefined functions (which are never actually called in the test) cause linker errors: /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6): undefined reference to `pr105609::iter_move(pr105609::I const&)' /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: (_ZN8pr1056099iter_moveERKNS_1IE): Unknown destination type (ARM/Thumb) in /tmp/ccqKQGzN.o /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6): dangerous relocation: unsupported relocation /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc): undefined reference to `pr105609::I::operator++()' /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: (_ZN8pr1056091IppEv): Unknown destination type (ARM/Thumb) in /tmp/ccqKQGzN.o /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc): dangerous relocation: unsupported relocation /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16): undefined reference to `pr105609::I::operator==(pr105609::I) const' /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld: (_ZNK8pr1056091IeqES0_): Unknown destination type (ARM/Thumb) in /tmp/ccqKQGzN.o /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16): dangerous relocation: unsupported relocation I think I should be able to workaround this.

3 months, 3 weeks

2
5
0 0

Re: [Linaro-TCWG-CI] gcc-15-7853-gde231924b73: 1 regressions on aarch64

by Christophe Lyon

On Thu, 6 Mar 2025 at 23:55, Giuseppe D'Angelo via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote: > > On 06/03/2025 20:29, ci_notify(a)linaro.org wrote: > > Dear contributor, > > > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > This has been fixed on trunk by r15-7863-gd2b022e38a778d. > Indeed I can see the test now passes. Thanks, Christophe > Thank you, > -- > Giuseppe D'Angelo

3 months, 3 weeks

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-5934-gb8189cf9e40: 3 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit binutils-2_41-release-5934-gb8189cf9e40 | Author: Richard Allen <rsaxvc(a)gmail.com> | Date: Sun Feb 16 16:50:05 2025 -0600 | | gprof: only process line numbers for intersection of vmas and histograms | | Some programs like RTOS firmware may have a large number of symbols. | | By loading the histograms before loading symbols, we can look up | ... 5 lines of the commit log omitted. Produces 3 regressions: | | regressions.sum: | Running glibc:gmon ... | FAIL: gmon/tst-gmon-gprof | FAIL: gmon/tst-gmon-pie-gprof | FAIL: gmon/tst-gmon-static-gprof Used configuration : *CI config* tcwg_gnu_native_check_glibc 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-1527. 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_native_check_glibc--master-arm-build/107… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/107… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/107… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/107… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_glibc--master-arm-build/107… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=b8189cf9e40bd…

3 months, 4 weeks

1
0
0 0

Fwd: [Linaro-TCWG-CI] gcc patch #107213: Failure on aarch64

by Jan Dubiec

Hello, I have recived the email quoted below. I wonder how my patch could have caused an issue when the only file it touches is related to H8/300 target, not ARM. As far as I can see in the logs you are not building an H8/300 toolchain. Best regards, /J.D. PS. I am not subscribed so please CC me. -------- Forwarded Message -------- Subject: [Linaro-TCWG-CI] gcc patch #107213: Failure on aarch64 Date: Fri, 28 Feb 2025 02:06:28 +0000 (UTC) From: ci_notify(a)linaro.org Reply-To: linaro-toolchain(a)lists.linaro.org To: jdx(a)o2.pl Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In simplebootstrap_build master-aarch64-bootstrap, after: | gcc patch https://patchwork.sourceware.org/patch/107213 | Author: Jan Dubiec <jdx(a)o2.pl> | Date: Thu Feb 27 22:42:20 2025 +0100 | | [PATCH] H8/300: PR target/109189 Silence -Wformat warnings on Windows | | This patch fixes annoying -Wformat warnings when gcc is built | on Windows/MinGW64. Instead of %ld it uses HOST_WIDE_INT_PRINT_DEC | macro, just like many other targets do. | ... 12 lines of the commit log omitted. | ... applied on top of baseline commit: | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030] Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe bootstrap: | # FAILED | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe bootstrap: | 1 Used configuration : *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu 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 * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.

4 months

2
2
0 0

Re: [Linaro-TCWG-CI] gcc-15-7709-gc2ece13931d: 1 regressions 10 improvements on aarch64

by Iain Buclaw

Excerpts from ci_notify(a)linaro.org's message of Februar 27, 2025 7:38 pm: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In master-aarch64, after: > | commit gcc-15-7709-gc2ece13931d > | Author: Iain Buclaw <ibuclaw(a)gdcproject.org> > | Date: Tue Feb 25 21:01:23 2025 +0100 > | > | libphobos: Generate test files for phobos testsuite > | > | Extracts all public unittests from libphobos/src and emits them as > | standalone tests in the testsuite using the tests_extractor script. > | > | ... 132 lines of the commit log omitted. > > Produces 1 regressions 10 improvements: > | > | regressions.sum: > | Running libphobos:libphobos.phobos/phobos.exp ... > | FAIL: libphobos.phobos/std_math_hardware.d execution test > | > | improvements.sum: > | Running libphobos:libphobos.phobos/shared/phobos-shared.exp ... > | FAIL: libphobos.phobos/shared/std/format/internal/floats.d execution test > | ... and 10 more > This just a test that was already failing, it's been renamed from std/math/hardware.d to std_math_hardware.d in the logs. Iain.

4 months

2
1
0 0

Re: [Linaro-TCWG-CI] gcc patch #107194: Failure on aarch64

by Christophe Lyon

Hi, Sorry for this spurious notification, it seems we had a "disk full" issue on the build machine. You can ignore this error message. Christophe On Fri, 28 Feb 2025 at 03:12, <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 simplebootstrap_build master-aarch64-bootstrap, after: > | gcc patch https://patchwork.sourceware.org/patch/107194 > | Author: Vladimir Makarov <vmakarov(a)redhat.com> > | Date: Thu Feb 27 13:43:37 2025 -0500 > | > | [pushed][PR118940][LRA]: Add a test > | > | The following patch adds a test for > | > | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118940 > | ... 17 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | 1 > > Used configuration : > *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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 > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

4 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #107213: Failure on aarch64

by Christophe Lyon

Hi, Sorry for this spurious notification, it seems we had a "disk full" issue on the build machine. You can ignore this error message. Christophe On Fri, 28 Feb 2025 at 03:06, <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 simplebootstrap_build master-aarch64-bootstrap, after: > | gcc patch https://patchwork.sourceware.org/patch/107213 > | Author: Jan Dubiec <jdx(a)o2.pl> > | Date: Thu Feb 27 22:42:20 2025 +0100 > | > | [PATCH] H8/300: PR target/109189 Silence -Wformat warnings on Windows > | > | This patch fixes annoying -Wformat warnings when gcc is built > | on Windows/MinGW64. Instead of %ld it uses HOST_WIDE_INT_PRINT_DEC > | macro, just like many other targets do. > | ... 12 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe bootstrap: > | 1 > > Used configuration : > *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > 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 > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

4 months

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #107058: Failure on arm

by Jakub Jelinek

On Tue, Feb 25, 2025 at 03:13:10PM +0000, ci_notify(a)linaro.org wrote: > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_build master-arm, after: > | gcc patch https://patchwork.sourceware.org/patch/107058 > | Author: Jakub Jelinek <jakub(a)redhat.com> > | Date: Tue Feb 25 13:31:29 2025 +0100 > | > | [PATCH] simplify-rtx: Fix up simplify_logical_relational_operation [PR119002] > | > | Hi! > | > | The following testcase is miscompiled on powerpc64le-linux starting with > | ... 45 lines of the commit log omitted. > | ... applied on top of baseline commit: > | af73228fdb2 Fortran: Fix detection of descriptor arrays in coarray [PR107635] > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | # First few build errors in logs: > | # 00:07:45 /home/tcwg-build/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/libstdc++-v3/src/c++17/floating_to_chars.cc:1306:3: internal compiler error: in reverse_condition, at jump.cc:536 > | # 00:07:46 make[5]: *** [Makefile:587: floating_to_chars.lo] Error 1 > | # 00:07:46 make[4]: *** [Makefile:797: all-recursive] Error 1 > | # 00:07:46 make[3]: *** [Makefile:577: all-recursive] Error 1 > | # 00:07:46 make[2]: *** [Makefile:502: all] Error 2 > | # 00:07:46 make[1]: *** [Makefile:12256: all-target-libstdc++-v3] Error 2 > | # 00:07:46 make: *** [Makefile:1062: all] Error 2 Wonder how is that possible, the patch uses REVERSE_CONDITION on GT and that is handled by both reverse_condition and reverse_condition_maybe_unordered. Can I ask for preprocessed source + cc1plus command line + what -march= etc. options one needs if it is just implied by configure, so that I can have a look in a cross-compiler? I really don't have access to 32-bit arm anymore. Jakub

4 months

2
1
0 0

Fw: [Linaro-TCWG-CI] gcc patch #106762: Failure on aarch64

by James K. Lowden

Hello, I seem to have begun receiving CI/CD patch notifications from ci_notify(a)linaro.org. I don't understand them, and they might be premature. I don't want to ignore them, though, if they do matter. I am supplying a 100,000 line patch, roughly, to add a COBOL front-end to gcc. As of now, there is no libgcobol or gcc/cobol directory in the master branch. The supplied patch came most recently in 14 "easy pieces". To be applied successfully, the patches to the Python scripts that create those directories must be applied first. The URLs at the end of the mail come up 404. I suppose they are ephemeral. I haven't been able to look at a complete log to understand the basis of the report. The mail says to ask here, so here I be. Please advise. I'm not subscribed to this list. Thanks, --jkl Begin forwarded message: Date: Wed, 19 Feb 2025 15:10:38 +0000 (UTC) From: ci_notify(a)linaro.org To: jklowden(a)schemamania.org Subject: [Linaro-TCWG-CI] gcc patch #106762: Failure on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In gcc_build master-aarch64, after: | gcc patch https://patchwork.sourceware.org/patch/106762 | Author: James K. Lowden <jklowden(a)schemamania.org> | Date: Tue Feb 18 18:37:13 2025 -0500 | | [PATCH] COBOL v3: 3/14 80K bld: config and build machinery | | From f89a50238de62b73d9fc44ee7226461650ab119d Tue 18 Feb 2025 04:19:10 PM EST | From: "James K. Lowden" <jklowden(a)symas.com> | Date: Tue 18 Feb 2025 04:19:10 PM EST | ... 27 lines of the commit log omitted. | ... applied on top of baseline commit: | 427386042f0 LoongArch: Use normal RTL pattern instead of UNSPEC for {x,}vsr{a,l}ri instructions Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe gcc: | # FAILED | # First few build errors in logs: | # 00:03:17 make[1]: *** [Makefile:4720: all-gcc] Error 2 | # 00:03:17 make: *** [Makefile:1063: all] Error 2 | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe gcc: | 1 Used configuration : *CI config* tcwg_gcc_build master-aarch64 *configure and test flags:* 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_gcc_build--master-aarch64-precommit/16368/ar… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar… Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/16368/ar… Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3164/artifac… Warning: we do not enable maintainer-mode nor automatically update generated files, which may lead to failures if the patch modifies the master files.

4 months, 1 week

3
4
0 0

[Linaro-TCWG-CI] glibc-2.41.9000-97-gad9c4c53611: 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 glibc_build master-aarch64, after: | commit glibc-2.41.9000-97-gad9c4c53611 | Author: Carlos O'Donell <carlos(a)redhat.com> | Date: Thu Feb 13 14:27:55 2025 -0500 | | manual: Document setlogmask as MT-safe. | | setlogmask(3) was made MT-safe in glibc-2.33 with the fix for | bug 26100. | | ... 1 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | # First few build errors in logs: | # 00:04:01 make[2]: *** [Makefile:90: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/manual/stamp-summary] Error 1 | # 00:04:01 make[1]: *** [Makefile:470: info] Error 2 | # 00:04:01 make: *** [Makefile:20: info] Error 2 | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1 Used configuration : *CI config* tcwg_glibc_build master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1515. 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_glibc_build--master-aarch64-build/2500/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2500/artif… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2500/artif… Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2500/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2497/artif… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=ad9c4c536115ba38be3e…

4 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] 2 patches in gcc: Failure on arm

by H.J. Lu

On Thu, Feb 13, 2025 at 9:03 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 gcc_build master-arm, after: > | 2 patches in gcc > | Patchwork URL: https://patchwork.sourceware.org/patch/106412 > | de53b4c527f [PATCH 2/2] x86: Fold sibcall targets into jump table > | 54322404f4b [PATCH 1/2] x86: Add a pass to fold tail call > | ... applied on top of baseline commit: > | 2f33fa09aab Daily bump. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | # FAILED > | # First few build errors in logs: > | # 00:05:34 make[2]: *** [Makefile:512: _mulsc3.o] Error 1 This is an arm bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118866 > | # 00:05:34 make[1]: *** [Makefile:14340: all-target-libgcc] Error 2 > | # 00:05:34 make: *** [Makefile:1062: all] Error 2 > | > | From > | # reset_artifacts: > | -10 > | # true: > | 0 > | # build_abe gcc: > | 1 > > Used configuration : > *CI config* tcwg_gcc_build master-arm > *configure and test flags:* --target arm-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 > * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa… > > Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-precommit/16438/artifa… > Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-arm-build/3189/artifact/ar… > > 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.

4 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] glibc patch #106352: Failure on aarch64

by H.J. Lu

On Wed, Feb 12, 2025 at 1:17 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. Which version of GCC is your IC using? My patch raises the minimum GCC version to 12.1. > In glibc_build master-aarch64, after: > | glibc patch https://patchwork.sourceware.org/patch/106352 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Wed Feb 12 12:53:09 2025 +0800 > | > | [PATCH] Raise the minimum GCC version to 12.1 [BZ #32539] > | > | For all Linux distros with glibc 2.40 which I can find, GCC 14.2 is used > | to compile glibc 2.40: > | > | ... 52 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 392261a2b6 hurd: Replace char foo[1024] with string_t > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # init_abe_sysroot: > | 0 > | # build_abe glibc -- --disable install: > | # FAILED > | > | From > | # reset_artifacts: > | -10 > | # init_abe_sysroot: > | 0 > | # build_abe glibc -- --disable install: > | 1 > > Used configuration : > *CI config* tcwg_glibc_build master-aarch64 > *configure and test flags:* --target aarch64-linux-gnu > > 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_glibc_build--master-aarch64-precommit/3634/a… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/a… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/a… > > Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-precommit/3634/a… > Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2468/artif… > > 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.

4 months, 2 weeks

2
3
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-262-gcff0a460ae86: Failure on arm

by Nathan Chancellor

On Sun, Feb 02, 2025 at 10:30:18AM +0000, 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 tcwg_kernel/llvm-master-arm-stable-allyesconfig, after: > | commit llvmorg-21-init-262-gcff0a460ae86 > | Author: Bill Wendling <morbo(a)google.com> > | Date: Thu Jan 30 15:36:13 2025 -0800 > | > | [Clang][counted_by] Refactor __builtin_dynamic_object_size on FAMs (#122198) > | > | Refactoring of how __builtin_dynamic_object_size() is calculated for > | flexible array members (in preparation for adding support for the > | 'counted_by' attribute on pointers in structs). > | ... 86 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # build_abe binutils: > | -9 > | # build_kernel_llvm: > | -5 > | # build_abe qemu: > | -2 > | # linux_n_obj: > | 22473 > | > | From > | # reset_artifacts: > | -10 > | # build_abe binutils: > | -9 > | # build_kernel_llvm: > | -5 > | # build_abe qemu: > | -2 > | # linux_n_obj: > | 22474 > > Used configuration : > tcwg_kernel/llvm-master-arm-stable-allyesconfig > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1541. 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: > > > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-stable-allyesconfig-… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-stable-allyesconfig-… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/cff0a460ae864505bc2a064c269ebe5… Thanks, I think Bill fixed this with https://github.com/llvm/llvm-project/commit/2eb44aa0a94a8d4230c1c9a0c306af1… Cheers, Nathan

4 months, 3 weeks

3
2
0 0

[Linaro-TCWG-CI] llvmorg-21-init-1026-ga5fc7c3ac153: 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 tcwg_flang_build/main-aarch64, after: | commit llvmorg-21-init-1026-ga5fc7c3ac153 | Author: David Pagan <dave.pagan(a)amd.com> | Date: Thu Feb 6 12:41:10 2025 -0800 | | [clang][OpenMP] New OpenMP 6.0 assumption clause, 'no_openmp_constructs' (#125933) | | Add initial parsing/sema support for new assumption clause so clause can | be specified. For now, it's ignored, just like the others. | | ... 5 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;openmp;clang-tools-extra : | # FAILED | | From | # reset_artifacts: | -10 | # true: | 0 | # build_llvm -- clang;lld;flang;openmp;clang-tools-extra : | 1 Used configuration : tcwg_flang_build/main-aarch64 We track this bug report under https://linaro.atlassian.net/browse/LLVM-1548. 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_flang_build--main-aarch64-build/3162/artifac… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/3162/artifac… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/3162/artifac… Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/3162/artifac… Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/3161/artifac… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/a5fc7c3ac153bddab7c9d3464f17037…

4 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-888-gdf1bee03de1c: 1 regressions 2 improvements on aarch64

by Takahiro Kawashima (Fujitsu)

Hi, The detected problem is probably caused by a precision error of floating-point arithmetic by the fast-math flag. No need to investigate. Sorry for the noise. Thanks. > 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-21-init-888-gdf1bee03de1c > | Author: Paul Carabas <paulcaraa(a)gmail.com> > | Date: Thu Feb 6 02:02:29 2025 +0200 > | > | [mlir] Add math to LLVM lowering support for missing trigonometric & hyperbolic ops (#125753) > | > | The patch adds support for math -> LLVM dialect lowering for TanOp, > | Sinh, Cosh, Tanh > > Produces 1 regressions 2 improvements: > | > | regressions.sum: > | Running test-suite:Fujitsu/Fortran/0344 ... > | FAIL: test-suite :: Fujitsu/Fortran/0344/Fujitsu-Fortran-0344_1090.test > | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one > | > | improvements.sum: > | Running test-suite:Fujitsu/Fortran/0338 ... > | FAIL: test-suite :: Fujitsu/Fortran/0338/Fujitsu-Fortran-0338_0146.test > | ... and 2 more > | # "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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1547. 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_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/df1bee03de1cdc1505a4e9dde3ed064…

4 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-21-init-302-gaeaafce46447: 1 regressions on aarch64

by Tom Eccles

Thanks for the email, The regression in 0688_0041 is expected and documented in https://github.com/llvm/llvm-project/pull/124019. Codegen for that test was already broken before my patch, we just got luckier with undefined behavior before my changes. The regression in 0688_0041 should go away after https://github.com/llvm/llvm-project/pull/125307. Please do reach out if you have any questions, Tom ________________________________ From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Saturday, February 1, 2025 2:54 PM To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; Tom Eccles <Tom.Eccles(a)arm.com> Subject: [Linaro-TCWG-CI] llvmorg-21-init-302-gaeaafce46447: 1 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O0-debug, after: | commit llvmorg-21-init-302-gaeaafce46447 | Author: Tom Eccles <tom.eccles(a)arm.com> | Date: Fri Jan 31 09:35:26 2025 +0000 | | [mlir][OpenMP][flang] make private variable allocation implicit in omp.private (#124019) | | The intention of this work is to give MLIR->LLVMIR conversion freedom to | control how the private variable is allocated so that it can be | allocated on the stack in ordinary cases or as part of a structure used | ... 54 lines of the commit log omitted. Produces 1 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0688 ... | FAIL: test-suite :: Fujitsu/Fortran/0688/Fujitsu-Fortran-0688_0041.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;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1540. 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_flang_test--main-aarch64-O0-debug-build/439/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/439/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/439/… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/439/… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/438/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/aeaafce4644788963d9823067e46b50… 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.

4 months, 4 weeks

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-5595-g99b90c46110: 76 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-aarch64, after: | commit binutils-2_41-release-5595-g99b90c46110 | Author: Andrew Carlotti <andrew.carlotti(a)arm.com> | Date: Thu Jan 30 19:14:46 2025 +0000 | | aarch64: Fix fp8 feature dependencies | | We agreed with LLVM that we shouldn't enforce the architectural | dependencies between fp8 muliplication features, so remove them. | | ... 3 lines of the commit log omitted. Produces 76 regressions: | | regressions.sum: | Running g++:g++.target/aarch64/sve2/acle/aarch64-sve2-acle-asm.exp ... | FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O0 -DSTREAMING_COMPATIBLE -DTEST_FULL (test for excess errors) | FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O0 -DSTREAMING_COMPATIBLE -DTEST_OVERLOADS (test for excess errors) | FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O2 -g -DTEST_FULL (test for excess errors) | FAIL: gcc.target/aarch64/sve2/acle/asm/dot_lane_mf8.c -std=c++11 -O2 -g -DTEST_OVERLOADS (test for excess errors) | ... and 73 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-1509. 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/19… 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/19… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-aarch64-build/19… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=99b90c46110df…

4 months, 4 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc patch #105574: 1 regressions 1 improvements on arm

by Siddhesh Poyarekar

Has the bisect somehow failed in this? It's highly unlikely that a test macro would cause an ICE, unless it somehow exposed a latent bug, which also seems very unlikely in this context. Sid On 2025-01-28 20:48, 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 gcc_check master-arm, after: > | gcc patch https://patchwork.sourceware.org/patch/105574 > | Author: Siddhesh Poyarekar <siddhesh(a)gotplt.org> > | Date: Tue Jan 28 12:43:50 2025 -0500 > | > | [PATCH v3] testsuite/118127: Pass fortran tests on ppc64le for IEEE128 long doubles > | > | Denormal behaviour is well defined for IEEE128 long doubles, so don't > | XFAIL some gfortran tests on ppc64le when configured with the IEEE128 > | long double ABI. > | ... 13 lines of the commit log omitted. > | ... applied on top of baseline commit: > | 2abc555a80b Daily bump. > > Produces 1 regressions 1 improvements: > | > | regressions.sum: > | Running gcc:gcc.dg/dg.exp ... > | FAIL: gcc.dg/pr41123.c (internal compiler error: in gen_movsf, at config/arm/arm.md:7450) > | > | improvements.sum: > | Running gcc:gcc.dg/dg.exp ... > | FAIL: gcc.dg/pr41123.c (internal compiler error: in gen_movsf, at /home/tcwg-buildslave/workspace/tcwg_gnu_2/abe/snapshots/gcc.git~master/gcc/config/arm/arm.md:7450) > > Used configuration : > *CI config* tcwg_gcc_check master-arm > *configure and test flags:* --target arm-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 > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/10965/artifa… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3358/artifact/ar… > > Warning: we do not enable maintainer-mode nor automatically update > generated files, which may lead to failures if the patch modifies the > master files.

5 months

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-18802-gee99c4d4845d: Failure on aarch64

by Nathan Chancellor

On Fri, Jan 24, 2025 at 06:55:49AM +0000, 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 tcwg_kernel/llvm-master-aarch64-stable-allmodconfig, after: > | commit llvmorg-20-init-18802-gee99c4d4845d > | Author: SivanShani-Arm <sivan.shani(a)arm.com> > | Date: Thu Jan 23 09:46:59 2025 +0000 > | > | [LLVM][Clang][AArch64] Implement AArch64 build attributes (#123990) > | > | - Added support for AArch64-specific build attributes. > | - Print AArch64 build attributes to assembly. > | - Emit AArch64 build attributes to ELF. > | ... 2 lines of the commit log omitted. > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # build_abe binutils: > | -9 > | # build_kernel_llvm: > | -5 > | # build_abe qemu: > | -2 > | # linux_n_obj: > | 40 > | > | From > | # reset_artifacts: > | -10 > | # build_abe binutils: > | -9 > | # build_kernel_llvm: > | -5 > | # build_abe qemu: > | -2 > | # linux_n_obj: > | 25849 > > Used configuration : > tcwg_kernel/llvm-master-aarch64-stable-allmodconfig > > We track this bug report under https://linaro.atlassian.net/browse/LLVM-1530. 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: > > > > Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allmodcon… > Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allmodcon… > > Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : https://github.com/llvm/llvm-project/commit/ee99c4d4845db66c4daa2373352133f… Thanks for the report, this change needs adaption on the kernel side: https://lore.kernel.org/20250124-arm64-handle-arm-attributes-in-linker-scri… Cheers, Nathan

5 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-18360-gaf91372b7561: 1 regressions on aarch64

by Qadeer, Hafiz Abid

[AMD Official Use Only - AMD Internal Distribution Only] Thanks for bringing this to my notice. I have opened upstream issue https://github.com/llvm/llvm-project/issues/123960 to track this. I am working on a fix and will update when a PR is opened. Thanks Abid ________________________________ From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Wednesday, January 22, 2025 6:43 AM To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: Qadeer, Hafiz Abid <HafizAbid.Qadeer(a)amd.com>; maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org> Subject: [Linaro-TCWG-CI] llvmorg-20-init-18360-gaf91372b7561: 1 regressions on aarch64 Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding. Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O0-debug, after: | commit llvmorg-20-init-18360-gaf91372b7561 | Author: Abid Qadeer <haqadeer(a)amd.com> | Date: Mon Jan 20 12:03:59 2025 +0000 | | [flang][debug] Improve handling of cyclic derived types. (#122770) | | When `RecordType` is converted to corresponding `DIType`, we cache the | information to avoid doing the conversion again. | | ... 66 lines of the commit log omitted. Produces 1 regressions: | | regressions.sum: | Running test-suite:Fujitsu/Fortran/0394 ... | NOEXE: test-suite :: Fujitsu/Fortran/0394/Fujitsu-Fortran-0394_0031.test | # "NOEXE" means : the test program cannot be compiled Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O0 -g" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g" -DCMAKE_Fortran_FLAGS_RELEASE="-O0 -g" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1528. 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_flang_test--main-aarch64-O0-debug-build/383/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/383/… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O0-debug-build/382/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/af91372b75613d5654e68d393477e86…

5 months, 1 week

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-5490-g50505c486ed: 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 master-aarch64, after: | commit binutils-2_41-release-5490-g50505c486ed | Author: Nick Clifton <nickc(a)redhat.com> | Date: Tue Jan 21 10:48:02 2025 +0000 | | More updated translations Produces Failure: | Results changed to | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe gcc: | # FAILED | # build_abe linux: | # build_abe glibc: | # build_abe gdb: | # First few build errors in logs: | # 00:36:56 make[2]: [Makefile:1835: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored) | # 00:36:56 make[2]: [Makefile:1836: aarch64-unknown-linux-gnu/bits/largefile-config.h] Error 1 (ignored) | # 00:47:24 make[7]: [Makefile:850: stamp-modules-bits] Error 1 (ignored) | # 02:07:45 make[2]: [/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/gcc/ada/gcc-interface/Make-lang.in:995: gnat-install-tools] Error 1 (ignored) | | From | # reset_artifacts: | -10 | # true: | 0 | # build_abe binutils: | 1 | # build_abe gcc: | 2 | # build_abe linux: | 4 | # build_abe glibc: | 5 | # build_abe gdb: | 6 Used configuration : *CI config* tcwg_gnu_native_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1505. 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_native_build--master-aarch64-build/928/a… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a… Current build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/928/a… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_build--master-aarch64-build/927/a… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=50505c486ed26…

5 months, 1 week

1
0
0 0

is anybody using QEMU's iwmmxt/xscale emulation for toolchain testing?

by Peter Maydell

Hi; I'm wondering if anybody is using QEMU's iwmmxt/xscale emulation for toolchain testing. (My suspicion is the answer is "no".) This emulation isn't enabled by default, so to use it you would have to explicitly select an iwmmxt capable CPU (with -cpu or the QEMU_CPU environment variable). The relevant CPU types are anything beginning "pxa" (pxa250, pxa255, pxa260, pxa261, pxa262, pxa270-a0, pxa270-a1, pxa270, pxa270-b0, pxa270-b1, pxa270-c0, pxa270-c5). The context for this is that I'm considering deprecate-and-drop for this emulation. (We already dropped all the system emulation of boards that use these CPUs, so the only thing remaining is their support via QEMU's user-mode emulation.) If there's still somebody using this then I'm OK keeping it in QEMU a bit longer, but if as I suspect it's all entirely unused then we might as well start the process of dropping it. (I'm aware that GCC is in the process of dropping its iwmmxt codegen support. I also didn't find anything particularly with a web search with examples of users using it.) thanks -- PMM

5 months, 1 week

1
0
0 0

[Linaro-TCWG-CI] glibc-2.40.9000-770-gc36fc507819: 189 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit glibc-2.40.9000-770-gc36fc507819 | Author: Malte Skarupke <malteskarupke(a)fastmail.fm> | Date: Wed Dec 4 07:56:38 2024 -0500 | | nptl: Remove g_refs from condition variables | | This variable used to be needed to wait in group switching until all sleepers | have confirmed that they have woken. This is no longer needed. Nothing waits | on this variable so there is no need to track how many threads are currently | ... 4 lines of the commit log omitted. Produces 189 regressions: | | regressions.sum: | Running g++:g++.dg/analyzer/analyzer.exp ... | FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 12 (test for warnings, line 11) | FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 17 (test for warnings, line 10) | FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 18 (test for warnings, line 11) | FAIL: g++.dg/analyzer/fanalyzer-show-events-in-system-headers-default.C -std=c++14 at line 19 (test for warnings, line 11) | ... and 192 more Used configuration : *CI config* tcwg_gnu_native_check_gcc master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1504. 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_native_check_gcc--master-arm-build/1823/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1823/… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1822/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=c36fc50781995e6758ca…

5 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-17063-g303249c4490a: 9 regressions on aarch64

by Tom Eccles

Hi thanks for the report. I think it has already been fixed upstream by https://github.com/llvm/llvm-project/pull/122550<https://github.com/llvm/llvm-project/pull/122550?notification_referrer_id=N…>. Please let me know if this was not the case. Kind regards, Tom ________________________________ From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Sent: Tuesday, January 14, 2025 10:57 PM To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>; itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>; t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>; Tom Eccles <Tom.Eccles(a)arm.com> Subject: [Linaro-TCWG-CI] llvmorg-20-init-17063-g303249c4490a: 9 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-20-init-17063-g303249c4490a | Author: Tom Eccles <tom.eccles(a)arm.com> | Date: Wed Jan 8 10:05:21 2025 +0000 | | [flang][StackArrays] track pointers through fir.convert (#121919) | | This does add a little computational complexity because now every | freemem operation has to be tested for every allocation. This could be | improved with some more memoisation but I think it is easier to read | ... 6 lines of the commit log omitted. Produces 9 regressions: | Running test-suite:Fujitsu/Fortran/0073 ... | NOEXE: test-suite :: Fujitsu/Fortran/0073/Fujitsu-Fortran-0073_0018.test | Running test-suite:Fujitsu/Fortran/0487 ... | NOEXE: test-suite :: Fujitsu/Fortran/0487/Fujitsu-Fortran-0487_0035.test | NOEXE: test-suite :: Fujitsu/Fortran/0487/Fujitsu-Fortran-0487_0036.test | ... and 7 more | # "NOEXE" means : the test program cannot be compiled Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1515. 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_flang_test--main-aarch64-O3-neoverse_v1-sve_… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/303249c4490a7777a744d9afd449b64… 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.

5 months, 2 weeks

2
1
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-15150-gb3cba9be41bf: 2 regressions on aarch64

by Mel Chen

Hi, Florian Hahn and I landed 2 patches for fixing FindLastIV reductions idiom. https://github.com/llvm/llvm-project/commit/0e528ac404e13ed2d952a2d83aaf838… https://github.com/llvm/llvm-project/commit/3397950f2d21426c7520d114a125881… I think those can fix the issue you are facing. Please try them, and let me know if you still have regression on it. Mel On Fri, Dec 13, 2024 at 7:11 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 tcwg_flang_test/main-aarch64-Ofast-sve_vla, after: > | commit llvmorg-20-init-15150-gb3cba9be41bf > | Author: Mel Chen <mel.chen(a)sifive.com> > | Date: Thu Dec 12 16:48:31 2024 +0800 > | > | [LoopVectorize] Vectorize select-cmp reduction pattern for > increasing integer induction variable (#67812) > | > | Consider the following loop: > | ``` > | int rdx = init; > | ... 12 lines of the commit log omitted. > > Produces 2 regressions: > | Running test-suite:Fujitsu/Fortran/0365 ... > | FAIL: test-suite :: Fujitsu/Fortran/0365/Fujitsu-Fortran-0365_0185.test > | FAIL: test-suite :: Fujitsu/Fortran/0365/Fujitsu-Fortran-0365_0186.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;openmp;clang-tools-extra" > -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/bin/clang" > -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" > -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/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 -mllvm > -treat-scalable-fixed-error-as-warning=false -DNDEBUG" > -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve > -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm > -treat-scalable-fixed-error-as-warning=false -DNDEBUG" > -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve > -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm > -treat-scalable-fixed-error-as-warning=false -DNDEBUG" > -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu > "$\WORKSPACE/test/test-suite" > > We track this bug report under > https://linaro.atlassian.net/browse/LLVM-1482. 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_flang_test--main-aarch64-Ofast-sve_vla-build… > The full lists of regressions and improvements as well as configure and > make commands are in > * > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > The list of [ignored] baseline and flaky failures are in > * > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ > > Current build : > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > Reference build : > https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build… > > Instruction to reproduce the build : > https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… > > Full commit : > https://github.com/llvm/llvm-project/commit/b3cba9be41bfa89bc0ec212706c6028…

5 months, 2 weeks

2
1
0 0

Re: [Linaro-TCWG-CI] 8 patches in glibc: Failure on aarch64

by Michael Jeanson

On 2025-01-09 12:16, 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_build master-aarch64, after: > | 8 patches in glibc > | Patchwork URL: https://patchwork.sourceware.org/patch/104425 > | b2d4876946 [PATCH v16 8/8] Linux: Update internal copy of '<sys/rseq.h>' > | cdd3e61830 [PATCH v16 7/8] nptl: Remove the rseq area from 'struct pthread' > | a673377e3d [PATCH v16 6/8] nptl: Move the rseq area to the 'extra TLS' block > | 86803776b0 [PATCH v16 5/8] nptl: Introduce <rseq-access.h> for RSEQ_* accessors > | 928c07fc09 [PATCH v16 4/8] nptl: add rtld_hidden_proto to __rseq_size and __rseq_offset > | ... and 3 more patches in glibc > | ... applied on top of baseline commit: > | e41aabcc93 tests: Verify inheritance of cpu affinity > > Produces Failure: > | Results changed to > | # reset_artifacts: > | -10 > | # init_abe_sysroot: > | 0 > | # build_abe glibc -- --disable install: > | # FAILED > | # First few build errors in logs: > | # 00:00:59 ../csu/libc-tls.c:221:64: error: ‘TLS_TP_OFFSET’ undeclared (first use in this function); did you mean ‘TLS_DTV_OFFSET’? > | # 00:00:59 make[2]: *** [/home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/sysd-rules:451: /home/tcwg-build/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/csu/libc-tls.o] Error 1 > | # 00:00:59 make[1]: *** [Makefile:484: csu/subdir_lib] Error 2 > | # 00:00:59 make: *** [Makefile:20: all] Error 2 Is there a way to re-trigger this job on the current master branch without posting a new patchset? I sent this by mistake before Florian's TLS_TP_OFFSET patch was pushed to master but it is now. Thanks, Michael

5 months, 2 weeks

2
1
0 0

[Linaro-TCWG-CI] binutils-2_41-release-5322-gfd7728c8a4a: 6 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit binutils-2_41-release-5322-gfd7728c8a4a | Author: H.J. Lu <hjl.tools(a)gmail.com> | Date: Sun Jan 12 15:14:38 2025 +0800 | | ld: Update function prototypes for compilers defaulting to -std=gnu23 | | Since GCC 15 defaults to -std=gnu23, update function prototypes in linker | tests for compilers defaulting to -std=gnu23. | | ... 16 lines of the commit log omitted. Produces 6 regressions: | Running ld:ld-vsb/vsb.exp ... | XPASS: visibility (hidden_undef) (non PIC) | XPASS: visibility (hidden_undef) (non PIC, load offset) | XPASS: visibility (hidden_undef) (PIC main, non PIC so) | XPASS: visibility (protected_undef) (non PIC) | ... and 2 more Used configuration : *CI config* tcwg_gnu_cross_check_binutils master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1502. 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_binutils--master-arm-build/9… 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_binutils--master-arm-build/9… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_binutils--master-arm-build/9… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_binutils--master-arm-build/9… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_binutils--master-arm-build/9… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=fd7728c8a4aa7…

5 months, 2 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] 2 patches in binutils: 1 regressions on aarch64

by H.J. Lu

On Mon, Jan 13, 2025 at 4:42 AM <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In binutils_check master-aarch64, after: > | 2 patches in binutils > | Patchwork URL: https://patchwork.sourceware.org/patch/104601 > | 795205673be [PATCH v3 2/4] ld: Document mixing IR and non-IR objects for -r > | a8d189da9d5 [PATCH v3 1/4] ld: Add lto and none-lto output support for ld -r > | ... applied on top of baseline commit: > | 338e0b05d8f Fix grammar in "Debug Names" node of the manual > > Produces 1 regressions: > | Running ld:ld-plugin/plugin.exp ... > | FAIL: nm --plugin I can't reproduce it on cfarm185.cfarm.net: /home/hjl/build/binutils/build-aarch64-linux/ld/../binutils/nm-new --plugin /home/hjl/build/binutils/build-aarch64-linux/ld/.libs/libldtestplug2.so.0 /home/hjl/git/binutils-gdb/ld/testsuite/ld-plugin/func.c 00000000 T _func 00000000 T func PASS: nm --plugin It has GCC 13.3.1. I saw you were using GCC 11.4.0. Please try GCC 11.5.0. > Used configuration : > *CI config* tcwg_binutils_check master-aarch64 > *configure and test flags:* --target aarch64-linux-gnu > > 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_binutils_check--master-aarch64-precommit/233… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/233… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/233… > > Current build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-precommit/233… > Reference build : https://ci.linaro.org/job/tcwg_binutils_check--master-aarch64-build/2093/ar… > > 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.

5 months, 2 weeks

1
1
0 0

Re: [Linaro-TCWG-CI] gcc-15-6774-g740c84975ceb: Failure on arm

by Sam James

This is definitely https://gcc.gnu.org/PR118409 (indeed the ifcombine change). We had PR118417 too which I suspect is the same.

5 months, 2 weeks

1
0
0 0

[Linaro-TCWG-CI] glibc-2.40.9000-734-g93d0bfbe8f: 2 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-arm, after: | commit glibc-2.40.9000-734-g93d0bfbe8f | Author: Michael Jeanson <mjeanson(a)efficios.com> | Date: Wed Jul 10 15:48:49 2024 -0400 | | nptl: Move the rseq area to the 'extra TLS' block | | Move the rseq area to the newly added 'extra TLS' block, this is the | last step in adding support for the rseq extended ABI. The size of the | rseq area is now dynamic and depends on the rseq features reported by | ... 7 lines of the commit log omitted. Produces 2 regressions: | Running glibc:elf ... | FAIL: elf/tst-tlsalign-extern-static | FAIL: elf/tst-tlsalign-static Used configuration : *CI config* tcwg_glibc_check master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1497. 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_glibc_check--master-arm-build/2302/artifact/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2302/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2302/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2302/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2301/artifact/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=93d0bfbe8ffa9c3dcbfc…

5 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] gcc-15-6566-g804e9d55d9e: 5 regressions on arm

by Sam James

This is being worked on at https://inbox.sourceware.org/libc-alpha/328b6145af0d5c1d2c3fc5ef44cb7b74717…. See also https://inbox.sourceware.org/libc-alpha/fcdbc863-3ad7-de56-6076-85948d03046…. thanks, sam

5 months, 3 weeks

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-16411-gccfe0de0e1e3: 1 regressions on aarch64

by Hassnaa Hamdi

Hello everyone. Is that regression is definitely caused by my patch ? Best Regards, Hassnaa. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Saturday, 28 December 2024 at 5:41 AM To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Hassnaa Hamdi <Hassnaa.Hamdi(a)arm.com> Subject: [Linaro-TCWG-CI] llvmorg-20-init-16411-gccfe0de0e1e3: 1 regressions on aarch64 Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-20-init-16411-gccfe0de0e1e3 | Author: Hassnaa Hamdi <hassnaa.hamdi(a)arm.com> | Date: Fri Dec 27 12:42:07 2024 +0000 | | [LV]: Teach LV to recursively (de)interleave. (#89018) | | Currently available intrinsics are only ld2/st2, which don't support interleaving factor > 2. | This patch teaches the LV to use ld2/st2 recursively to support high | interleaving factors. Produces 1 regressions: | Running test-suite:Fujitsu/Fortran/0341 ... | NOEXE: test-suite :: Fujitsu/Fortran/0341/Fujitsu-Fortran-0341_0409.test | # "NOEXE" means : the test program cannot be compiled Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://linaro.atlassian.net/browse/LLVM-1494. 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_flang_test--main-aarch64-O3-neoverse_v1-sve_… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/ Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s… Full commit : https://github.com/llvm/llvm-project/commit/ccfe0de0e1e37ed369c9bf89dd0188b… 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.

5 months, 3 weeks

2
1
0 0

[Linaro-TCWG-CI] glibc-2.40.9000-670-ge5ca265a9c9: 28 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In glibc_check master-arm, after: | commit glibc-2.40.9000-670-ge5ca265a9c9 | Author: Paul Zimmermann <Paul.Zimmermann(a)inria.fr> | Date: Fri Dec 20 10:41:38 2024 +0100 | | new inputs with large errors for [a]cospi, [a]sinpi, [a]tanpi, atan2pi | | These inputs were generated with the programs from | https://gitlab.inria.fr/zimmerma/math_accuracy, | with rounding to nearest: | ... 3 lines of the commit log omitted. Produces 28 regressions: | Running glibc:math ... | FAIL: math/test-double-acospi | FAIL: math/test-double-atanpi | FAIL: math/test-double-cospi | FAIL: math/test-double-sinpi | ... and 24 more Used configuration : *CI config* tcwg_glibc_check master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1482. 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_glibc_check--master-arm-build/2267/artifact/… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2267/artifact/… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2267/artifact/… Current build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2267/artifact/… Reference build : https://ci.linaro.org/job/tcwg_glibc_check--master-arm-build/2266/artifact/… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=e5ca265a9c9054c01c78…

5 months, 4 weeks

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-4788-gd5cbf916be4: 14 regressions on arm

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-arm, after: | commit binutils-2_41-release-4788-gd5cbf916be4 | Author: Jan Beulich <jbeulich(a)suse.com> | Date: Mon Nov 18 11:35:57 2024 +0100 | | gas/ELF: also reject merge entity size being zero | | This won't have any useful effect, so is at best marginally less bogus | than a negative value. | | ... 2 lines of the commit log omitted. Produces 14 regressions: | Running ld:ld-elf/compress.exp ... | FAIL: Build zlibbegin.o with zlib compressed debug sections | FAIL: Build gnubegin.o with zlib-gnu compressed debug sections | FAIL: Build gabiend.o with zlib-gabi compressed debug sections | FAIL: Link -r with zlib compressed debug output | ... and 10 more Used configuration : *CI config* tcwg_gnu_cross_check_binutils master-arm *configure and test flags:* --target arm-linux-gnueabihf We track this bug report under https://linaro.atlassian.net/browse/GNU-1427. 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_binutils--master-arm-build/8… 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_binutils--master-arm-build/8… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_cross_check_binutils--master-arm-build/8… Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_binutils--master-arm-build/8… Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_binutils--master-arm-build/8… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=d5cbf916be4a0…

6 months

5
12
0 0

[Linaro-TCWG-CI] glibc-2.40.9000-564-ge79e5c4899e: 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 glibc_build master-aarch64, after: | commit glibc-2.40.9000-564-ge79e5c4899e | Author: DJ Delorie <dj(a)redhat.com> | Date: Thu Nov 14 15:12:57 2024 -0500 | | assert: ensure posix compliance, add tests for such | | Fix assert.c so that even the fallback | case conforms to POSIX, although not exactly the same as | the default case so a test can tell the difference. | ... 6 lines of the commit log omitted. Produces Failure: | Results changed to | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | # FAILED | # First few build errors in logs: | # 00:01:09 assert.c:120:14: error: ignoring return value of ‘writev’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:09 make[2]: *** [../o-iterator.mk:9: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/assert/assert.o] Error 1 | # 00:01:09 assert.c:120:14: error: ignoring return value of ‘writev’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result] | # 00:01:09 make[2]: *** [../o-iterator.mk:9: /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-glibc.git~master/assert/assert.os] Error 1 | # 00:01:09 make[1]: *** [Makefile:484: assert/subdir_lib] Error 2 | # 00:01:09 make: *** [Makefile:21: all] Error 2 | | From | # reset_artifacts: | -10 | # init_abe_sysroot: | 0 | # build_abe glibc -- --disable install: | 1 Used configuration : *CI config* tcwg_glibc_build master-aarch64 *configure and test flags:* --target aarch64-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1473. 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_glibc_build--master-aarch64-build/2254/artif… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2254/artif… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2254/artif… Current build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2254/artif… Reference build : https://ci.linaro.org/job/tcwg_glibc_build--master-aarch64-build/2252/artif… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=e79e5c4899e82eff1032…

6 months, 1 week

1
0
0 0

[Linaro-TCWG-CI] binutils-2_41-release-5150-g9f2e3c21f65: Failure 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 tcwg_kernel/gnu-master-arm-mainline-allnoconfig, after: | commit binutils-2_41-release-5150-g9f2e3c21f65 | Author: Nick Clifton <nickc(a)redhat.com> | Date: Thu Dec 19 09:59:11 2024 +0000 | | Fix the handling or arguments and macro pseudo-variables inside nested assembler macros. | | PR 32391 Produces Failure: | Results changed to | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 557 | | From | # reset_artifacts: | -10 | # build_abe binutils: | -9 | # build_abe stage1: | -5 | # build_abe qemu: | -2 | # linux_n_obj: | 618 | # linux build successful: | all Used configuration : tcwg_kernel/gnu-master-arm-mainline-allnoconfig We track this bug report under https://linaro.atlassian.net/browse/GNU-1470. 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: Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-mainline-allnoconfig-… Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-mainline-allnoconfig-… Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti… Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=9f2e3c21f6506…

6 months, 1 week

2
2
0 0

Re: [Linaro-TCWG-CI] v6.13-rc2-20-gce8fd0500b741: Failure on aarch64

by Nathan Chancellor

Thanks for the report! On Thu, Dec 19, 2024 at 04:05:00AM +0000, 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 tcwg_kernel/llvm-master-aarch64-next-defconfig, after: > | commit v6.13-rc2-20-gce8fd0500b741 > | Author: Bartosz Golaszewski <bartosz.golaszewski(a)linaro.org> > | Date: Tue Dec 3 10:19:35 2024 +0100 > | > | crypto: qce - use __free() for a buffer that's always freed > | > | The buffer allocated in qce_ahash_hmac_setkey is always freed before > | returning to use __free() to automate it. > | > | ... 3 lines of the commit log omitted. I have sent a revert of that change: https://lore.kernel.org/20241218-crypto-qce-sha-fix-clang-cleanup-error-v1-… Cheers, Nathan

6 months, 1 week

1
0
0 0

Re: [Linaro-TCWG-CI] llvmorg-20-init-15723-gb2c363e2616d: 7 regressions on aarch64

by Peter Klausler

Fixed by https://github.com/llvm/llvm-project/pull/120614. From: ci_notify(a)linaro.org <ci_notify(a)linaro.org> Date: Wednesday, December 18, 2024 at 21:27 To: ohno.yasuyuki(a)fujitsu.com <ohno.yasuyuki(a)fujitsu.com>, itou.tetsuya(a)fujitsu.com <itou.tetsuya(a)fujitsu.com>, t-kawashima(a)fujitsu.com <t-kawashima(a)fujitsu.com> Cc: maxim.kuvyrkov(a)linaro.org <maxim.kuvyrkov(a)linaro.org>, Peter Klausler <pklausler(a)nvidia.com> Subject: [Linaro-TCWG-CI] llvmorg-20-init-15723-gb2c363e2616d: 7 regressions on aarch64 External email: Use caution opening links or attachments Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In tcwg_flang_test/main-aarch64-O3-neoverse_v1-sve_vla-mpipeliner-stack_arrays, after: | commit llvmorg-20-init-15723-gb2c363e2616d | Author: Peter Klausler <pklausler(a)nvidia.com> | Date: Tue Dec 17 12:10:29 2024 -0800 | | [flang] Fix generic resolution with actual/dummy procedure incompatib… (#120105) | | …ility | | We generally allow any legal procedure pointer target as an actual | ... 6 lines of the commit log omitted. Produces 7 regressions: | Running test-suite:Fujitsu/Fortran/0249 ... | NOEXE: test-suite :: Fujitsu/Fortran/0249/Fujitsu-Fortran-0249_0023.test | NOEXE: test-suite :: Fujitsu/Fortran/0249/Fujitsu-Fortran-0249_0024.test | NOEXE: test-suite :: Fujitsu/Fortran/0249/Fujitsu-Fortran-0249_0025.test | NOEXE: test-suite :: Fujitsu/Fortran/0249/Fujitsu-Fortran-0249_0026.test | ... and 4 more | # "NOEXE" means : the test program cannot be compiled Used configuration : * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -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/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -mcpu=neoverse-v1 -msve-vector-bits=scalable -mllvm -scalable-vectorization=preferred -mllvm -treat-scalable-fixed-error-as-warning=false -mllvm -aarch64-enable-pipeliner -mllvm -pipeliner-mve-cg -DNDEBUG -fstack-arrays" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite" We track this bug report under https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinaro.at…<https://linaro.atlassian.net/browse/LLVM-1486>. 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> The full lists of regressions and improvements as well as configure and make commands are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> The list of [ignored] baseline and flaky failures are in * https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Fujitsu testsuite : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/fujitsu/compiler-test-suite/> Current build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Reference build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fci.linaro…<https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-O3-neoverse_v1-sve_…> Instruction to reproduce the build : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit-us.li…<https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…> Full commit : https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…<https://github.com/llvm/llvm-project/commit/b2c363e2616dc6ac6ee76c223d84ec5…>

6 months, 1 week

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain