From: Peter Bergner <bergner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
richard.sandiford@arm.com
Cc: Gcc-patches <gcc-patches@gcc.gnu.org>, "ian@airs.com" <ian@airs.com>
Subject: Re: [PATCH] lower-subreg: PR94123, SVN r273240, causes gcc.target/powerpc/pr87507.c to fail
Date: Mon, 30 Mar 2020 11:26:59 -0500 [thread overview]
Message-ID: <99d2d9f1-ff48-ffc2-f56f-d90ccaac6b84@linux.ibm.com> (raw)
In-Reply-To: <6c43dfe0-2dd8-aa95-4ace-62b49657e0aa@linux.ibm.com>
On 3/30/20 11:23 AM, Peter Bergner wrote:
> I kind of agree with Richard above on making it more applicable/symmetric,
> but why can't we just remove the HARD_REGISTER_NUM_P() tests altogether?
> It's not like lower-subreg is extending hard register lifetime usage than
> what is already there in the rtl. We're just decomposing what's already
> there into smaller register sized chunks. Is there a problem with that
> I'm not aware of?
...or maybe there was an issue when combine used to extend hard register
lifetimes (which it doesn't anymore) and the test above was just a workaround?
Peter
next prev parent reply other threads:[~2020-03-30 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 22:41 Peter Bergner
2020-03-27 23:26 ` Ian Lance Taylor
2020-03-28 19:22 ` Segher Boessenkool
2020-03-28 23:39 ` Peter Bergner
2020-04-02 21:56 ` Segher Boessenkool
2020-03-30 8:50 ` Richard Sandiford
2020-03-30 11:26 ` Segher Boessenkool
2020-03-30 16:23 ` Peter Bergner
2020-03-30 16:26 ` Peter Bergner [this message]
2020-03-30 16:39 ` Segher Boessenkool
2020-03-30 16:06 ` Segher Boessenkool
2020-04-01 17:48 ` Peter Bergner
2020-04-01 18:32 ` Richard Sandiford
2020-04-01 19:43 ` Peter Bergner
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=99d2d9f1-ff48-ffc2-f56f-d90ccaac6b84@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=richard.sandiford@arm.com \
--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).