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;
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…
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!
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
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…
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…
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…
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.
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…
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
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…
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…
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…
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…
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…
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…
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…
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.