From: Richard Sandiford <richard.sandiford@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: segher@kernel.crashing.org
Subject: [PATCH v2 0/2] Series of patch to fix PR106594
Date: Thu, 09 Mar 2023 12:08:33 +0000 [thread overview]
Message-ID: <mptjzzq160u.fsf@arm.com> (raw)
This series of patches fixes PR106594, an aarch64 regression in which
we fail to combine an extension into an address. The first patch just
refactors code. The second patch contains the actual fix.
The cover note for the second patch describes the problem and the fix.
Tested on aarch64-linux-gnu and x86_64-linux-gnu. OK to install?
Richard
next reply other threads:[~2023-03-09 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 12:08 Richard Sandiford [this message]
2023-03-09 12:09 ` [PATCH v2 1/2] combine: Split code out of make_compound_operation_int Richard Sandiford
2023-03-31 11:06 ` Segher Boessenkool
2023-03-31 12:13 ` Richard Sandiford
2023-03-09 12:10 ` [PATCH v2 2/2] combine: Try harder to form zero_extends [PR106594] Richard Sandiford
2023-03-31 12:16 ` Segher Boessenkool
2023-03-31 14:06 ` Richard Sandiford
2023-03-31 14:35 ` Segher Boessenkool
2023-03-31 14:55 ` Richard Sandiford
2023-03-27 12:14 ` [PATCH v2 0/2] Series of patch to fix PR106594 Richard Sandiford
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=mptjzzq160u.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).