> -----Original Message-----
> From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
> Sent: Thursday, August 22, 2024 10:30 AM
> To: rguenth(a)gcc.gnu.org
> Cc: gcc-regression(a)gcc.gnu.org; Andrew Pinski (QUIC)
> <quic_apinski(a)quicinc.com>
> Subject: [Linaro-TCWG-CI] gcc-15-3087-gb07f8a30115: FAIL: 2
> regressions on aarch64
>
> Dear contributor, our automatic CI has detected problems
> related to your patch(es). Please find some details below. If
> you have any questions, please follow up on linaro-
> toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg
> channel, or ping your favourite Linaro toolchain developer on
> the usual project channel.
>
> We appreciate that it might be difficult to find the necessary
> logs or reproduce the issue locally. If you can't get what you
> need from our CI within minutes, let us know and we will be
> happy to help.
>
> We track this report status in
> https://linaro.atlassian.net/browse/GNU-1317 , please let us
> know if you are looking at the problem and/or when you have
> a fix.
I have filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116463 for the failure (which was a missed optimization even before the patch; the detection of vector complex multiply is very sensitive in changes to the IR differences).
Thanks,
Andrew Pinski
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-15-3087-gb07f8a30115
> | Author: Andrew Pinski <quic_apinski(a)quicinc.com>
> | Date: Wed Aug 21 17:41:38 2024 -0700
> |
> | fold: Fix `a * 1j` if a has side effects [PR116454]
> |
> | The problem here was a missing save_expr around arg0
> since
> | it is used twice, once in REALPART_EXPR and once in
> IMAGPART_EXPR.
> | Thia adds the save_expr and reformats the code slightly
> so it is a
> | little easier to understand. It excludes the case when arg0
> is
> | a COMPLEX_EXPR since in that case we'll end up with the
> distinct
> | ... 19 lines of the commit log omitted.
>
> FAIL: 2 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/vect/complex/complex.exp ...
> FAIL: gcc.dg/vect/complex/fast-math-complex-mls-double.c
> scan-tree-dump vect "Found COMPLEX_FMA"
> FAIL: gcc.dg/vect/complex/fast-math-complex-mls-float.c
> scan-tree-dump vect "Found COMPLEX_FMA"
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/2486/artifact/artifacts/00-sumfiles/
> 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/2486/artifact/artifacts/notify/
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-
> build/2486/artifact/artifacts/sumfiles/xfails.xfail
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<---
> -----------------------
> The information below can be used to reproduce a debug
> environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--
> master-aarch64-build/2486/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--
> master-aarch64-build/2485/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/b07f8a301158e53717b8688cc8ea
> 430b6f02574c/tcwg_gcc_check/master-
> aarch64/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/b07f8a301158e53717b8688cc8ea430b6f0
> 2574c
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 2 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/b07f8a301158e53717b8688cc8ea
> 430b6f02574c/tcwg_gcc_check/master-aarch64/details.txt
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-
> aarch64-build/2486/artifact/artifacts
This is already recorded as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116409 . I am about to submit a v2 of the patch to fix this too.
> -----Original Message-----
> From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
> Sent: Tuesday, August 20, 2024 8:34 AM
> To: Andrew Pinski (QUIC) <quic_apinski(a)quicinc.com>
> Cc: gcc-regression(a)gcc.gnu.org
> Subject: [Linaro-TCWG-CI] gcc-15-2986-gcd2f394418b: Failure
> on aarch64
>
> Dear contributor, our automatic CI has detected problems
> related to your patch(es). Please find some details below. If
> you have any questions, please follow up on linaro-
> toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg
> channel, or ping your favourite Linaro toolchain developer on
> the usual project channel.
>
> We appreciate that it might be difficult to find the necessary
> logs or reproduce the issue locally. If you can't get what you
> need from our CI within minutes, let us know and we will be
> happy to help.
>
> We track this report status in
> https://linaro.atlassian.net/browse/GNU-1316 , please let us
> know if you are looking at the problem and/or when you have
> a fix.
>
> In master-aarch64 after:
>
> | commit gcc-15-2986-gcd2f394418b
> | Author: Andrew Pinski <quic_apinski(a)quicinc.com>
> | Date: Sat Apr 20 00:13:12 2024 -0700
> |
> | PHIOPT: move factor_out_conditional_operation over to
> use gimple_match_op
> |
> | To start working on more with expressions with more
> than one operand, converting
> | over to use gimple_match_op is needed.
> | The added side-effect here is
> factor_out_conditional_operation can now support
> | builtins/internal calls that has one operand without any
> extra code added.
> |
> | ... 20 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe binutils:
> 1
> # build_abe gcc:
> 2
> # build_abe linux:
> 4
> # build_abe glibc:
> # FAILED
> # build_abe gdb:
> # First few build errors in logs:
> # 00:02:13 ../sysdeps/ieee754/dbl-64/e_hypot.c:146:1:
> internal compiler error: in factor_out_conditional_operation,
> at tree-ssa-phiopt.cc:407 # 00:02:13 make[2]: ***
> [/home/tcwg-
> buildslave/workspace/tcwg_gnu_2/abe/builds/aarch64-
> unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-
> glibc.git~master/sysd-rules:553: /home/tcwg-
> buildslave/workspace/tcwg_gnu_2/abe/builds/aarch64-
> unknown-linux-gnu/aarch64-unknown-linux-gnu/glibc-
> glibc.git~master/math/e_hypot.o] Error 1 # 00:02:13 make[1]:
> *** [Makefile:484: math/others] Error 2 # 00:02:13 make: ***
> [Makefile:9: all] Error 2
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe binutils:
> 1
> # build_abe gcc:
> 2
> # build_abe linux:
> 4
> # build_abe glibc:
> 5
> # build_abe gdb:
> 6
>
> The configuration of this build is:
> CI config tcwg_gnu_native_build master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<---
> -----------------------
> The information below can be used to reproduce a debug
> environment:
>
> Current build :
> https://ci.linaro.org/job/tcwg_gnu_native_build--master-
> aarch64-build/747/artifact/artifacts
> Reference build :
> https://ci.linaro.org/job/tcwg_gnu_native_build--master-
> aarch64-build/746/artifact/artifacts
>
> Reproduce last good and first bad builds: https://git-
> us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/cd2f394418be0cc15d05c97ed725
> 67f2f5e15172/tcwg_gnu_native_build/master-
> aarch64/reproduction_instructions.txt
>
> Full commit : https://github.com/gcc-
> mirror/gcc/commit/cd2f394418be0cc15d05c97ed72567f2f5e1
> 5172
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_native_build
> ** master-aarch64
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-
> commits.git/plain/gcc/sha1/cd2f394418be0cc15d05c97ed725
> 67f2f5e15172/tcwg_gnu_native_build/master-
> aarch64/details.txt
> *** https://ci.linaro.org/job/tcwg_gnu_native_build--master-
> aarch64-build/747/artifact/artifacts
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1312 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig after:
| commit binutils-2_41-release-3996-g6ae8a30d44f
| Author: Jan Beulich <jbeulich(a)suse.com>
| Date: Fri Aug 9 11:59:31 2024 +0200
|
| gas: have scrubber retain more whitespace
|
| According to the description of the state machine, the expectation
| appears to be that (leaving aside labels) any insn mnemonic or
| directive would be followed by a comma separated list of operands. That
| may have been true very long ago, but the latest with the advent of more
| elaborate macros this isn't rhe case anymore. Neither macro parameters
| ... 26 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
8104
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
9328
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-aarch64-lts-defconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used 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…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
Full commit : https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=6ae8a30d44f01…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-aarch64-lts-defconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
Hi Julian,
Your patch below breaks Flang build [on aarch64]. Would you please investigate?
The interesting log is at https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/174/artifact… .
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
> On Aug 5, 2024, at 16:56, ci_notify(a)linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/LLVM-1306 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_flang_build/main-aarch64 after:
>
> | commit llvmorg-20-init-1360-ga42e515e3a9f
> | Author: Julian Brown <julian.brown(a)amd.com>
> | Date: Mon Aug 5 12:37:07 2024 +0100
> |
> | [OpenMP] OpenMP 5.1 "assume" directive parsing support (#92731)
> |
> | This is a minimal patch to support parsing for "omp assume" directives.
> | These are meant to be hints to a compiler's optimisers: as such, it is
> | legitimate (if not very useful) to ignore them. The patch builds on top
> | of the existing support for "omp assumes" directives (note spelling!).
> |
> | ... 8 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
> # FAILED
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_llvm -- clang;lld;flang;openmp;clang-tools-extra :
> 1
>
> The configuration of this build is:
> CI config tcwg_flang_build/main-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/174/artifact…
> Reference build : https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/172/artifact…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/a42e515e3a9f3bb4e44389c097b8910…
>
> List of configurations that regressed due to this commit :
> * tcwg_flang_build
> ** main-aarch64
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
> *** https://ci.linaro.org/job/tcwg_flang_build--main-aarch64-build/174/artifact…
ci_notify(a)linaro.org writes:
> Dear contributor, our automatic CI has detected problems related to
> your patch(es). Please find some details below. If you have any
> questions, please follow up on linaro-toolchain(a)lists.linaro.org
> mailing list, Libera's #linaro-tcwg channel, or ping your favourite
> Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or
> reproduce the issue locally. If you can't get what you need from our
> CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1305 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-aarch64 after:
>
> | commit gcc-15-2414-g2d105efd6f60
> | Author: Sam James <sam(a)gentoo.org>
> | Date: Tue Jul 30 17:10:01 2024 +0100
> |
> | testsuite: fix whitespace in dg-do assemble directive
> |
> | * gcc.target/aarch64/simd/vmmla.c: Fix whitespace in dg directive.
>
> FAIL: 3 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.target/aarch64/simd/simd.exp ...
> UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\tsmmla\\tv[0-9]+.4s, v[0-9]+.16b, v[0-9]+.16b 1
> UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\tummla\\tv[0-9]+.4s, v[0-9]+.16b, v[0-9]+.16b 1
> UNRESOLVED: gcc.target/aarch64/simd/vmmla.c scan-assembler-times \\tusmmla\\tv[0-9]+.4s, v[0-9]+.16b, v[0-9]+.16b 1
> [...]
Thanks. The test has been broken since it was added.
Filed https://gcc.gnu.org/PR116207.
Hi Leandro,
Our Flang CI is running in test mode, and it already catches regressions!
> On Aug 1, 2024, at 01:27, ci_notify(a)linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/LLVM-1300 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld after:
>
> | commit llvmorg-20-init-943-g366eade911b5
> | Author: Leandro Lupori <leandro.lupori(a)linaro.org>
> | Date: Wed Jul 31 14:39:06 2024 -0300
> |
> | [flang][OpenMP] Reland Fix copyprivate semantic checks (#95799) (#101009)
> |
> | There are some cases in which variables used in OpenMP constructs
> | are predetermined as private. The semantic checks for copyprivate
> | were not handling those cases.
> |
> | Besides that, shared symbols were not being properly represented
> | ... 9 lines of the commit log omitted.
>
> FAIL: 7 regressions: 7 improvements
>
> regressions.sum:
> === test-suite tests ===
>
> Running test-suite:Fujitsu/Fortran/0141 ...
> FAIL: test-suite :: Fujitsu/Fortran/0141/Fujitsu-Fortran-0141_0019.test
This means that after your patch the test that could not compile before, now compiles, but fails to run correctly. This is an improvement.
>
> Running test-suite:Fujitsu/Fortran/0153 ...
> NOEXE: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0234.test
> NOEXE: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0235.test
> NOEXE: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0237.test
These tests go the other way -- they used to fail at runtime before, but now they fail to compile.
>
> ... and 5 more entries
>
> improvements.sum:
> === test-suite tests ===
>
> Running test-suite:Fujitsu/Fortran/0141 ...
> NOEXE: test-suite :: Fujitsu/Fortran/0141/Fujitsu-Fortran-0141_0019.test
>
> Running test-suite:Fujitsu/Fortran/0153 ...
> FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0237.test
> FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0234.test
> FAIL: test-suite :: Fujitsu/Fortran/0153/Fujitsu-Fortran-0153_0235.test
>
> ... and 5 more entries
Please investigate, and let me know if you need any help in reproducing or troubleshooting these.
Thanks!
--
Maxim Kuvyrkov
https://www.linaro.org
>
> 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…
>
> The configuration of this build is:
> CI config tcwg_flang_test/main-aarch64-Ofast-sve_vls-lto-lld
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> 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…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/366eade911b54878c9cc1835d2544fb…
>
> List of configurations that regressed due to this commit :
> * tcwg_flang_test
> ** main-aarch64-Ofast-sve_vls-lto-lld
> *** FAIL: 7 regressions: 7 improvements
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
> *** https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vls-lto-l…
Hi all,
what should I do with this – I have no idea what artifacts are nor is it
clear to me when looking at the webpage.
Tobias
ci_notify(a)linaro.org wrote:
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In gcc_check master-aarch64 after:
>
> | gcc patch https://patchwork.sourceware.org/patch/94612
> | Author: Tobias Burnus <tburnus(a)baylibre.com>
> | Date: Fri Jul 26 20:05:43 2024 +0200
> |
> | libgomp: Fix declare target link with offset array-section mapping [PR116107]
> |
> | The main idea of 'link' is to permit putting only a subset of a
> | huge array on the device. Well, in order to make this work properly,
> | it requires that one can map an array section, which does not
> | start with the first element.
> |
> | ... 28 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 6d79d53eed8 Match: Support .SAT_SUB with IMM op for form 1-4
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 2 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/7257/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2370/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 Andi,
The regression is ...
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: c-c++-common/musttail12.c -std=c++14 (test for excess errors)
FAIL: c-c++-common/musttail12.c -std=c++17 (test for excess errors)
FAIL: c-c++-common/musttail12.c -std=c++20 (test for excess errors)
FAIL: g++.dg/musttail6.C (test for excess errors)
It wasn't included in the report due to typo in the scripts.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 26, 2024, at 19: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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1299 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-2233-g8d1af8f904a
> | Author: Andi Kleen <ak(a)linux.intel.com>
> | Date: Tue Jan 23 23:54:56 2024 -0800
> |
> | Add tests for C/C++ musttail attributes
> |
> | Some adopted from the existing C musttail plugin tests.
> | Also extends the ability to query the sibcall capabilities of the
> | target.
> |
> | gcc/testsuite/ChangeLog:
> | ... 16 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 4 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2460/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2459/artifact/ar…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/8d1af8f904a0c08656d976cbf8ca56dba3…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2460/artifact/ar…
Hi Jason,
For this one the regressions are:
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++20 (test for excess errors)
FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++23 (test for excess errors)
FAIL: g++.dg/cpp2a/consteval-prop21.C -std=c++26 (test for excess errors)
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 28, 2024, at 09:28, ci_notify(a)linaro.org wrote:
>
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1301 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-2362-ga9e9f772c748
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Fri Jul 26 17:20:18 2024 -0400
> |
> | c++: consteval propagation and templates [PR115986]
> |
> | Here the call to e() makes us decide to check d() for escalation at EOF, but
> | while checking it we try to fold_immediate 0_c, and get confused by the
> | template trees. Let's not mess with escalation for function templates.
> |
> | PR c++/115986
> | ... 9 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 3 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2472/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2471/artifact/ar…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/a9e9f772c7488ac0c09dd92f28890bdab9…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2472/artifact/ar…
Hi Jason,
The regression is ...
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: g++.dg/abi/arm_rtti1.C -std=gnu++26 scan-assembler _ZNKSt9type_infoeqERKS_
It wasn't included in the report due to typo in the scripts.
Kind regards,
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jul 28, 2024, at 05: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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/GNU-1300 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In gcc_check master-arm after:
>
> | commit gcc-15-2360-gdab0f35fcb4d
> | Author: Jason Merrill <jason(a)redhat.com>
> | Date: Fri Jul 26 15:10:50 2024 -0400
> |
> | c++: improve C++ testsuite default versions
> |
> | I wanted to add more cases to the setting of std_list in g++-dg.exp, but
> | didn't want to do a full scan through the file for each case. So this patch
> | improves that in two ways: first, by extracting all interesting lines on a
> | single pass; second, by generating the list more flexibly: now we test every
> | version mentioned explicitly in the testcase, plus a few more if fewer than
> | ... 12 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
> # 1 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gcc:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gcc --:
> 0
>
> The configuration of this build is:
> CI config tcwg_gcc_check master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2468/artifact/ar…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2466/artifact/ar…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
>
> Full commit : https://github.com/gcc-mirror/gcc/commit/dab0f35fcb4dd3ba584422013096c4ebc6…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-arm
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2468/artifact/ar…
On 2024-07-27 03: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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In gdb_check master-aarch64 after:
>
> | 2 patches in gdb
> | Patchwork URL: https://patchwork.sourceware.org/patch/94605
> | 9aca4cc6ec5 gdb: pass inferior to gdbarch_update_p
> | f3b21ad781e gdb: pass inferior to target_current_description
> | ... applied on top of baseline commit:
> | ced7ecee432 Automatic date update in version.in
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe gdb -- --prefix /usr --disable install:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1:
> 0
> # 1 regressions
>
> From
> # reset_artifacts:
> -10
> # build_abe gdb -- --prefix /usr --disable install:
> -2
> # build_abe dejagnu:
> -1
> # build_abe check_gdb -- --set check_buffer_workaround=gdb-read1:
> 0
>
> The configuration of this build is:
> CI config tcwg_gdb_check master-aarch64
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-precommit/2974/art…
> Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-aarch64-build/1474/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.
Hello,
Could you help me understand what failed?
Simon
On Mon, Jul 22, 2024 at 02:12:58PM +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. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> We track this report status in https://linaro.atlassian.net/browse/LLVM-1287 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig after:
>
> | commit llvmorg-19-init-18145-g1f6f97e2b64a
> | Author: Bill Wendling <5993918+bwendling(a)users.noreply.github.com>
> | Date: Thu Jul 18 22:11:56 2024 +0000
> |
> | [Clang] Loop over FieldDecls instead of all Decls (#99574)
> |
> | Only FieldDecls are important when determining GEP indices. A struct
> | defined within another struct has the same semantics as if it were
> | defined outside of the struct. So there's no need to look into
> | RecordDecls that aren't a field.
> |
> | ... 4 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 22903
>
> From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 22904
>
> The configuration of this build is:
> CI config tcwg_kernel/llvm-master-aarch64-stable-allyesconfig
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon…
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon…
>
> Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
>
> Full commit : https://github.com/llvm/llvm-project/commit/1f6f97e2b64a9c4c51712d32b53e07d…
>
> List of configurations that regressed due to this commit :
> * tcwg_kernel
> ** llvm-master-aarch64-stable-allyesconfig
> *** Failure
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/s…
> *** https://ci.linaro.org/job/tcwg_kernel--llvm-master-aarch64-stable-allyescon…
This should be fixed with
https://github.com/llvm/llvm-project/commit/6db5f4fd2a287de9d20adc7a44cfcc6….
Cheers,
Nathan
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1297 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-aarch64-mainline-allnoconfig after:
| commit gcc-15-2192-g0c5c0c959c2e
| Author: Tamar Christina <tamar.christina(a)arm.com>
| Date: Mon Jul 22 10:28:19 2024 +0100
|
| AArch64: implement TARGET_VECTORIZE_CONDITIONAL_OPERATION_IS_EXPENSIVE [PR115531].
|
| This implements the new target hook indicating that for AArch64 when possible
| we prefer masked operations for any type vs doing LOAD + SELECT or
| SELECT + STORE.
|
| Thanks,
| ... 16 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
662
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
669
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-aarch64-mainline-allnoconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/0c5c0c959c2e592b84739f19ca771fa69e…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-aarch64-mainline-allnoconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-mainline-allnocon…
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1294 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-arm-next-defconfig after:
| commit gcc-15-2110-g71b31690a7c5
| Author: Richard Sandiford <richard.sandiford(a)arm.com>
| Date: Wed Jul 17 19:38:11 2024 +0100
|
| rtl-ssa: Fix split_clobber_group [PR115928]
|
| One of the goals of the rtl-ssa representation was to allow a
| group of consecutive clobbers to be skipped in constant time,
| with amortised sublinear insertion and deletion. This involves
| putting consecutive clobbers in groups. Splitting or joining
| groups would be linear if we had to update every clobber on
| ... 21 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
0
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
7865
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-arm-next-defconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/71b31690a7c52413496e91bcc5ee4c68af…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-arm-next-defconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-next-defconfig-build/…
FAIL: gcc.dg/pr116003.c (test for excess errors)
Excess errors:
/home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:4:1: sorry, unimplemented: '_BitInt(5)' is not supported on this target
/home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:8:1: sorry, unimplemented: '_BitInt(129)' is not supported on this target
/home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/snapshots/gcc.git~master/gcc/testsuite/gcc.dg/pr116003.c:11:5: sorry, unimplemented: '_BitInt(128)' is not supported on this target
I think it needs dg-do compile { target bitint }.
Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
We track this report status in https://linaro.atlassian.net/browse/GNU-1282 , please let us know if you are looking at the problem and/or when you have a fix.
In CI config tcwg_kernel/gnu-master-aarch64-lts-allmodconfig after:
| commit gcc-15-2026-g44c9403ed183
| Author: Alejandro Colomar <alx(a)kernel.org>
| Date: Sat Jun 29 15:10:43 2024 +0200
|
| c, objc: Add -Wunterminated-string-initialization
|
| Warn about the following:
|
| char s[3] = "foo";
|
| Initializing a char array with a string literal of the same length as
| ... 63 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
24546
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
24548
The configuration of this build is:
CI config tcwg_kernel/gnu-master-aarch64-lts-allmodconfig
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/44c9403ed1833ae71a59e84f9e37af3182…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-aarch64-lts-allmodconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-allmodconfig-…
Hi there,
You detected a failure in gfortran.dg/class_transformational_2.f90:
PASS: gfortran.dg/class_transformational_2.f90 -O0 (test for excess
errors)
PASS: gfortran.dg/class_transformational_2.f90 -O0 execution test
PASS: gfortran.dg/class_transformational_2.f90 -O1 (test for excess
errors)
FAIL: gfortran.dg/class_transformational_2.f90 -O1 execution test
PASS: gfortran.dg/class_transformational_2.f90 -O2 (test for excess
errors)
PASS: gfortran.dg/class_transformational_2.f90 -O2 execution test
PASS: gfortran.dg/class_transformational_2.f90 -O3 -fomit-frame-pointer
...snip...
PASS: gfortran.dg/class_transformational_2.f90 -O3 -fomit-frame-pointer
...snip...
PASS: gfortran.dg/class_transformational_2.f90 -O3 -g (test for excess
errors)
PASS: gfortran.dg/class_transformational_2.f90 -O3 -g execution test
PASS: gfortran.dg/class_transformational_2.f90 -Os (test for excess
errors)
PASS: gfortran.dg/class_transformational_2.f90 -Os execution test
The stop message in the full log indicates a numeric error in the first
test. I am unable to reproduce the error. Adding deallocation of all the
allocated variables (which I should have done in the first place) and
running valgrind with -s shows no errors and no memory loss.
I find it odd that it should fail once at -O1 and not at -O2 and higher.
Can you provide me with any insights; eg, by rerunning the testcase outside
of the dejagnu framework?
Thank you for doing this testing, by the way, even if the failure is a bit
obscure at the moment.
Best regards
Paul
I get this problem when the CI is building a patchset for the binutils
with my patches.
The patchset consists of 7 patches, and I suspect that this error message
is generated when only part of the 7 patches are applied.
Could this be true?
They are interdependent, so there is no way to reorder the patches to make
this work if not all the patches are applied.
Den 2024-07-07 kl. 02:47, skrev ci_notify(a)linaro.org:
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain(a)lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel.
>
> We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help.
>
> In binutils_build master-arm after:
>
> | 2 patches in binutils
> | Patchwork URL: https://patchwork.sourceware.org/patch/93436
> | dd57e0ed6f6 ldgram.y: Add ASCII parsing
> | 304119944bb ldlex.l: Add ASCII token
> | ... applied on top of baseline commit:
> | 85a67d0a39a Automatic date update in version.in
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe binutils:
> # FAILED
> # First few build errors in logs:
> # 00:01:58 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/binutils.git~master/ld/ldgram.y:711:21: error: too many arguments to function ‘lang_add_string’
> # 00:01:58 /home/tcwg-build/workspace/tcwg_gnu_2/abe/snapshots/binutils.git~master/ld/ldgram.y:717:19: error: too many arguments to function ‘lang_add_string’
> # 00:01:58 make[4]: *** [Makefile:2290: ldgram.o] Error 1
> # 00:01:58 make[3]: *** [Makefile:1903: all-recursive] Error 1
> # 00:01:58 make[2]: *** [Makefile:1092: all] Error 2
> # 00:01:58 make[1]: *** [Makefile:8044: all-ld] Error 2
> # 00:01:58 make: *** [Makefile:1028: all] Error 2
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe binutils:
> 1
>
> The configuration of this build is:
> CI config tcwg_binutils_build master-arm
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-precommit/2298/ar…
> Reference build : https://ci.linaro.org/job/tcwg_binutils_build--master-arm-build/1304/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.
--
Best Regards
Ulf Samuelsson
Greetings!
This is Mingming and I'm an LLVM contributor. I have received a lot of
useful code review feedback from aarch64 experts. Thank you for all of that!
I'm writing to report a failure (
https://lab.llvm.org/buildbot/#/builders/122/builds/150) on buildbot
clang-armv8-lld-2stage triggered by my recent patch. The issue seems to
stem from the C++ standard libraries not being configured in the buildbot
environment.
While using a c-style header is a workaround (which pr 97245
<https://github.com/llvm/llvm-project/pull/97245> did), @petrhosek reminded
me that it would be good to inform maintainers so they can take a look,
which makes sense to me.
Could someone please assist in resolving this configuration problem?
Thank you in advance and let me know if I miss anything.
Thanks, Mingming