From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: ebotcazou@libertysurf.fr
Subject: Re: [PATCH v2] [PR100106] Reject unaligned subregs when strict alignment is required
Date: Wed, 24 May 2023 02:39:11 -0300 [thread overview]
Message-ID: <ormt1up9ts.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orfslnfkm1.fsf_-_@lxoliva.fsfla.org> (Alexandre Oliva's message of "Thu, 05 May 2022 23:41:42 -0300")
On May 5, 2022, Alexandre Oliva <oliva@adacore.com> wrote:
> for gcc/ChangeLog
> PR target/100106
> * emit-rtl.cc (validate_subreg): Reject a SUBREG of a MEM that
> requires stricter alignment than MEM's.
> for gcc/testsuite/ChangeLog
> PR target/100106
> * gcc.target/powerpc/pr100106-sa.c: New.
Ping?
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/594166.html
The testcase variant was approved, but the reformatted patch is still
pending review, despite support from Vlad Makarov for the original one;
the suggested separate followup patch, mentioned in the linked email,
turned out to be far more involved than anticipated, and needs further
work, but it's independent from this self-contained fix.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2023-05-24 5:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 6:52 [PATCH] " Alexandre Oliva
2022-05-05 7:59 ` Richard Sandiford
2022-05-05 13:50 ` Segher Boessenkool
2022-05-06 10:57 ` [PATCH v2 2/2] " Alexandre Oliva
2022-05-09 8:09 ` Richard Sandiford
2022-05-05 14:33 ` [PATCH] " Segher Boessenkool
2022-05-06 2:41 ` [PATCH v2] " Alexandre Oliva
2022-07-09 17:14 ` Jeff Law
2023-05-24 5:39 ` Alexandre Oliva [this message]
2023-05-24 9:04 ` Richard Biener
2022-05-06 18:04 ` [PATCH] " Vladimir Makarov
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=ormt1up9ts.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc-patches@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).