From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: "Roger Sayle" <roger@nextmovesoftware.com>
Cc: "'Christophe LYON'" <christophe.lyon@foss.st.com>,
"'GCC Patches'" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Preserve SUBREG_PROMOTED_VAR_P on (extend:HI (subreg/s:QI (reg:SI)))
Date: Tue, 31 Aug 2021 23:00:21 +0200 [thread overview]
Message-ID: <ydd1r695nyy.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <006801d79e6b$9a0754e0$ce15fea0$@nextmovesoftware.com> (Roger Sayle's message of "Tue, 31 Aug 2021 14:24:59 +0100")
Hi Roger,
> I'm testing the attached patch, but without an aarch64, it'll take a while
> to figure
> out the toolchain to reproduce the failure. Neither of the platforms I
> tested were
> affected, but I can see it's unsafe to reuse the subreg_promoted_reg idiom from
> just a few lines earlier. Any help testing the attached patch on an
> affected target
> would be much appreciated.
after reverting the patch that caused PR middle-end/102133 and had
already broken 32-bit sparc bootstrap, sparc was affected again by this
one for a couple of files in 64-bit libgcc.
Fortunately, this patch fixes the build (only tried a minimal
non-bootstrap so far).
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2021-08-31 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 7:46 Roger Sayle
2021-08-29 20:59 ` Jeff Law
2021-08-31 12:32 ` Christophe LYON
2021-08-31 13:24 ` Roger Sayle
2021-08-31 15:30 ` Jeff Law
2021-08-31 21:00 ` Rainer Orth [this message]
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=ydd1r695nyy.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=christophe.lyon@foss.st.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.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).