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 understand 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-1329 , please let us know if you are looking at the problem and/or when you have a fix.
In arm-eabi cortex-m33 hard after:
| commit binutils-2_41-release-4187-g31ed3a9d691
| Author: Christophe Lyon <christophe.lyon(a)linaro.org>
| Date: Wed Jun 19 12:35:30 2024 +0000
|
| arm: Do not insert stubs needing Arm code on Thumb-only cores.
|
| We recently fixed a bug in libgcc
| (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115360)
| where a symbol was missing a %function .type decoration.
|
| This meant the linker would silently pick the wrong type of 'farcall
| ... 48 lines of the commit log omitted.
FAIL: 72074 regressions: 94 improvements
regressions.sum:
=== g++ tests ===
Running g++:g++.dg/analyzer/analyzer.exp ...
FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++17 (test for excess errors)
FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++26 (test for excess errors)
FAIL: c-c++-common/analyzer/pr98580-a.c -std=c++98 (test for excess errors)
Running g++:g++.dg/compat/compat.exp ...
FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o link
FAIL: g++.dg/compat/abi/bitfield2 cp_compat_x_tst.o-cp_compat_y_tst.o link
... and 72156 more entries
improvements.sum:
=== g++ tests ===
Running g++:g++.dg/dg.exp ...
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++98 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++17 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-3.C -std=c++26 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++98 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++26 execution test
FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-4.C -std=gnu++17 execution test
=== gcc tests ===
... and 104 more entries
You can find the failure logs in *.log.1.xz files in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_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_m33_hard_e…
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
The configuration of this build is:
CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv8-m.main+dsp+fp -mtune=cortex-m33 -mfloat-abi=hard -mfpu=auto
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
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=31ed3a9d69149…
List of configurations that regressed due to this commit :
* tcwg_gnu_embed_check_gcc
** master-thumb_m33_hard_eabi
*** FAIL: 72074 regressions: 94 improvements
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/binuti…
*** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m33_hard_e…
On Wed, Sep 04, 2024 at 10:36:41PM +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 understand 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-1339 , 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-next-allyesconfig after:
>
> | commit v6.11-rc1-143-g4e7795eda4459
> | Author: Kent Overstreet <kent.overstreet(a)linux.dev>
> | Date: Sun Sep 1 18:08:25 2024 -0400
> |
> | bcachefs: bch2_sb_member_alloc()
> |
> | refactoring
> |
> | Signed-off-by: Kent Overstreet <kent.overstreet(a)linux.dev>
Thanks for the report, this should be fixed now:
https://git.kernel.org/next/linux-next/c/da6e6a70084d99d522058bbef00b9cbe48…
Cheers,
Nathan
Hi,
Can I get a reduced .ll showing the regression, or some reduced steps for
reproducing the bug? I suspect the bug is elsewhere, and not in the commit
itself.
Warm regards,
Ram
On Thu, Sep 5, 2024 at 3:39 AM <ci_notify(a)linaro.org> wrote:
> Dear contributor, our automatic CI has detected problems related to your
> patch(es). Please find some details below. 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 understand 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-1340 , 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_vla after:
>
> | commit llvmorg-20-init-4622-g16900d3b98e6
> | Author: Ramkumar Ramachandra <ramkumar.ramachandra(a)codasip.com>
> | Date: Wed Sep 4 22:01:04 2024 +0100
> |
> | LICM: hoist BO assoc when BinOp is in RHS (#107072)
> |
> | Extend hoistBOAssociation smoothly to handle the case when the
> inner
> | BinaryOperator is in the RHS of the outer BinaryOperator. This
> completes
> | the generalization of hoistBOAssociation, and the only limitation
> after
> | this patch is the fact that only Add and Mul are hoisted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === test-suite tests ===
>
> Running test-suite:Fujitsu/Fortran/0354 ...
> FAIL: test-suite :: Fujitsu/Fortran/0354/Fujitsu-Fortran-0354_0334.test
>
>
> You can find the failure logs in *.log.1.xz files in
> -
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The full lists of regressions and improvements as well as configure and
> make commands are in
> -
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
> The list of [ignored] baseline and flaky failures are in
> -
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> The configuration of this build is:
> CI config tcwg_flang_test/main-aarch64-Ofast-sve_vla
>
>
> -----------------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_vla-build…
> Reference build :
> https://ci.linaro.org/job/tcwg_flang_test--main-aarch64-Ofast-sve_vla-build…
>
> 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/16900d3b98e6c8fbdad4411a054e356…
>
> List of configurations that regressed due to this commit :
> * tcwg_flang_test
> ** main-aarch64-Ofast-sve_vla
> *** FAIL: 1 regressions
> ***
> 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_vla-build…
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-1324 , 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 gcc-15-3256-g1c4b9826bd0
| Author: Filip Kastl <fkastl(a)suse.cz>
| Date: Wed Aug 28 15:47:44 2024 +0200
|
| gimple ssa: switchconv: Use __builtin_popcount and support more types in exp transform [PR116355]
|
| The gen_pow2p function generates (a & -a) == a as a fallback for
| POPCOUNT (a) == 1. Not only is the bitmagic not equivalent to
| POPCOUNT (a) == 1 but it also introduces UB (consider signed
| a = INT_MIN).
|
| ... 43 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:
9328
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
9330
# 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/gcc/sh…
Full commit : https://github.com/gcc-mirror/gcc/commit/1c4b9826bd0d5ac471543c68f097d80b19…
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/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-aarch64-lts-defconfig-bui…
* ci notify:
> 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 understand 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 glibc_check master-arm after:
>
> | 4 patches in glibc
> | Patchwork URL: https://patchwork.sourceware.org/patch/96984
> | 11d52d986b elf: Reorder audit events in dlcose to match _dl_fini (bug 32066)
> | 7b2cd1e545 elf: Call la_objclose for proxy link maps in _dl_fini (bug 32065)
> | 0f79eb4a6f elf: Signal la_objopen for the proxy link map in dlmopen (bug 31985)
> | f26a9b6323 elf: Always write audit log to elf/tst-audit23.out
> | ... applied on top of baseline commit:
> | 96d0bf98ca Add support/ code for checking file contents
>
> FAIL: 1 regressions
>
> regressions.sum:
> === glibc tests ===
>
> Running glibc:elf ...
> FAIL: elf/tst-audit23
Adhemerval, does elf/tst-audit23.out now show more details?
Thanks,
Florian
> -----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
Progress:
* UM-2 [QEMU upstream maintainership]
- patch-review queue has filled up again; reviewed at least some patches
ready for an arm pullreq
- another KVM Forum PC meeting
* QEMU-530 [QEMU ARMv9.5 Baseline CPU for TCG]
- realized that FEAT_AFP means we need to refactor our FPCR/FPSR
implementation, because it adds new AArch64-only bits that aren't
visible in the AArch32 FPSCR format. (QEMU for historical reasons
implemented FPCR and FPSR as masked views of FPSCR; now we need
to switch to having FPSCR be a view of the FPCR/FPSR data.)
Wrote the necessary refactoring and sent patchseries out for review.
-- PMM
I think we need to revert this.
I got this email from linaro/gcc-regressions:
[Linaro-TCWG-CI] gcc-15-1649-g19f630e6ae8d: FAIL: 2 regressions on aarch64
regressions.sum:
=== gcc tests ===
Running gcc:gcc.misc-tests/gcov.exp ...
FAIL: gcc.misc-tests/gcov-23.c (internal compiler error: in operator[],
at vec.h:910)
FAIL: gcc.misc-tests/gcov-23.c (test for excess errors)
This did not reproduce on my machine, but I took a quick look at the
hash-map implementation. hash_map.put calls
hash_table.find_slot_with_hash, which calls hash_table.expand, which
does move+destroy. auto_vec is not really move-aware which leads to a
double-free.
The fix is either to make auto_vec move-aware (and more like C++'s
std::vector) or revert this patch and apply the original version with an
explicit release.
OK?
Thanks,
Jørgen
On 6/25/24 12:23, Jan Hubicka wrote:
>> The value vec objects are destroyed on exit, but release still needs to
>> be called explicitly.
>>
>> gcc/ChangeLog:
>>
>> * tree-profile.cc (find_conditions): Release vectors before
>> return.
> I wonder if you turn
> hash_map<int_hash<unsigned, 0>, vec<basic_block>> exprs;
> to
> hash_map<int_hash<unsigned, 0>, auto_vec<basic_block>> exprs;
> Won't hash_map destructor take care of this by itself?
>
> Honza
>> ---
>> gcc/tree-profile.cc | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/gcc/tree-profile.cc b/gcc/tree-profile.cc
>> index e4bb689cef5..18f48e8d04e 100644
>> --- a/gcc/tree-profile.cc
>> +++ b/gcc/tree-profile.cc
>> @@ -919,6 +919,9 @@ find_conditions (struct function *fn)
>> if (!have_post_dom)
>> free_dominance_info (fn, CDI_POST_DOMINATORS);
>>
>> + for (auto expr : exprs)
>> + expr.second.release ();
>> +
>> cov->m_masks.safe_grow_cleared (2 * cov->m_index.last ());
>> const size_t length = cov_length (cov);
>> for (size_t i = 0; i != length; i++)
>> --
>> 2.39.2
>>
Hi,
I am looking into these regressions.
Regards,
Surya
On 26/06/24 7:51 am, ci_notify(a)linaro.org wrote:
> Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. 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-1270 , 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-1619-g3b9b8d6cfdf5
> | Author: Surya Kumari Jangala <jskumari(a)linux.ibm.com>
> | Date: Tue Jun 25 08:37:49 2024 -0500
> |
> | ira: Scale save/restore costs of callee save registers with block frequency
> |
> | In assign_hard_reg(), when computing the costs of the hard registers, the
> | cost of saving/restoring a callee-save hard register in prolog/epilog is
> | taken into consideration. However, this cost is not scaled with the entry
> | block frequency. Without scaling, the cost of saving/restoring is quite
> | small and this can result in a callee-save register being chosen by
> | ... 14 lines of the commit log omitted.
>
> FAIL: 4 regressions
>
> regressions.sum:
> === g++ tests ===
>
> Running g++:g++.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> FAIL: gcc.target/aarch64/sve/acle/general/cpy_1.c -march=armv8.2-a+sve -moverride=tune=none check-function-bodies dup_x0_m
> === gcc tests ===
>
> Running gcc:gcc.dg/dg.exp ...
> FAIL: gcc.dg/pr10474.c scan-rtl-dump pro_and_epilogue "Performing shrink-wrapping"
>
> Running gcc:gcc.target/aarch64/sve/acle/aarch64-sve-acle.exp ...
> ... and 5 more entries
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
> The full lists of regressions and progressions as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
>
> 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/2235/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2234/artifac…
>
> 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/3b9b8d6cfdf59337f4b7ce10ce92a98044…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_check
> ** master-aarch64
> *** FAIL: 4 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/2235/artifac…
Hi Matthias,
Looking at [1], we are seeing this error only for bare-metal 32-bit ARM target, which, I believe, is not a configuration that compiler explorer supports. The specific configurations are either soft-float, or target ARM cores without NEON (aka no SIMD FPU).
Maybe the test should be guarded on the target supporting vectorization? I.e., maybe add
// { dg-require-effective-target vect_int }
?
[1] https://linaro.atlassian.net/browse/GNU-1265
--
Maxim Kuvyrkov
https://www.linaro.org
> On Jun 21, 2024, at 19:03, Matthias Kretz via Gcc-regression <gcc-regression(a)gcc.gnu.org> wrote:
>
> Hi,
>
> I looked into this and still don't understand how to reproduce it.
>
> The issue as logged in libstdc++.log is a call from
> find_last_set(simd_mask<int, _VecBuiltin<16>>) to
> _MaskImplNeonMixin::_S_to_bits, which calls vpadd_s32 with two
> [[gnu::vector_size(8)]] int arguments. The CI compiler complains "error:
> cannot convert '__vector(2) int' to 'int32x2_t'".
>
> Why is that an error on your side and not on any compiler I have at hand?
>
> https://compiler-explorer.com/z/88WhcM7Kb not an error here.
>
> In any case, the new test only exposes an existing issue in the <experimental/
> simd> implementation (or its interaction with some variants of GCC?). The
> change did not introduce a new bug to libstdc++.
>
> Best,
> Matthias
>
>
> On Friday, 21 June 2024 17:00:23 GMT+2 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-1265
>> , please let us know if you are looking at the problem and/or when you have
>> a fix.
>> In arm-eabi v7-a softfp after:
>> | commit gcc-15-1500-g1340ddea015
>> | Author: Matthias Kretz <m.kretz(a)gsi.de>
>> | Date: Fri Jun 14 15:11:25 2024 +0200
>> |
>> | libstdc++: Fix find_last_set(simd_mask) to ignore padding bits
>> |
>> | With the change to the AVX512 find_last_set implementation, the
>> | change
>> | to AVX512 operator!= is unnecessary. However, the latter was not
>> | producing optimal code and unnecessarily set the padding bits. In
>> | theory, the compiler could determine that with the new !=
>> | implementation, the bit operation for clearing the padding bits is a
>> |
>> | ... 13 lines of the commit log omitted.
>>
>> FAIL: 2 regressions
>>
>> regressions.sum:
>> === libstdc++ tests ===
>>
>> Running libstdc++:libstdc++-dg/conformance.exp ...
>> FAIL: experimental/simd/pr115454_find_last_set.cc -mfpu=neon -ffast-math -O2
>> -Wno-psabi (test for excess errors) UNRESOLVED:
>> experimental/simd/pr115454_find_last_set.cc -mfpu=neon -ffast-math -O2
>> -Wno-psabi compilation failed to produce executable
>>
>>
>> You can find the failure logs in *.log.1.xz files in
>> -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts/00-sumfiles/ The full lists of regressions
>> and progressions as well as configure and make commands are in -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts/notify/ The list of [ignored] baseline and
>> flaky failures are in
>> -
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts/sumfiles/xfails.xfail
>>
>> The configuration of this build is:
>> CI config tcwg_gnu_embed_check_gcc arm-eabi -marm -march=armv7-a
>> -mfpu=vfpv3-d16 -mfloat-abi=softfp
>>
>> -----------------8<--------------------------8<--------------------------8<-
>> ------------------------- The information below can be used to reproduce a
>> debug environment:
>>
>> Current build :
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts Reference build :
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/511/artifact/artifacts
>>
>> Reproduce last good and first bad builds:
>> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh
>> a1/1340ddea0158de3f49aeb75b4013e5fc313ff6f4/tcwg_gnu_embed_check_gcc/master-
>> arm_v7a_softfp_eabi/reproduction_instructions.txt
>>
>> Full commit :
>> https://github.com/gcc-mirror/gcc/commit/1340ddea0158de3f49aeb75b4013e5fc31
>> 3ff6f4
>>
>> List of configurations that regressed due to this commit :
>> * tcwg_gnu_embed_check_gcc
>> ** master-arm_v7a_softfp_eabi
>> *** FAIL: 2 regressions
>> ***
>> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh
>> a1/1340ddea0158de3f49aeb75b4013e5fc313ff6f4/tcwg_gnu_embed_check_gcc/master-
>> arm_v7a_softfp_eabi/details.txt ***
>> https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_e
>> abi-build/512/artifact/artifacts
>
>
> --
> ──────────────────────────────────────────────────────────────────────────
> Dr. Matthias Kretz https://mattkretz.github.io
> GSI Helmholtz Center for Heavy Ion Research https://gsi.de
> std::simd
> ──────────────────────────────────────────────────────────────────────────
Progress:
* UM-2 [QEMU upstream maintainership]
+ code review and target-arm pullreq
+ Coverity gardening: triage of new issues; update of component definitions
+ respin of "allow a second UART in virt machine" patchset from last year
+ KVM Forum programme committee work
-- PMM
Hello Linaro Toolchain Working Group,
clang-arm64-windows-msvc cannot checkout LLVM because of this error:
fatal: Unable to create
'C:/Users/tcwg/llvm-worker/clang-arm64-windows-msvc/llvm/.git/index.lock':
File exists.
Looks like it needs some love and care. Could you look at this, please?
Thanks
Galina
On Wed, 2024-06-12 at 20:25 +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/GNU-1254 , please let us know if
> you are looking at the problem and/or when you have a fix.
Sorry about the breakage.
I had filed this as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115465
and I believe I've fixed it with r15-1220-
ge35f4eab68773b08324f9784ca69f8ace3c657cc.
Dave
>
> In gcc_build master-aarch64 after:
>
> | commit gcc-15-1209-gc5e3be45688
> | Author: David Malcolm <dmalcolm(a)redhat.com>
> | Date: Wed Jun 12 09:15:09 2024 -0400
> |
> | pretty_printer: make all fields private
> |
> | No functional change intended.
> |
> | gcc/analyzer/ChangeLog:
> | * access-diagram.cc (access_range::dump): Update for
> fields of
> | pretty_printer becoming private.
> | ... 227 lines of the commit log omitted.
>
> Results changed to
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> # FAILED
> # First few build errors in logs:
> # 00:03:27 ../../../../../../gcc/gcc/config/aarch64/aarch64-early-
> ra.cc:3449:23: error: ‘class pretty_printer’ has no member named
> ‘buffer’; did you mean ‘output_buffer* pretty_printer::m_buffer’?
> (not accessible from this context)
> # 00:03:27 make[2]: *** [/home/tcwg-
> buildslave/workspace/tcwg_gnu_3/abe/snapshots/gcc.git~master/gcc/conf
> ig/aarch64/t-aarch64:200: aarch64-early-ra.o] Error 1
> # 00:03:27 make[1]: *** [Makefile:4704: all-gcc] Error 2
> # 00:03:27 make: *** [Makefile:1065: all] Error 2
>
> From
> # reset_artifacts:
> -10
> # true:
> 0
> # build_abe gcc:
> 1
>
> The configuration of this build is:
> CI config tcwg_gcc_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_gcc_build--master-aarch64-build/2157/artifac…
> Reference build :
> https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2156/artifac…
>
> 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/c5e3be456888aa48f591512ec28183703e…
>
> List of configurations that regressed due to this commit :
> * tcwg_gcc_build
> ** master-aarch64
> *** Failure
> ***
> https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> ***
> https://ci.linaro.org/job/tcwg_gcc_build--master-aarch64-build/2157/artifac…
Hi,
On Sun, Jun 09, 2024 at 11:37:45PM +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-1233 , 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-lts-allmodconfig after:
>
> | commit llvmorg-19-init-12271-g29189738b832
> | Author: Dan Liew <dan(a)su-root.co.uk>
> | Date: Thu May 23 18:35:24 2024 -0700
> |
> | Reland #90786 ([BoundsSafety] Allow 'counted_by' attribute on pointers in structs in C) (#93121)
> |
> | [BoundsSafety] Reland #93121 Allow 'counted_by' attribute on pointers in structs in C (#93121)
> |
> | Fixes #92687.
> |
> | Previously the attribute was only allowed on flexible array members.
> | ... 130 lines of the commit log omitted.
Thanks a lot for the report. This is expected and how Linux needs to
react is still being discussed/figured out:
https://github.com/ClangBuiltLinux/linux/issues/2026https://github.com/ClangBuiltLinux/linux/issues/2027https://github.com/ClangBuiltLinux/linux/issues/2028
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-1249 , please let us know if you are looking at the problem and/or when you have a fix.
In arm-eabi cortex-m0 soft after:
| commit v9.0.0-1299-g1f97715c83
| Author: Paolo Bonzini <pbonzini(a)redhat.com>
| Date: Wed Aug 9 01:10:34 2023 +0200
|
| Revert "python: use vendored tomli"
|
| Now that Ubuntu 20.04 is not included anymore, there is no need to ship
| it as part of QEMU; Ubuntu 22.04 includes it and Leap users anyway
| need to install all the required dependencies from PyPI.
|
| This mostly reverts commit ec77ee7634de123b7c899739711000fd21dab68b,
| ... 3 lines of the commit log omitted.
Results changed to
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft:
2
# build_abe newlib:
4
# build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft:
5
# build_abe gdb:
6
# build_abe qemu:
# FAILED
From
# reset_artifacts:
-10
# true:
0
# build_abe binutils:
1
# build_abe stage1 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft:
2
# build_abe newlib:
4
# build_abe stage2 -- --set gcc_override_configure=--disable-multilib --set gcc_override_configure=--with-mode=thumb --set gcc_override_configure=--with-cpu=cortex-m0 --set gcc_override_configure=--with-float=soft:
5
# build_abe gdb:
6
# build_abe qemu:
7
The configuration of this build is:
CI config tcwg_gnu_embed_build arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto
-----------------8<--------------------------8<--------------------------8<--------------------------
The information below can be used to reproduce a debug environment:
Current build : https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m0_eabi-build/…
Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m0_eabi-build/…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s…
Full commit : https://gitlab.com/qemu-project/qemu/commit/1f97715c8390e582f154d8b579c7077…
List of configurations that regressed due to this commit :
* tcwg_gnu_embed_build
** master-thumb_m0_eabi
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/qemu/s…
*** https://ci.linaro.org/job/tcwg_gnu_embed_build--master-thumb_m0_eabi-build/…
Progress:
* UM-2 [QEMU upstream maintainership]
- updated our component definition regexes for Coverity Scan
- sent patches with the followon cleanup RTH requested when reviewing
my FEAT_WFxT patchset
- code review
- triage of new coverity issues
-- PMM
Do r15-1050-gfcfce55c85f842ed843cbc4aabe744c6a004dead fix the failure?
On Thu, Jun 6, 2024 at 10:06 PM ci_notify--- via Gcc-regression
<gcc-regression(a)gcc.gnu.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-1244 , please let us know if you are looking at the problem and/or when you have a fix.
>
> In arm-eabi cortex-m0 soft after:
>
> | commit gcc-15-1022-gb05288d1f1e
> | Author: liuhongt <hongtao.liu(a)intel.com>
> | Date: Tue May 21 16:57:17 2024 +0800
> |
> | Don't simplify NAN/INF or out-of-range constant for FIX/UNSIGNED_FIX.
> |
> | According to IEEE standard, for conversions from floating point to
> | integer. When a NaN or infinite operand cannot be represented in the
> | destination format and this cannot otherwise be indicated, the invalid
> | operation exception shall be signaled. When a numeric operand would
> | convert to an integer outside the range of the destination format, the
> | ... 29 lines of the commit log omitted.
>
> FAIL: 1 regressions
>
> regressions.sum:
> === gcc tests ===
>
> Running gcc:gcc.dg/dg.exp ...
> FAIL: gcc.dg/pr100927.c scan-rtl-dump-times final "(?n)\\(fix:SI" 3
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
> The full lists of regressions and progressions as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
>
> The configuration of this build is:
> CI config tcwg_gnu_embed_check_gcc arm-eabi -mthumb -march=armv6s-m -mtune=cortex-m0 -mfloat-abi=soft -mfpu=auto
>
> -----------------8<--------------------------8<--------------------------8<--------------------------
> The information below can be used to reproduce a debug environment:
>
> Current build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
> Reference build : https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
>
> 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/b05288d1f1e4b632eddf8830b4369d4659…
>
> List of configurations that regressed due to this commit :
> * tcwg_gnu_embed_check_gcc
> ** master-thumb_m0_eabi
> *** FAIL: 1 regressions
> *** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
> *** https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m0_eabi-bu…
--
BR,
Hongtao
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-1242 , 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-stable-allmodconfig after:
| commit gcc-15-874-g9bda2c4c81b
| Author: David Malcolm <dmalcolm(a)redhat.com>
| Date: Tue May 28 15:55:24 2024 -0400
|
| libcpp: move label_text to its own header
|
| No functional change intended.
|
| libcpp/ChangeLog:
| * Makefile.in (TAGS_SOURCES): Add include/label-text.h.
| * include/label-text.h: New file.
| ... 4 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:
33
From
# reset_artifacts:
-10
# build_abe binutils:
-9
# build_abe stage1:
-5
# build_abe qemu:
-2
# linux_n_obj:
34005
# linux build successful:
all
# linux boot successful:
boot
The configuration of this build is:
CI config tcwg_kernel/gnu-master-arm-stable-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-arm-stable-allmodconfig-b…
Reference build : https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b…
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/9bda2c4c81b668b1d9abbb58cc4e805ac9…
List of configurations that regressed due to this commit :
* tcwg_kernel
** gnu-master-arm-stable-allmodconfig
*** Failure
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sh…
*** https://ci.linaro.org/job/tcwg_kernel--gnu-master-arm-stable-allmodconfig-b…
Fixed by v2 of the patch.
On Wed, 5 Jun 2024 at 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. 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-arm after:
>
> | gcc patch https://patchwork.sourceware.org/patch/91570
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Wed Jun 5 16:31:46 2024 +0100
> |
> | libstdc++: Use memchr to optimize std::find [PR88545]
> |
> | I plan to push this after testing finishes.
> |
> | -- >8 --
> |
> | This optimizes std::find to use memchr when searching for an integer in
> | ... 12 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | 66fa2f10372 contrib: Fix spelling and capitalization in header-tools
>
> FAIL: 4 regressions
>
> regressions.sum:
> === libstdc++ tests ===
>
> Running libstdc++:libstdc++-dg/conformance.exp ...
> FAIL: std/ranges/adaptors/lazy_split.cc -std=gnu++20 (test for excess errors)
> UNRESOLVED: std/ranges/adaptors/lazy_split.cc -std=gnu++20 compilation failed to produce executable
> FAIL: std/ranges/adaptors/lazy_split.cc -std=gnu++26 (test for excess errors)
> UNRESOLVED: std/ranges/adaptors/lazy_split.cc -std=gnu++26 compilation failed to produce executable
>
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/7597/artifac…
> The full lists of regressions and progressions as well as configure and make commands are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/7597/artifac…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-precommit/7597/artifac…
>
> 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-precommit/7597/artifac…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2226/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.
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-1221
> , 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-937-g7e322d576eb
> | Author: Rainer Orth <ro(a)CeBiTec.Uni-Bielefeld.DE>
> | Date: Fri May 31 09:29:38 2024 +0200
> |
> | testsuite: Adjust several dg-additional-files-options calls [PR115294]
> |
> | A recent patch
> |
> | commit bdc264a16e327c63d133131a695a202fbbc0a6a0
> | Author: Alexandre Oliva <oliva(a)adacore.com>
> | Date: Thu May 30 02:06:48 2024 -0300
> | ... 42 lines of the commit log omitted.
>
> FAIL: 8 regressions
I couldn't find a way to comment on the issue page directly, and I
refuse to spend any time on some random CI system du jour.
This is a false positive: the previous commit
commit bdc264a16e327c63d133131a695a202fbbc0a6a0
Author: Alexandre Oliva <oliva(a)adacore.com>
Date: Thu May 30 02:06:48 2024 -0300
broke libgomp testing, hiding any previous failures as described in PR
testsuite/115294. My patch restored testing, so all failures previously
visible are now visible again.
Those failures are well known and tracked as PR testsuite/115140, no
regression here.