linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Anton Blanchard <anton@samba.org>
Cc: Michael Gschwind <mkg@us.ibm.com>, Alan Modra <amodra@gmail.com>,
	Bill Schmidt <wschmidt@us.ibm.com>,
	Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	paulus@samba.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: RFC: Reducing the number of non volatile GPRs in the ppc64 kernel
Date: Tue, 11 Aug 2015 17:18:05 -0500	[thread overview]
Message-ID: <20150811221805.GD4711@gate.crashing.org> (raw)
In-Reply-To: <20150811200829.GC4711@gate.crashing.org>

On Tue, Aug 11, 2015 at 03:08:29PM -0500, Segher Boessenkool wrote:
> [snip code]
> 
> After the prologue there are 46 insns executed before the epilogue.
> Many of those are conditional branches (that are not executed); it is
> all fall-through until it jumps to the "tail" (the few insns before
> the epilogue).  GCC knows how to duplicate a tail so that it can do
> shrink-wrapping (the original tail needs to be followed by an epilogue,
> the duplicated one does not want one); but it can only do it in very
> simple cases (one basic block or at least no control flow), and that
> is not the case here.  We need to handle more generic tails.

And never mind the elephant in the room: the "fastpath" instructions
already use a few non-volatile registers, and the shrink-wrap pass
(which runs after register allocation) cannot fix that.  Ugh.

> This seems related to (if not the same as!) <http://gcc.gnu.org/PR51982>.

This has that same problem, too.


Segher

  reply	other threads:[~2015-08-11 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05  4:03 RFC: Reducing the number of non volatile GPRs in the ppc64 kernel Anton Blanchard
2015-08-05  4:19 ` Segher Boessenkool
2015-08-07  5:55   ` Bill Schmidt
2015-08-10  4:52     ` Anton Blanchard
2015-08-11 20:08       ` Segher Boessenkool
2015-08-11 22:18         ` Segher Boessenkool [this message]
2015-08-13 21:04       ` Anton Blanchard
2015-08-14  2:01 ` Michael Ellerman

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=20150811221805.GD4711@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=amodra@gmail.com \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mkg@us.ibm.com \
    --cc=paulus@samba.org \
    --cc=wschmidt@us.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 NNTP newsgroup(s).