public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100106] [10 Regression] ICE in gen_movdi, at config/arm/arm.md:6187 since r10-2840-g70cdb21e
Date: Fri, 08 Apr 2022 10:20:56 +0000 [thread overview]
Message-ID: <bug-100106-4-NoGzuJD0rj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100106-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100106
--- Comment #8 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to CVS Commits from comment #7)
> The releases/gcc-11 branch has been updated by Richard Biener
> <rguenth@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:5155015ce57dc133e006f87fdf0237a5f259bebd
>
Just to note that on master it was necessary to apply r12-3480 as part of a
subsequent patch set. The problem case was calling gen_highpart() on an
unaligned MEM. Prior to this patch gen_highpart() would generate the expected
unaligned MEM for the narrower access, but after r12-163 we'd get (subreg(MEM))
being returned, which was unexpected. I'm not going to backport that now as
it's not clear if this is needed for GCC-11.
next prev parent reply other threads:[~2022-04-08 10:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 21:06 [Bug target/100106] New: [10/11 " acoplan at gcc dot gnu.org
2021-04-15 21:06 ` [Bug target/100106] " acoplan at gcc dot gnu.org
2021-04-16 7:09 ` rguenth at gcc dot gnu.org
2021-04-16 7:13 ` rguenth at gcc dot gnu.org
2021-04-20 6:00 ` bernd.edlinger at hotmail dot de
2021-04-27 15:48 ` [Bug target/100106] [10/11/12 " cvs-commit at gcc dot gnu.org
2021-04-27 15:51 ` [Bug target/100106] [10/11 " edlinger at gcc dot gnu.org
2021-07-19 11:59 ` rguenth at gcc dot gnu.org
2022-04-07 10:39 ` cvs-commit at gcc dot gnu.org
2022-04-08 10:20 ` rearnsha at gcc dot gnu.org [this message]
2022-06-28 10:44 ` [Bug target/100106] [10 " jakub at gcc dot gnu.org
2023-05-25 2:46 ` cvs-commit at gcc dot gnu.org
2023-07-07 9:35 ` rguenth 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-100106-4-NoGzuJD0rj@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).