Hi Nathan,
Sorry this report is incorrect because we are in the process of moving
to new machines.
Please ignore it.
Sorry for the noise.
Thanks,
Christophe
On Tue, 29 Jul 2025 at 04:34, <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:
> | gcc patch https://patchwork.sourceware.org/patch/117089
> | Author: Nathan Myers <ncm(a)cantrip.org>
> | Date: Mon Jul 28 05:25:55 2025 -0400
> |
> | [PATCHv5] libstdc++: Add NTTP bind_front, -back, not_fn (P2714) [PR119744]
> |
> | Stabilizing.
> |
> | Changes in v5:
> | ... 39 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | a51bf9e10182 ifcvt: Fix ifcvt for multiple phi nodes after factoring operator [PR121236]
>
> Produces 84 regressions 2 fixes:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/cpp1z/pr85569.C -std=c++20 (test for excess errors)
> | Running g++:g++.dg/modules/modules.exp ...
> | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (internal compiler error: canonical types differ for identical types 'auto' and 'auto')
> | FAIL: g++.dg/modules/xtreme-header-2_b.C -std=c++26 (test for excess errors)
> | ... and 83 more
> |
> | fixes.sum:
> | Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
> | Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
>
> Used configuration :
> *CI config* tcwg_gcc_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_gcc_check--master-aarch64-precommit/11852/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-aarch64-precommit/11852/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11852/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4055/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.
Hi Richard,
Sorry this report is incorrect because we are in the process of moving
to new machines.
Please ignore it.
Sorry for the noise.
Thanks,
Christophe
On Tue, 29 Jul 2025 at 04:11, <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:
> | gcc patch https://patchwork.sourceware.org/patch/117090
> | Author: Richard Biener <rguenther(a)suse.de>
> | Date: Mon Jul 28 11:36:06 2025 +0200
> |
> | [PATCH] Remove STMT_VINFO_MEMORY_ACCESS_TYPE
> |
> | This should be present only on SLP nodes now. The RISC-V changes
> | are mechanical along the line of the SLP_TREE_TYPE changes.
> |
> | ... 19 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | a51bf9e1018 ifcvt: Fix ifcvt for multiple phi nodes after factoring operator [PR121236]
>
> Produces 6976 regressions 2 fixes:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++11 (internal compiler error: Segmentation fault)
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++11 (test for excess errors)
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++17 (internal compiler error: Segmentation fault)
> | FAIL: g++.dg/opt/pr112374.C -std=gnu++17 (test for excess errors)
> | ... and 6984 more
> |
> | fixes.sum:
> | Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
> | Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> | FAIL: gcc.target/aarch64/sve/acle/general/cops.c -march=armv8.2-a+sve -moverride=tune=none execution test
>
> Used configuration :
> *CI config* tcwg_gcc_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_gcc_check--master-aarch64-precommit/11853/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-aarch64-precommit/11853/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/11853/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4055/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.
On Thu, Jul 24, 2025 at 10:42:41AM +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.
It appears that this build was running tests on qemu that doesn't seem to support
the same signal handling behaviour for SME as would the kernel that supports SME.
On a system that supports SME with kernel 6.16 these tests work as expected provided
that their dependencies are resolved by dynamic loader to the new version of libgcc.
So, no issue in the patch or in the tests.
Thanks,
Yury
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.
> Our automatic CI has detected problems related to your patch(es).
Thanks, I'm looking into it.
Kind regards,
Yury
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.
Hi!
On 2025-04-26T00:09:21+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 gcc_check master-arm, after:
> | commit gcc-16-130-gaafe942227b
> | Author: Thomas Schwinge <tschwinge(a)baylibre.com>
> | Date: Wed Apr 23 10:51:48 2025 +0200
> |
> | GCN, nvptx offloading: Host/device compatibility: Itanium C++ ABI, DSO Object Destruction API [PR119853, PR119854]
> |
> | '__dso_handle' for '__cxa_atexit', '__cxa_finalize'. See
> | <https://itanium-cxx-abi.github.io/cxx-abi/abi.html#dso-dtor>.
> |
> | ... 13 lines of the commit log omitted.
>
> Produces 10 regressions:
> |
> | regressions.sum:
> | Running libgomp:libgomp.c++/c++.exp ...
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, " 4
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sH1, \\&__dso_handle>" 1
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sH2, \\&__dso_handle>" 1
> | FAIL: libgomp.c++/target-cdtor-1.C scan-tree-dump-times optimized "gimple_call <__cxa_atexit, NULL, _ZN1SD1Ev, \\&sHD1, \\&__dso_handle>" 1
> | ... and 6 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-1568.
Is it expected that I'm not able to log into the Jira instance, and that
most of the links in there are either:
| Secure Connection Failed
|
| An error occurred during a connection to git-us.linaro.org. Cannot communicate securely with peer: no common encryption algorithm(s).
..., or:
| Oops!
|
| Not Found
|
| This page may not exist, or you may not have permission to see it.
> Please let us know if you have a fix.
I should have a fix: the attached
"Adjust 'libgomp.c++/target-cdtor-{1,2}.C' for 'targetm.cxx.use_aeabi_atexit' [PR119853, PR119854]"
ought to address this. I've "mock-tested" this locally; is there a way
for me to run this through the Linaro "pre-commit" CI?
Grüße
Thomas
> 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/3752/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/3752/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/artifact/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3752/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3751/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=aafe942227baf8c2bcd4cac2c…
I have pushed the following PR to address issues in my patch: https://github.com/llvm/llvm-project/pull/149703
I haven’t verified that it fixes your regression, will do that shortly.
Jonathan
> On 18 Jul 2025, at 20:40, 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-22-init-340-ge8a891b0f9d2
> | Author: Jonathan Cohen <joncoh(a)apple.com>
> | Date: Thu Jul 17 19:21:57 2025 +0300
> |
> | [AArch64][Machine-Combiner] Split gather patterns into neon regs to multiple vectors (#142941)
> |
> | This changes optimizes gather-like sequences, where we load values
> | separately into lanes of a neon vector. Since each load has serial
> | dependency, when performing multiple i32 loads into a 128 bit vector for example, it
> | ... 3 lines of the commit log omitted.
>
> Produces 4 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0631 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0110.test
> | FAIL: test-suite :: Fujitsu/Fortran/0631/Fujitsu-Fortran-0631_0111.test
> | Running test-suite:Fujitsu/Fortran/0640 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0640/Fujitsu-Fortran-0640_0074.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-1731. 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/e8a891b0f9d2a742ac3904116aaec2c…
Tomasz,
The new __any_input_iterator type should only be declared for C++20
and higher, so guarded by __cpp_lib_concepts
Just checking __cpp_concepts isn't enough, because that's true for
-std=c++17 -fconcepts but std::input_iterator isn't defined in that
case.
On Fri, 18 Jul 2025 at 17: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 arm-eabi v7-a softfp, after:
> | commit gcc-16-2334-g9e330977385
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Jun 5 12:05:19 2025 +0100
> |
> | libstdc++: Add std::inplace_vector for C++26 (P0843R14) [PR119137]
> |
> | Implement std::inplace_vector as specified in P0843R14, without follow
> | up papers, in particular P3074R7 (trivial unions). In consequence
> | inplace_vector<T, N> can be used inside constant evaluations only
> | ... 62 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/concepts/expression.C -std=gnu++17 (test for excess errors)
> | UNRESOLVED: g++.dg/concepts/expression.C -std=gnu++17 compilation failed to produce executable
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=arm --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=softfp --target_board=-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp qemu_cpu=cortex-a9
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1636. 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-arm_v7a_softfp_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-arm_v7a_softfp_e…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e…
>
> 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
Hi,
Probably 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-18750-gdd60663b9bfa
> | Author: Alexey Bataev <a.bataev(a)outlook.com>
> | Date: Wed Jul 9 19:52:09 2025 -0400
> |
> | [SLP] Emit reduction instead of 2 extracts + scalar op, when vectorizing operands (#147583)
> |
> | Added emission of the 2-element reduction instead of 2 extracts + scalar
> | op, when trying to vectorize operands of the instruction, if it is more
> | profitable.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/C/0030 ...
> | FAIL: test-suite :: Fujitsu/C/0030/Fujitsu-C-0030_0056.test
> | Running test-suite:Fujitsu/Fortran/0334 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0334/Fujitsu-Fortran-0334_0012.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-1728. 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/dd60663b9bfaab15362a850ba7f63ba…
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-509-g3d3572f590
| Author: Florian Weimer <fweimer(a)redhat.com>
| Date: Fri Jul 11 16:04:07 2025 +0200
|
| Linux: Keep termios ioctl constants strictly internal
|
| Undefine TCGETS, TCGETS2, and related ioctl constants in the installed
| headers. Extract the correct constants (using the kernel type
| definitions) automatically from the UAPI headers. The kernel
| ... 11 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:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:766:27: error: ‘TCGETS’ was not declared in this scope; did you mean ‘TCGETX’?
| # 00:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:772:27: error: ‘TCSETS’ was not declared in this scope; did you mean ‘TCSETA’?
| # 00:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:773:28: error: ‘TCSETSF’ was not declared in this scope; did you mean ‘TCSETAF’?
| # 00:07:05 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/snapshots/gcc.git~master/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:774:28: error: ‘TCSETSW’ was not declared in this scope; did you mean ‘TCSETAW’?
| # 00:07:05 make[4]: *** [Makefile:627: sanitizer_platform_limits_posix.lo] Error 1
| # 00:07:05 make[3]: *** [Makefile:533: all-recursive] Error 1
| # 00:07:05 make[2]: *** [Makefile:420: all] Error 2
| # 00:07:05 make[1]: *** [Makefile:12804: all-target-libsanitizer] Error 2
| # 00:07:05 make: *** [Makefile:1068: 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-arm
*configure and test flags:* --target arm-linux-gnueabihf
We track this bug report under https://linaro.atlassian.net/browse/GNU-1632. 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-arm-build/1136/artif…
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-arm-build/1136/artif…
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1136/artif…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_build--master-arm-build/1135/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=3d3572f59059e2b19b85…
I am testing this.
On Tue, Jul 8, 2025 at 7:10 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 simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/115820
> | Author: H.J. Lu <hjl.tools(a)gmail.com>
> | Date: Sat Jun 28 06:27:25 2025 +0800
> |
> | [PATCH] Check backend when setting DECL_ALIGN for PARM_DECL
> |
> | Since a backend may ignore type alignment for arguments passed on stack,
> | call targetm.calls.function_arg_boundary to set DECL_ALIGN for PARM_DECL
> | and change __alignof to return DECL_ALIGN, instead of TYPE_ALIGN, for
> | ... 21 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | ed912b1ee5a libstdc++: Fix attribute order on __normal_iterator friends [PR120949]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> | # First few build errors in logs:
> | # 00:04:46 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/gcc.git~master/libgcc/config/aarch64/lse-init.c:44:1: internal compiler error: Segmentation fault
> | # 00:04:47 make[3]: *** [/home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/gcc.git~master/libgcc/config/aarch64/t-lse:41: lse-init.o] Error 1
> | # 00:04:47 make[2]: *** [Makefile:19575: all-stage1-target-libgcc] Error 2
> | # 00:04:47 make[1]: *** [Makefile:25557: stage1-bubble] Error 2
> | # 00:04:47 make: *** [Makefile:1106: all] Error 2
> |
> | 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.
--
H.J.
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In master-arm, after:
| commit v10.0.0-1793-g932522a9ddc
| Author: Richard Henderson <richard.henderson(a)linaro.org>
| Date: Mon Oct 23 14:29:46 2023 -0700
|
| tcg/optimize: Fold and to extract during optimize
|
| Reviewed-by: Pierrick Bouvier <pierrick.bouvier(a)linaro.org>
| Signed-off-by: Richard Henderson <richard.henderson(a)linaro.org>
Produces 6 regressions:
|
| regressions.sum:
| Running gcc:gcc.target/aarch64/advsimd-intrinsics/advsimd-intrinsics.exp ...
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O1 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O2 execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
| FAIL: gcc.target/aarch64/advsimd-intrinsics/vshl.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
| ... and 2 more
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-1617. 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/2154/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/2154/a…
The list of [ignored] baseline and flaky failures are in
* https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2154/a…
Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2154/a…
Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/2153/a…
Instruction to reproduce the build : https://gitlab.com/Linaro/tcwg/ci/interesting-commits/-/raw/master/qemu/sha…
Full commit : https://gitlab.com/qemu-project/qemu/commit/932522a9ddc1f7c7866009cd73eaf79…
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-15039-gea9046699eae
> | Author: Paul Walker <paul.walker(a)arm.com>
> | Date: Wed Jun 11 11:02:32 2025 +0100
> |
> | [LLVM][SROA] Teach SROA how to "bitcast" between fixed and scalable vectors. (#130973)
> |
> | For function whose vscale_range is limited to a single value we can size
> | scalable vectors. This aids SROA by allowing scalable vector load and
> | store operations to be considered for replacement whereby bitcasts
> | ... 1 lines of the commit log omitted.
>
> Produces 1 regression:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0136 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0136/Fujitsu-Fortran-0136_0012.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-1716. 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/ea9046699eae04ac5159a1666f19b5b…
Thanks. See https://gcc.gnu.org/PR120929.
Qing, you may be able to reproduce it on x86-64 with ./configure
--with-build-config="bootstrap-ubsan" && make -j$(nproc) -l$(nproc) too.
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_vla, after:
> | commit llvmorg-21-init-16543-g7d2293d1d953
> | Author: Ross Kirsling <ross.kirsling(a)sony.com>
> | Date: Tue Jun 24 09:51:49 2025 -0700
> |
> | [InstCombine] KnownBits::isNonNegative should recognize `b - a` after `a <= b` (#145105)
> |
> | Alive2: https://alive2.llvm.org/ce/z/an9npN
> | Fixes #142283.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/Fortran/0117 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0117/Fujitsu-Fortran-0117_0070.test
> | Running test-suite:Fujitsu/Fortran/0680 ...
> | FAIL: test-suite :: Fujitsu/Fortran/0680/Fujitsu-Fortran-0680_0065.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-1715. 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/7d2293d1d95379bbdbb6446b088219a…
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…
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.
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.
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…
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…
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…
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…
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.
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…>
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…
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
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/