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: Wed, 1 Apr 2020 12:48:53 -0500 [thread overview]
Message-ID: <b5969e13-f671-4938-c5c9-f3b2615d91d8@linux.ibm.com> (raw)
In-Reply-To: <mptwo72dy6a.fsf@arm.com>
On 3/30/20 3:50 AM, Richard Sandiford wrote:
> Peter Bergner via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
>> * lower-subreg.c (pass_lower_subreg3::gate): Remove test for
>> flag_split_wide_types_early.
>>
>> diff --git a/gcc/lower-subreg.c b/gcc/lower-subreg.c
>> index 4c8bc835f93..807ad398b64 100644
>> --- a/gcc/lower-subreg.c
>> +++ b/gcc/lower-subreg.c
>> @@ -1844,8 +1844,7 @@ public:
>> {}
>>
>> /* 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; }
>> virtual unsigned int execute (function *)
>> {
>> decompose_multiword_subregs (true);
>
> Looks good to me with the s/ != 0// that Segher mentioned.
>
> With this change, the only remaining function of -fsplit-wide-types-early
> is to act as a double lock on one pass. IMO it'd make more sense to remove
> that double lock and make -fsplit-wide-types-early and -fsplit-wide-types
> act as independent options, a bit like -fschedule-insns{,2}.
Have we come to consensus on whether to split the options or not?
I think Segher is against it given we actually have 3 passes of
lower-subreg and -fsplit-wide-types would control the 1st and 3rd
passes and -fsplit-wide-types-early would control the second.
That does seem strange to me too.
Peter
next prev parent reply other threads:[~2020-04-01 17:49 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
2020-03-30 16:39 ` Segher Boessenkool
2020-03-30 16:06 ` Segher Boessenkool
2020-04-01 17:48 ` Peter Bergner [this message]
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=b5969e13-f671-4938-c5c9-f3b2615d91d8@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).