public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	"ian@airs.com" <ian@airs.com>,
	Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCH] lower-subreg: PR94123, SVN r273240, causes gcc.target/powerpc/pr87507.c to fail
Date: Sat, 28 Mar 2020 18:39:56 -0500	[thread overview]
Message-ID: <1d9009c1-7902-44e2-ba36-6e985e84f5eb@linux.ibm.com> (raw)
In-Reply-To: <20200328192252.GM22482@gate.crashing.org>

On 3/28/20 2:22 PM, Segher Boessenkool wrote:
> On Fri, Mar 27, 2020 at 05:41:36PM -0500, Peter Bergner wrote:
>> A different (ie, safer) approach would be to just rerun lower-subreg at
>> its old location, regardless of whether we used -fsplit-wide-types-early.
> 
> That is my preference, for a simpler reason even: when I added the new
> pass I disabled the old one, thinking it wouldn't do anything useful
> anymore.  Here you show that isn't true.
>
>> This way, we are not changing lower-subreg's behaviour, just running it an
>> extra time (3 times instead of twice when using -fsplit-wide-types-early).
>> I don't think lower-subreg is too expensive to run an extra time
> 
> Yes, I think so too.

Right.  However, like I said though, the downside is that we don't expose
the decomposed uses to passes in between subreg2 and subreg3, like combine,
etc.  Isn't that why you moved it early in the first place?  Then again,
maybe you're getting the important cases now and subreg3 is just cleanup?

That said, I'm fine with whatever you, richi and others want.



>>    /* opt_pass methods: */
>> -  virtual bool gate (function *) { return flag_split_wide_types
>> -					  && !flag_split_wide_types_early; }
>> +  virtual bool gate (function *) { return flag_split_wide_types != 0; }
> 
> I think you mean
>   return flag_split_wide_types != 0 != 0 != 0;

Heh, I was just reverting it to the code prior to your change.  I can make
that just "return flag_split_wide_types;" if you like and we end up going
with this version.

Peter


  reply	other threads:[~2020-03-28 23:40 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 [this message]
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
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=1d9009c1-7902-44e2-ba36-6e985e84f5eb@linux.ibm.com \
    --to=bergner@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ian@airs.com \
    --cc=richard.guenther@gmail.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).