On Sat, 29 Mar 2025 at 22:07, <ci_notify(a)linaro.org> wrote:
>
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_check master-arm, after:
> | gcc patch https://patchwork.sourceware.org/patch/109240
> | Author: Richard Earnshaw <rearnsha(a)arm.com>
> | Date: Wed Mar 26 17:19:11 2025 +0000
> |
> | [PATCH] arm: don't vectorize fmaxf() unless unsafe math opts are enabled
> |
> | This test has presumably been failing since vectorization was enabled
> | at -O2. I suspect part of the reason this wasn't picked up sooner is
> | that the test is a hybrid execution/scan-assembler test and the
> | ... 29 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 876a521a198 OpenMP: Fix declaration in append-args-interop.c test case
>
> Produces 2 regressions 2 improvements:
> |
> | regressions.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vmaxnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1
> | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vminnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1
> |
> | improvements.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vmaxnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1
> | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vminnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1
>
Hi Richard,
I suspect the scripts were confused because there were some bugs in
dg-directives during a few days, leading to random Tcl errors.
You've committed your patch by now anyway, just mentioning in case you
are confused.
Thanks and sorry for the inconvenience,
Christophe
> Used configuration :
> *CI config* tcwg_gcc_check master-arm
> *configure and test flags:* none, autodetected on armv8l-unknown-linux-gnueabihf
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa…
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/11651/artifa…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/3611/artifact/ar…
>
> Warning: we do not enable maintainer-mode nor automatically update
> generated files, which may lead to failures if the patch modifies the
> master files.
On 29/03/2025 23:18, ci_notify(a)linaro.org wrote:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In master-arm, after:
> | commit gcc-15-8965-gb631ff45f23
> | Author: Richard Earnshaw <rearnsha(a)arm.com>
> | Date: Wed Mar 26 15:56:18 2025 +0000
> |
> | arm: don't vectorize fmaxf() unless unsafe math opts are enabled
> |
> | This test has presumably been failing since vectorization was enabled
> | at -O2. I suspect part of the reason this wasn't picked up sooner is
> | that the test is a hybrid execution/scan-assembler test and the
> | ... 29 lines of the commit log omitted.
>
> Produces 2 regressions 2 improvements:
> |
> | regressions.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vmaxnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1
> | FAIL: gcc.target/arm/vect-fmaxmin.c scan-assembler-times vminnm.f32\tq[0-9]+, q[0-9]+, q[0-9]+ 1
> |
Fixed with r15-9064-gf30e180194bfbc
R.
> | improvements.sum:
> | Running gcc:gcc.target/arm/arm.exp ...
> | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vminnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1
> | FAIL: gcc.target/arm/fmaxmin.c scan-assembler-times vmaxnm.f32\ts[0-9]+, s[0-9]+, s[0-9]+ 1
>
> Used configuration :
> *CI config* tcwg_gnu_cross_check_gcc master-arm
> *configure and test flags:* --target arm-linux-gnueabihf
>
> We track this bug report under https://linaro.atlassian.net/browse/GNU-1553. Please let us know if you have a fix.
>
> If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list.
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
>
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
>
> You can find the failure logs in *.log.1.xz files in
> * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a…
> The full lists of regressions and improvements as well as configure and make commands are in
> * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a…
> The list of [ignored] baseline and flaky failures are in
> * https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a…
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1998/a…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_cross_check_gcc--master-arm-build/1997/a…
>
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=b631ff45f231db55b28b4c92c…
ci_notify(a)linaro.org writes:
> Dear contributor,
>
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
>
> In gcc_check master-aarch64, after:
> | commit gcc-15-8956-ge90d6c2639c
> | Author: Sam James <sam(a)gentoo.org>
> | Date: Thu Mar 27 00:21:43 2025 +0000
> |
> | testsuite: more (mostly cosmetic) dg- whitespace fixes
> |
> | Some of these are harmless but still inconsistent (and asking for trouble
> | given it may give people the wrong idea about similar "style").
> |
> | ... 9 lines of the commit log omitted.
>
> Produces 8 regressions:
> |
> | regressions.sum:
> | Running gcc:gcc.target/aarch64/aarch64.exp ...
> | ERROR: tcl error code NONE
> | ERROR: tcl error sourcing gcc.target/aarch64/aarch64.exp.
> | UNRESOLVED: testcase gcc.target/aarch64/aarch64.exp' aborted due to Tcl error
> | ERROR: unmatched open brace in list
> | ... and 5 more
Should be fixed with r15-8981-g176c7a2f751e04, thanks!
The tree dump had bogus tailing numbers: interop.[0-9]+3, interop.[0-9]+2
This happened to work with x86-64 (-m32, -m64) but not with aarch64.
I committed inr15-9033-ge0886d8ad4c519 the obvious fix: remove the 3 and 2 after the '+'
Tobias
ci_notify(a)linaro.org wrote:
> In gcc_check master-aarch64, after:
> | commit gcc-15-8972-g7e286b56545
>
> We track this bug report underhttps://linaro.atlassian.net/browse/GNU-1554. Please let us know if you have a fix.
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.