On Fri, Mar 28, 2025 at 03:28:46PM +0000, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In tcwg_kernel/llvm-master-aarch64-stable-allmodconfig, after:
> | commit llvmorg-21-init-6198-g9694844d7e36
> | Author: Henry Jiang <h243jian(a)uwaterloo.ca>
> | Date: Mon Mar 24 09:49:31 2025 -0400
> |
> | Reland "[Transforms] LoopIdiomRecognize recognize strlen and wcslen #108985" (#132572)
> |
> | Reland https://github.com/llvm/llvm-project/pull/108985
> |
> | Extend `LoopIdiomRecognize` to find and replace loops of the form
> | ... 12 lines of the commit log omitted.
Thanks a lot for the report. I sent the third version of the patchset
that should resolve this issue this morning so I hope it will be moved
on soon:
https://lore.kernel.org/20250328-string-add-wcslen-for-llvm-opt-v3-0-a180b4…
Cheers,
Nathan
Hi,
On Fri, 28 Mar 2025 at 14:24, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi cortex-m23 soft, after:
> | commit gcc-15-8947-g8ed2d5d219e
> | Author: Jørgen Kvalsvik <j(a)lambda.is>
> | Date: Tue Jun 4 14:13:22 2024 +0200
> |
> | Add prime path coverage to gcc/gcov
> |
> | This patch adds prime path coverage to gcc/gcov. First, a quick
> | introduction to path coverage, before I explain a bit on the pieces of
> | the patch.
> | ... 404 lines of the commit log omitted.
>
> Produces 5 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/gcov/gcov.exp ...
> | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++17 gcov failed: spawn failed
> | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++26 gcov failed: spawn failed
> | FAIL: g++.dg/gcov/gcov-22.C -std=gnu++98 gcov failed: spawn failed
> | Running gcc:gcc.misc-tests/gcov.exp ...
> | ... and 2 more
>
I've given a quick look at the logs, and gcov-22.C says:
spawn -ignore SIGHUP
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/destdir/x86_64-pc-linux-gnu/bin/gcov
--prime-paths gcov-22.C
FAIL: g++.dg/gcov/gcov-22.C -std=gnu++98 gcov failed: spawn failed
I believe that rather than "dg-compile", it should use "dg-do run {
target native }" like almost all other gcov tests?
For the other errors:
FAIL: gcc.misc-tests/gcov-31.c (test for excess errors)
FAIL: gcc.misc-tests/gcov-32.c (test for excess errors)
the log actually says:
/gcov-31.c:12:8: error: unknown type name 'sigjmp_buf'; did you mean 'jmp_buf'?
/gcov-31.c: In function 'run_pending_traps':
/gcov-31.c:22:5: error: implicit declaration of function '__sigsetjmp'
[-Wimplicit-function-declaration]
/gcov-32.c:6:8: error: unknown type name 'sigjmp_buf'; did you mean 'jmp_buf'?
/gcov-32.c:21:19: error: passing argument 1 of 'setjmp' makes pointer
from integer without a cast [-Wint-conversion]
I haven't looked further, but does this indicate a dependency on
glibc? (this target "arm-none-eabi" uses newlib)
Thanks,
Christophe
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1551. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_soft_e…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=8ed2d5d219e999aee42015a0d…
On Wed, 26 Mar 2025 at 00:55, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_check master-aarch64, after:
> | commit gcc-15-8904-ge200f53a555
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Mar 25 13:24:08 2025 +0000
> |
> | libstdc++: Optimize std::vector construction from input iterators [PR108487]
> |
> | LWG 3291 make std::ranges::iota_view's iterator have input_iterator_tag
> | as its iterator_category, even though it satisfies the C++20
> | std::forward_iterator concept. This means that the traditional
> | ... 41 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running g++:g++.dg/dg.exp ...
> | FAIL: g++.dg/tree-ssa/initlist-opt1.C -std=c++26 scan-tree-dump gimple "_M_range_initialize<const char\\* const\\*>"
> | FAIL: g++.dg/tree-ssa/initlist-opt2.C -std=c++26 scan-tree-dump gimple "_M_range_initialize<const char\\* const\\*>"
>
> Used configuration :
> *CI config* tcwg_gcc_check master-aarch64
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1548. Please let us know if you have a fix.
I have a fix:
--- a/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
+++ b/gcc/testsuite/g++.dg/tree-ssa/initlist-opt1.C
@@ -4,7 +4,7 @@
// { dg-skip-if "requires hosted libstdc++ for string" { ! hostedlib } }
// Test that we do range-initialization from const char *.
-// { dg-final { scan-tree-dump {_M_range_initialize<const char\*
const\*>} "gimple" } }
+// { dg-final { scan-tree-dump {_M_range_initialize_n<const char\*
const\*} "gimple" } }
// { dg-final { scan-tree-dump {static const char.*72} "gimple" } }
#include <string>
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3491/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/3490/artifac…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e200f53a5556516ec831e6b7a…
Hi,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:22, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_build master-aarch64, after:
> | gcc patch https://patchwork.sourceware.org/patch/109136
> | Author: Hu, Lin1 <lin1.hu(a)intel.com>
> | Date: Tue Mar 25 15:44:51 2025 +0800
> |
> | [PATCH] i386: Add "s_" as Saturation for AVX10.2 Converting Intrinsics.
> |
> | Hi, all
> |
> | This patch aims to add "s_" after 'cvt' represent saturation.
> | ... 21 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
> Used configuration :
> *CI config* tcwg_gcc_build master-aarch64
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17123/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17123/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17123/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:10, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/109150
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Tue Mar 25 10:24:01 2025 +0000
> |
> | [committed] libstdc++: Cast -1 to size_t in <format> [PR119429]
> |
> | This avoids a runtime error from Clang's annoying -fsanitize=integer
> | (even though it's not undefined and behaves correctly).
> |
> | ... 5 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 4d1b1969566 libstdc++: Fix handling of common cpp20-only ranges for flat sets [PR119415]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:24, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_build master-aarch64, after:
> | gcc patch https://patchwork.sourceware.org/patch/109141
> | Author: Tobias Burnus <tburnus(a)baylibre.com>
> | Date: Tue Mar 25 10:32:08 2025 +0100
> |
> | [Patch] omp-general.cc: Remove 'if' around call to always 'true' returning function [PR118627]
> |
> | I intent to commit this a bit later today as obvious,
> | unless there are comments.
> |
> | ... 35 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
> Used configuration :
> *CI config* tcwg_gcc_build master-aarch64
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17126/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
We had a "disk full" issue on that machine, sorry for the false alarm.
We can manually retrigger the build if you wish?
Thanks,
Christophe
On Tue, 25 Mar 2025 at 12:22, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_build master-aarch64, after:
> | gcc patch https://patchwork.sourceware.org/patch/109137
> | Author: Sam James <sam(a)gentoo.org>
> | Date: Tue Mar 25 07:54:09 2025 +0000
> |
> | [PATCH] testsuite: add testcase for recent alias fix
> |
> | r15-7961-gdc47161c1f32c3 fixes a typo in ao_compare::compare_ao_refs
> | but there wasn't a testcase available at the time. Now there is.
> |
> | ... 8 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 7679b826840 opcodes: fix wrong code in expand_binop_directly [PR117811]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe gcc:
> | 1
>
> Used configuration :
> *CI config* tcwg_gcc_build master-aarch64
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-precommit/17124/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/3294/artifac…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
Clang 20 has been released and per libc++ policy we want to remove
support for Clang 18. While testing a patch to remove Clang 18 support
[1] I noticed the ARM buildbots you maintain failed [2] since they use
Clang 18.
Would it be possible to update these bots to Clang 20 or Clang 19?
[1] https://github.com/llvm/llvm-project/pull/130142
[2] https://buildkite.com/llvm-project/libcxx-ci/builds/41081
Kind regards,
Mark
Hi,
We have encountered a CI failure on a libc++ CI bot owned by this list. I
am seeking assistance to help debug the issue since it's a bit difficult to
do without having access to that platform. This is time sensitive for us,
since the patch fixes a real issue we encountered and we'd like to get it
fixed in the LLVM 20 release. See
https://github.com/llvm/llvm-project/pull/131921#issuecomment-2737539434
for more details.
Thanks,
Louis
On 21/03/2025 20:36, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_check master-arm, after:
> | commit gcc-15-8649-g1d2257dc850
> | Author: Richard Earnshaw <rearnsha(a)arm.com>
> | Date: Fri Mar 21 15:20:03 2025 +0000
> |
> | arm: testsuite: make unaligned-memcpy-*.c executable tests [PR91614]
> |
> | These tests have been looking for a very specific instruction sequence
> | which has the tendency to be fairly unstable as a result. But what is
> | more interesting is that the the tests must not contain instructions
> | ... 22 lines of the commit log omitted.
>
> Produces 1 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/unaligned-memcpy-4.c scan-assembler-not unaligned
Should be fixed now. The scanner was matching 'unaligned' in a .file directive containing the test name.
R.
>
> Used configuration :
> *CI config* tcwg_gcc_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1545. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3580/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3579/artifact/ar…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=1d2257dc850d088f6d9267b46…
Hello there,
You had previously warned me of the problem with the pre-commit patch, from
which I was able to identify the problem. Unfortunately, I screwed up by
only correcting the cast of 'dim' in three out of four places. Hans-Peter
Nilsson has put it right and I believe that the regression will disappear.
Thanks for your help on this.
Paul
On Sun, 16 Mar 2025 at 13:16, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi cortex-m23 soft, after:
> | commit gcc-15-8035-g7ee31bc9276
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Mar 13 13:34:55 2025 +0000
> |
> | libstdc++: Implement <stdbit.h> for C++26 (P3370R1)
> |
> | This is the first part of the P3370R1 proposal just approved by the
> | committee in Wrocław. This adds C++ equivalents of the functions added
> | to C23 by WG14 N3022.
> | ... 16 lines of the commit log omitted.
>
> Produces 2 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 20_util/stdbit/1.cc -std=gnu++26 (test for excess errors)
> | UNRESOLVED: 20_util/stdbit/1.cc -std=gnu++26 compilation failed to produce executable
>
> Used configuration :
> *CI config* tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.base -mtune=cortex-m23 -mfloat-abi=soft -mfpu=auto
> *configure and test flags:* --target arm-eabi --disable-multilib --with-mode=thumb --with-cpu=cortex-m23 --with-float=soft --target_board=-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto qemu_cpu=cortex-m33
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1543. Please let us know if you have a fix.
All the errors are of the form:
error: 'ULLONG_MAX' was not declared in this scope
but the test includes <limits.h>.
So this target doesn't support long long? Or just doesn't define ULLONG_MAX?
Hi,
Sorry for this issue, I've reverted this in:
https://github.com/llvm/llvm-project/commit/21610e3ecc8bc727f99047e544186b3…
Before I start digging into it further, could you please let me know
what hardware is used to run these tests? I just thought I'd
double-check that the requested -msve-vector-bits=256 does match the
hardware SVE length.
Thanks very much,
Ricardo
On 3/7/25 09:03, ci_notify(a)linaro.org wrote:
> [You don't often get email from ci_notify(a)linaro.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld, after:
> | commit llvmorg-21-init-4020-gf01e760c0836
> | Author: Ricardo Jesus <rjj(a)nvidia.com>
> | Date: Thu Mar 6 09:27:07 2025 +0000
> |
> | [AArch64][SVE] Improve fixed-length addressing modes. (#129732)
> |
> | When compiling VLS SVE, the compiler often replaces VL-based offsets
> | with immediate-based ones. This leads to a mismatch in the allowed
> | addressing modes due to SVE loads/stores generally expecting immediate
> | ... 29 lines of the commit log omitted.
>
> Produces 6235 regressions:
> |
> | regressions.sum:
> | Running test-suite:Fujitsu/C/0000 ...
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0003.test
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0004.test
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0008.test
> | FAIL: test-suite :: Fujitsu/C/0000/Fujitsu-C-0000_0009.test
> | ... and 6513 more
> | # "FAIL" means : the execution of the compiled binary failed / output of the binary differs from the expected one
>
> Used configuration :
> * Toolchain : cmake -G Ninja ../llvm/llvm "-DLLVM_ENABLE_PROJECTS=clang;lld;flang;openmp;clang-tools-extra" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=True -DCMAKE_INSTALL_PREFIX=../llvm-install "-DLLVM_TARGETS_TO_BUILD=AArch64" -DCLANG_DEFAULT_LINKER=lld
> * Testsuite : export LD_LIBRARY_PATH=$\WORKSPACE/llvm-install/lib/aarch64-unknown-linux-gnu$\{LD_LIBRARY_PATH:+:$\LD_LIBRARY_PATH}
> cmake -GNinja -DCMAKE_C_COMPILER="$\WORKSPACE/llvm-install/bin/clang" -DCMAKE_CXX_COMPILER="$\WORKSPACE/llvm-install/bin/clang++" -DCMAKE_Fortran_COMPILER="$\WORKSPACE/llvm-install/bin/flang-new" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS= -DCMAKE_CXX_FLAGS= -DCMAKE_Fortran_FLAGS= -DCMAKE_C_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_CXX_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DCMAKE_Fortran_FLAGS_RELEASE="-O3 -ffast-math -march=armv8.4-a+sve -msve-vector-bits=256 -mllvm -treat-scalable-fixed-error-as-warning=false -flto -fuse-ld=lld -DNDEBUG" -DTEST_SUITE_FORTRAN=ON -DTEST_SUITE_SUBDIRS=Fujitsu "$\WORKSPACE/test/test-suite"
>
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-1592 Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>>
> Fujitsu testsuite : https://github.com/fujitsu/compiler-test-suite/>>
> Current build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>> Reference build : https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…>>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…>>
> Full commit : https://github.com/llvm/llvm-project/commit/f01e760c08365426de95f02dc2c2dc6…>
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please find some details below.
In tcwg_kernel/gnu-master-aarch64-lts-defconfig, after:
| commit gcc-15-8025-g7dae3f64c069
| Author: Richard Sandiford <richard.sandiford(a)arm.com>
| Date: Thu Mar 13 12:03:04 2025 +0000
|
| match.pd: Fold ((X >> C1) & C2) * (1 << C1)
|
| Using a combination of rules, we were able to fold
|
| ((X >> C1) & C2) * (1 << C1) --> X & (C2 << C1)
| ... 22 lines of the commit log omitted.
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 8743
|
| From
| # reset_artifacts:
| -10
| # build_abe binutils:
| -9
| # build_abe stage1:
| -5
| # build_abe qemu:
| -2
| # linux_n_obj:
| 10059
| # linux build successful:
| all
| # linux boot successful:
| boot
Used configuration :
tcwg_kernel/gnu-master-aarch64-lts-defconfig
We track this bug report under https://linaro.atlassian.net/browse/GNU-1539. Please let us know if you have a fix.
If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=7dae3f64c069b942b9abd768f…
On Sun, 2 Mar 2025 at 02:42, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In arm-eabi cortex-m7 hard, after:
> | commit gcc-15-7765-g3866ca796d5
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Feb 27 13:27:17 2025 +0000
> |
> | libstdc++: Fix ranges::move and ranges::move_backward to use iter_move [PR105609]
> |
> | The ranges::move and ranges::move_backward algorithms are supposed to
> | use ranges::iter_move(iter) instead of std::move(*iter), which matters
> | for an iterator type with an iter_move overload findable by ADL.
> | ... 16 lines of the commit log omitted.
>
> Produces 8 regressions:
> |
> | regressions.sum:
> | Running libstdc++:libstdc++-dg/conformance.exp ...
> | FAIL: 25_algorithms/move/constrained.cc -std=gnu++20 (test for excess errors)
> | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++20 compilation failed to produce executable
> | FAIL: 25_algorithms/move/constrained.cc -std=gnu++26 (test for excess errors)
> | UNRESOLVED: 25_algorithms/move/constrained.cc -std=gnu++26 compilation failed to produce executable
> | ... and 4 more
It looks like thumb has some unusual linking requirements that I'm not
familiar with, so undefined functions (which are never actually called
in the test) cause linker errors:
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
undefined reference to `pr105609::iter_move(pr105609::I const&)'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZN8pr1056099iter_moveERKNS_1IE): Unknown destination type
(ARM/Thumb) in /tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/iterator_concepts.h:155:(.text._Z6test06N8pr1056091IE+0x6):
dangerous relocation: unsupported relocation
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
undefined reference to `pr105609::I::operator++()'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZN8pr1056091IppEv): Unknown destination type (ARM/Thumb) in
/tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:326:(.text._Z6test06N8pr1056091IE+0xc):
dangerous relocation: unsupported relocation
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
undefined reference to `pr105609::I::operator==(pr105609::I) const'
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/arm-eabi/bin/ld:
(_ZNK8pr1056091IeqES0_): Unknown destination type (ARM/Thumb) in
/tmp/ccqKQGzN.o
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/x86_64-pc-linux-gnu/arm-eabi/gcc-gcc.git~master-stage2/arm-eabi/libstdc++-v3/include/bits/ranges_algobase.h:323:(.text._Z6test06N8pr1056091IE+0x16):
dangerous relocation: unsupported relocation
I think I should be able to workaround this.
On Thu, 6 Mar 2025 at 23:55, Giuseppe D'Angelo via Gcc-regression
<gcc-regression(a)gcc.gnu.org> wrote:
>
> On 06/03/2025 20:29, ci_notify(a)linaro.org wrote:
> > Dear contributor,
> >
> > Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> This has been fixed on trunk by r15-7863-gd2b022e38a778d.
>
Indeed I can see the test now passes.
Thanks,
Christophe
> Thank you,
> --
> Giuseppe D'Angelo
Hello,
I have recived the email quoted below. I wonder how my patch could have
caused an issue when the only file it touches is related to H8/300
target, not ARM. As far as I can see in the logs you are not building an
H8/300 toolchain.
Best regards,
/J.D.
PS. I am not subscribed so please CC me.
-------- Forwarded Message --------
Subject: [Linaro-TCWG-CI] gcc patch #107213: Failure on aarch64
Date: Fri, 28 Feb 2025 02:06:28 +0000 (UTC)
From: ci_notify(a)linaro.org
Reply-To: linaro-toolchain(a)lists.linaro.org
To: jdx(a)o2.pl
Dear contributor,
Our automatic CI has detected problems related to your patch(es). Please
find some details below.
In simplebootstrap_build master-aarch64-bootstrap, after:
| gcc patch https://patchwork.sourceware.org/patch/107213
| Author: Jan Dubiec <jdx(a)o2.pl>
| Date: Thu Feb 27 22:42:20 2025 +0100
| | [PATCH] H8/300: PR target/109189 Silence -Wformat warnings
on Windows
| | This patch fixes annoying -Wformat warnings when gcc is
built
| on Windows/MinGW64. Instead of %ld it uses HOST_WIDE_INT_PRINT_DEC
| macro, just like many other targets do.
| ... 12 lines of the commit log omitted.
| ... applied on top of baseline commit:
| 8371e7f240c gimple-fold: Fix a pasto in
fold_truth_andor_for_ifcombine [PR119030]
Produces Failure:
| Results changed to
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe bootstrap:
| # FAILED
| | From
| # reset_artifacts:
| -10
| # true:
| 0
| # build_abe bootstrap:
| 1
Used configuration :
*CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
*configure and test flags:* none, autodetected on
aarch64-unknown-linux-gnu
If you have any questions regarding this report, please ask on
linaro-toolchain(a)lists.linaro.org mailing list.
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below contains the details of the failures, and the ways
to reproduce a debug environment:
You can find the failure logs in
*
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
The full lists of regressions and improvements as well as configure and
make commands are in
*
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
Current build :
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
Reference build :
https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
Warning: we do not enable maintainer-mode nor automatically update
generated files, which may lead to failures if the patch modifies the
master files.
Excerpts from ci_notify(a)linaro.org's message of Februar 27, 2025 7:38 pm:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In master-aarch64, after:
> | commit gcc-15-7709-gc2ece13931d
> | Author: Iain Buclaw <ibuclaw(a)gdcproject.org>
> | Date: Tue Feb 25 21:01:23 2025 +0100
> |
> | libphobos: Generate test files for phobos testsuite
> |
> | Extracts all public unittests from libphobos/src and emits them as
> | standalone tests in the testsuite using the tests_extractor script.
> |
> | ... 132 lines of the commit log omitted.
>
> Produces 1 regressions 10 improvements:
> |
> | regressions.sum:
> | Running libphobos:libphobos.phobos/phobos.exp ...
> | FAIL: libphobos.phobos/std_math_hardware.d execution test
> |
> | improvements.sum:
> | Running libphobos:libphobos.phobos/shared/phobos-shared.exp ...
> | FAIL: libphobos.phobos/shared/std/format/internal/floats.d execution test
> | ... and 10 more
>
This just a test that was already failing, it's been renamed from
std/math/hardware.d to std_math_hardware.d in the logs.
Iain.
Hi,
Sorry for this spurious notification, it seems we had a "disk full"
issue on the build machine.
You can ignore this error message.
Christophe
On Fri, 28 Feb 2025 at 03:12, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/107194
> | Author: Vladimir Makarov <vmakarov(a)redhat.com>
> | Date: Thu Feb 27 13:43:37 2025 -0500
> |
> | [pushed][PR118940][LRA]: Add a test
> |
> | The following patch adds a test for
> |
> | https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118940
> | ... 17 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
Hi,
Sorry for this spurious notification, it seems we had a "disk full"
issue on the build machine.
You can ignore this error message.
Christophe
On Fri, 28 Feb 2025 at 03:06, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In simplebootstrap_build master-aarch64-bootstrap, after:
> | gcc patch https://patchwork.sourceware.org/patch/107213
> | Author: Jan Dubiec <jdx(a)o2.pl>
> | Date: Thu Feb 27 22:42:20 2025 +0100
> |
> | [PATCH] H8/300: PR target/109189 Silence -Wformat warnings on Windows
> |
> | This patch fixes annoying -Wformat warnings when gcc is built
> | on Windows/MinGW64. Instead of %ld it uses HOST_WIDE_INT_PRINT_DEC
> | macro, just like many other targets do.
> | ... 12 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 8371e7f240c gimple-fold: Fix a pasto in fold_truth_andor_for_ifcombine [PR119030]
>
> Produces Failure:
> | Results changed to
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | # FAILED
> |
> | From
> | # reset_artifacts:
> | -10
> | # true:
> | 0
> | # build_abe bootstrap:
> | 1
>
> Used configuration :
> *CI config* tcwg_simplebootstrap_build master-aarch64-bootstrap
> *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Current build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
> Reference build : https://ci.linaro.org/job/tcwg_simplebootstrap_build--master-aarch64-bootst…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.