public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: ci_notify@linaro.org
To: linkw@linux.ibm.com
Cc: gcc-regression@gcc.gnu.org
Subject: [Linaro-TCWG-CI] gcc-14-4579-g0bdb9bb5607: FAIL: 11 regressions on aarch64
Date: Thu, 12 Oct 2023 09:49:52 +0000 (UTC) [thread overview]
Message-ID: <429416104.38224.1697104193851@jenkins.jenkins> (raw)
[-- Attachment #1: Type: text/plain, Size: 3281 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.
In gcc_check master-aarch64 after:
| commit gcc-14-4579-g0bdb9bb5607
| Author: Kewen Lin <linkw@linux.ibm.com>
| Date: Thu Oct 12 00:04:57 2023 -0500
|
| vect: Get rid of vect_model_store_cost
|
| This patch is to eventually get rid of vect_model_store_cost,
| it adjusts the costing for the remaining memory access types
| VMAT_CONTIGUOUS{, _DOWN, _REVERSE} by moving costing close
| to the transform code. Note that in vect_model_store_cost,
| there is one special handling for vectorizing a store into
| ... 8 lines of the commit log omitted.
FAIL: 11 regressions
regressions.sum:
=== gcc tests ===
Running gcc:gcc.target/aarch64/aarch64.exp ...
FAIL: gcc.target/aarch64/ldp_stp_15.c check-function-bodies cons2_16_int32_t
FAIL: gcc.target/aarch64/ldp_stp_15.c check-function-bodies cons4_8_int32_t
FAIL: gcc.target/aarch64/ldp_stp_15.c check-function-bodies dup_8_int32_t
FAIL: gcc.target/aarch64/ldp_stp_16.c check-function-bodies cons2_4_float
FAIL: gcc.target/aarch64/ldp_stp_17.c check-function-bodies cons2_16_int64_t
FAIL: gcc.target/aarch64/ldp_stp_17.c check-function-bodies cons4_16_int64_t
FAIL: gcc.target/aarch64/ldp_stp_17.c check-function-bodies dup_16_int64_t
... 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/1040/artifact/artifacts/00-sumfiles/ .
The full lists of regressions and progressions are in
- https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1040/artifact/artifacts/notify/ .
The list of [ignored] baseline and flaky failures are in
- https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1040/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/1040/artifact/artifacts
Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1039/artifact/artifacts
Reproduce last good and first bad builds: https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/0bdb9bb5607edd7df1ee74ddfcadb87324ca00c2/tcwg_gcc_check/master-aarch64/reproduction_instructions.txt
Full commit : https://github.com/gcc-mirror/gcc/commit/0bdb9bb5607edd7df1ee74ddfcadb87324ca00c2
Latest bug report status : https://linaro.atlassian.net/browse/GNU-965
List of configurations that regressed due to this commit :
* tcwg_gcc_check
** master-aarch64
*** FAIL: 11 regressions
*** https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/gcc/sha1/0bdb9bb5607edd7df1ee74ddfcadb87324ca00c2/tcwg_gcc_check/master-aarch64/details.txt
*** https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1040/
reply other threads:[~2023-10-12 9:49 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=429416104.38224.1697104193851@jenkins.jenkins \
--to=ci_notify@linaro.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=linaro-toolchain@lists.linaro.org \
--cc=linkw@linux.ibm.com \
/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).