From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Bergner via Gcc-patches <gcc-patches@gcc.gnu.org>,
Peter Bergner <bergner@linux.ibm.com>,
"ian@airs.com" <ian@airs.com>,
richard.sandiford@arm.com
Subject: Re: [PATCH] lower-subreg: PR94123, SVN r273240, causes gcc.target/powerpc/pr87507.c to fail
Date: Mon, 30 Mar 2020 11:06:10 -0500 [thread overview]
Message-ID: <20200330160610.GS22482@gate.crashing.org> (raw)
In-Reply-To: <mptwo72dy6a.fsf@arm.com>
Hi!
On Mon, Mar 30, 2020 at 09:50:05AM +0100, Richard Sandiford wrote:
> 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}.
But then, -fsplit-wide-types would control two passes, one of which is
identical to -fsplit-wide-types-early, just in a different spot in the
pass pipeline. That is bad enough on its own, already :-/
I still think all three passes should be controlled by -fsplit-wide-types,
just as they already are (and the "old" two have been for years).
Segher
next prev parent reply other threads:[~2020-03-30 16:06 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 [this message]
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=20200330160610.GS22482@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.sandiford@arm.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).