From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Bergner <bergner@linux.ibm.com>
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 14:22:52 -0500 [thread overview]
Message-ID: <20200328192252.GM22482@gate.crashing.org> (raw)
In-Reply-To: <20ee8944-f0bf-cec1-e3d1-5dd5e9c6a4ef@linux.ibm.com>
On Fri, Mar 27, 2020 at 05:41:36PM -0500, Peter Bergner wrote:
> Given we're late in stage4, the above patch (assuming it's ok) probably
> shouldn't go in until stage1, since it is changing lower-subreg's behaviour
> slightly.
>
> 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.
> and we'd only do it when using -fsplit-wide-types-early.
But note that is true by default for some targets (rs6000 and avr
currently, I think).
> /* 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;
:-P
Segher
next prev parent reply other threads:[~2020-03-28 19:23 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 [this message]
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
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=20200328192252.GM22482@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=richard.guenther@gmail.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).