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