public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: ci_notify@linaro.org
To: mjambor@suse.cz
Cc: gcc-regression@gcc.gnu.org
Subject: [Linaro-TCWG-CI] gcc-14-9841-g1e3312a25a7: FAIL: 3 regressions on arm
Date: Tue, 9 Apr 2024 03:16:27 +0000 (UTC)	[thread overview]
Message-ID: <2013640996.10436.1712632588875@jenkins.jenkins> (raw)

[-- Attachment #1: Type: text/plain, Size: 3433 bytes --]

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@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-1191 , 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-14-9841-g1e3312a25a7
  | Author: Martin Jambor <mjambor@suse.cz>
  | Date:   Mon Apr 8 18:53:23 2024 +0200
  | 
  |     ICF&SRA: Make ICF and SRA agree on padding
  |     
  |     PR 113359 shows that (at least with -fno-strict-aliasing) ICF can
  |     unify two functions which copy an aggregate type of the same size but
  |     then SRA, through its total scalarization, can copy the aggregate by
  |     pieces, skipping paddding, but the padding was not the same in the two
  |     original functions that ICF unified.
  | ... 51 lines of the commit log omitted.

FAIL: 3 regressions

regressions.sum:
		=== gcc tests ===

Running gcc:gcc.dg/lto/lto.exp ...
FAIL: gcc-dg-lto-pr113359-2-01.exe scan-wpa-ipa-dump icf "Semantic equality hit:geta/.*getb/"
FAIL: gcc.dg/lto/pr113359-2 c_lto_pr113359-2_0.o assemble, -O2 -flto -fno-strict-aliasing -fno-ipa-cp  --disable-tree-esra -fdump-ipa-icf-details
FAIL: gcc.dg/lto/pr113359-2 c_lto_pr113359-2_0.o-c_lto_pr113359-2_1.o execute -O2 -flto -fno-strict-aliasing -fno-ipa-cp  --disable-tree-esra -fdump-ipa-icf-details


You can find the failure logs in *.log.1.xz files in
 - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1948/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_gcc_check--master-arm-build/1948/artifact/artifacts/notify/
The list of [ignored] baseline and flaky failures are in
 - https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1948/artifact/artifacts/sumfiles/xfails.xfail

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/1948/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1947/artifact/artifacts

Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/1e3312a25a7b34d6e3f549273e1674c7114e4408/tcwg_gcc_check/master-arm/reproduction_instructions.txt

Full commit : https://github.com/gcc-mirror/gcc/commit/1e3312a25a7b34d6e3f549273e1674c7114e4408

List of configurations that regressed due to this commit :
* tcwg_gcc_check
** master-arm
*** FAIL: 3 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/1e3312a25a7b34d6e3f549273e1674c7114e4408/tcwg_gcc_check/master-arm/details.txt
*** https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/1948/artifact/artifacts

                 reply	other threads:[~2024-04-09  3:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2013640996.10436.1712632588875@jenkins.jenkins \
    --to=ci_notify@linaro.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=mjambor@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).