Yeah I'll fix this, looks like a testism due to changes in codegen between dev and commit versions, code improved too so it's the good type of testism ;)
________________________________________
From: ci_notify(a)linaro.org <ci_notify(a)linaro.org>
Sent: Thursday, April 11, 2024 3:43 PM
To: Andre Simoes Dias Vieira
Cc: gcc-regression(a)gcc.gnu.org
Subject: [Linaro-TCWG-CI] gcc-14-9891-g5aa3fec38cc: FAIL: 12 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-1192 , 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-14-9891-g5aa3fec38cc
| Author: Andre Vieira <andre.simoesdiasvieira(a)arm.com>
| Date: Wed Apr 10 16:29:46 2024 +0100
|
| aarch64: Add support for _BitInt
|
| This patch adds support for C23's _BitInt for the AArch64 port when compiling
| for little endianness. Big Endianness requires further target-agnostic
| support and we therefor disable it for now.
|
| gcc/ChangeLog:
| ... 24 lines of the commit log omitted.
FAIL: 12 regressions
regressions.sum:
=== gcc tests ===
Running gcc:gcc.target/aarch64/aarch64.exp ...
FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g1
FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g16
FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g16p
FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g1p
FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g8
FAIL: gcc.target/aarch64/bitfield-bitint-abi-align16.c check-function-bodies g8p
FAIL: gcc.target/aarch64/bitfield-bitint-abi-align8.c check-function-bodies g1
... and 6 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/1842/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/1842/artifac…
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1842/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/1842/artifac…
Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1841/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/5aa3fec38cc6f52285168b161bab1a869d…
List of configurations that regressed due to this commit :
* tcwg_gcc_check
** master-aarch64
*** FAIL: 12 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/1842/artifac…
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ci_notify(a)linaro.org writes:
> In CI config tcwg_kernel/gnu-master-arm-next-allyesconfig after:
>
> | commit v6.9-rc2-36-gfc4216add64ee
> | Author: Samuel Holland <samuel.holland(a)sifive.com>
> | Date: Fri Mar 29 00:18:28 2024 -0700
> |
> | drm/amd/display: use ARCH_HAS_KERNEL_FPU_SUPPORT
> |
> | Now that all previously-supported architectures select
> | ARCH_HAS_KERNEL_FPU_SUPPORT, this code can depend on that symbol instead
> | of the existing list of architectures. It can also take advantage of the
> | common kernel-mode FPU API and method of adjusting CFLAGS.
> |
> | ... 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:
> 22511
>
> From
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_abe stage1:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 22321
> # linux build successful:
> all
This problem still reproduces on next-20240410, so I reported it to the
patch author. He responded here:
https://lore.kernel.org/linux-arm-kernel/75a37a4b-f516-40a3-b6b5-4aa1636f9b…
mentioning that it's a shortcoming of GCC on arm:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91970
Though Andrew Pinski has just disagreed with that assessment.
--
Thiago
Hi there,
Thanks for the heads-up on gcc patch #88281: 6 regressions on arm.
I see from the log that the test timed-out and the core was dumped. I
cannot reproduce this and can see nothing in the tree-dump that might cause
a time out. I would appreciate some help on where the fault lies and what
the cause might be.
Best regards
Paul Thomas
Progress (short week, 3 days):
* UM-2 [QEMU upstream maintainership]
- more pullreq wrangling
- more FEAT_NMI patchset review: I think I'm now finally done with this
- looked at issue #2150 and produced a short standalone repro case from
the logfile the user provided (which was from a boot of Windows)
-- PMM
On Thu, 4 Apr 2024 at 22:21, <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.
Hi,
The new testcase only works for targets where char is signed, because
I forgot to add the assertions for the unsigned case. My own aarch64
testing found the same problem.
I'll send a v2 patch shortly. Thanks for the useful CI service!
>
> 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/88035
> | Author: Jonathan Wakely <jwakely(a)redhat.com>
> | Date: Thu Apr 4 16:29:09 2024 +0100
> |
> | libstdc++: Fix infinite loop in std::istream::ignore(n, delim) [PR93672]
> |
> | I would appreciate more eyes on this to confirm my conclusions about
> | negative int_type values, and the proposed fix, make sense.
> |
> | Tested x86_64-linux.
> |
> | ... 32 lines of the commit log omitted.
> | ... applied on top of baseline commit:
> | dc8a25189dd Add gcov MC/DC tests for GDC
>
> FAIL: 1 regressions
>
> regressions.sum:
> === libstdc++ tests ===
>
> Running libstdc++:libstdc++-dg/conformance.exp ...
> FAIL: 27_io/basic_istream/ignore/char/93672.cc -std=gnu++17 execution test
>
>
> # of stable fails 61
> # of flaky entries 9
> # of all tests 890731
>
> You can find the failure logs in *.log.1.xz files in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/5627/art…
> 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-precommit/5627/art…
> The list of [ignored] baseline and flaky failures are in
> - https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-precommit/5627/art…
>
> 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/5627/art…
> Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1805/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.
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-1187 , please let us know if you are looking at the problem and/or when you have a fix.
In master-aarch64 after:
| commit glibc-2.39.9000-128-ga4ed0471d7
| Author: Adhemerval Zanella <adhemerval.zanella(a)linaro.org>
| Date: Thu Jan 18 10:18:01 2024 -0300
|
| Always define __USE_TIME_BITS64 when 64 bit time_t is used
|
| It was raised on libc-help [1] that some Linux kernel interfaces expect
| the libc to define __USE_TIME_BITS64 to indicate the time_t size for the
| kABI. Different than defined by the initial y2038 design document [2],
| the __USE_TIME_BITS64 is only defined for ABIs that support more than
| one time_t size (by defining the _TIME_BITS for each module).
| ... 12 lines of the commit log omitted.
FAIL: 4 regressions
regressions.sum:
=== g++ tests ===
Running g++:g++.dg/tsan/tsan.exp ...
FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O0 (test for excess errors)
UNRESOLVED: g++.dg/tsan/pthread_cond_clockwait.C -O0 compilation failed to produce executable
FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O2 (test for excess errors)
UNRESOLVED: g++.dg/tsan/pthread_cond_clockwait.C -O2 compilation failed to produce executable
... and 2 more entries
You can find the failure logs in *.log.1.xz files in
- https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1…
The full lists of regressions and progressions as well as configure and make commands are in
- https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1…
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1…
The configuration of this build is:
CI config tcwg_gnu_native_check_gcc 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_check_gcc--master-aarch64-build/1…
Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1…
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=a4ed0471d71739928a0d…
List of configurations that regressed due to this commit :
* tcwg_gnu_native_check_gcc
** master-aarch64
*** FAIL: 4 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/glibc/…
*** https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1…