linaro-toolchain

linaro-toolchain@lists.linaro.org

5599 discussions

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

[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, 2 days

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

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, 3 days

[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

[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

[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

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…

1 week, 6 days

[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

[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, 2 days

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain