public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111784] [14 Regression] aarch64: ldp_stp_{15,16,17,18}.c test failures since r14-4579
Date: Fri, 13 Oct 2023 00:52:00 +0000 [thread overview]
Message-ID: <bug-111784-4-F85bCaywVs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111784-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111784
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[14 Regression] aarch64: |[14 Regression] aarch64:
|ldp_stp_{15,16,17,18}.c |ldp_stp_{15,16,17,18}.c
|test failures |test failures since
| |r14-4579
Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2023-10-13
CC| |linkw at gcc dot gnu.org
--- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> ---
Thanks for reporting!
(In reply to Alex Coplan from comment #1)
> More context/details about the issue in 8/10 of the original patch series
> (that the above revision comes from):
> https://gcc.gnu.org/pipermail/gcc-patches/2023-September/630234.html
Yeah, there are some discussion under this thread, I'll make a patch to cover
both load and store.
next prev parent reply other threads:[~2023-10-13 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 13:02 [Bug target/111784] New: [14 Regression] aarch64: ldp_stp_{15,16,17,18}.c test failures acoplan at gcc dot gnu.org
2023-10-12 15:30 ` [Bug target/111784] " acoplan at gcc dot gnu.org
2023-10-13 0:52 ` linkw at gcc dot gnu.org [this message]
2023-10-13 6:48 ` [Bug target/111784] [14 Regression] aarch64: ldp_stp_{15,16,17,18}.c test failures since r14-4579 rguenth at gcc dot gnu.org
2023-10-23 2:24 ` cvs-commit at gcc dot gnu.org
2023-10-23 6:16 ` linkw at gcc dot gnu.org
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=bug-111784-4-F85bCaywVs@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).