From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: Peter Bergner <bergner@linux.ibm.com>,
Pat Haugen <pthaugen@linux.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] rs6000: Disable -fcaller-saves by default
Date: Wed, 26 Aug 2020 15:58:50 -0500 [thread overview]
Message-ID: <20200826205850.GW28786@gate.crashing.org> (raw)
In-Reply-To: <90a17292189abb90f3b624df3537274045997ed8.camel@redhat.com>
On Tue, Aug 25, 2020 at 02:35:51PM -0600, Jeff Law wrote:
> I've gone back and forth on pre allocation splitting as well as post-allocating
> splitting and re-allocation. I could argue either side of that discussion --
If you end up wanting something split it is best to do it early. But if
you cannot predict well if you want it split eventually, there is no
good way to do this afaics :-(
> given we've got a bit of special code for splitting to help shrink wrapping,
Only very minimal stuff for splitting copies from a hard reg (argument reg)
to a pseudo. And then only for all together.
> I'd probably start by making sure the cost computation is sane though.
Yeah.
Segher
next prev parent reply other threads:[~2020-08-26 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 19:25 Pat Haugen
2020-07-23 19:42 ` Jeff Law
2020-07-23 20:19 ` Segher Boessenkool
2020-07-23 20:29 ` Jeff Law
2020-07-23 20:43 ` Segher Boessenkool
2020-08-10 16:11 ` Peter Bergner
2020-08-25 20:35 ` Jeff Law
2020-08-26 20:58 ` Segher Boessenkool [this message]
2020-08-26 21:10 ` Jeff Law
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=20200826205850.GW28786@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=pthaugen@linux.ibm.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).