public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51982] Shrink-wrapping opportunity
Date: Mon, 06 Feb 2012 07:07:00 -0000	[thread overview]
Message-ID: <bug-51982-4-Xx5VEIHs1C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51982-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51982

Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|amodra at gcc dot gnu.org   |amodra at gmail dot com

--- Comment #2 from Alan Modra <amodra at gmail dot com> 2012-02-06 07:07:41 UTC ---
I confirm comment #2.  We do have incoming args being saved in callee-saved
regs and those callee-saved regs then being used.

However, there are additional problems to solve before this function will ever
be shrink-wrapped.  We have uses of callee-saved regs for more than just
incoming args.  For instance, "mask" gets put in r24 and "ep0" in r25 in the
first bb, and a little later, "i" in r29 and others are used for other
intermediate values.


  parent reply	other threads:[~2012-02-06  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 19:08 [Bug middle-end/51982] New: " dje at gcc dot gnu.org
2012-01-24 19:42 ` [Bug middle-end/51982] " dje at gcc dot gnu.org
2012-01-24 19:42 ` pinskia at gcc dot gnu.org
2012-02-06  7:07 ` amodra at gmail dot com [this message]
2013-04-21 23:26 ` dje at gcc dot gnu.org
2013-11-25 13:10 ` jamborm at gcc dot gnu.org
2021-12-25 11:32 ` [Bug rtl-optimization/51982] " pinskia at gcc dot gnu.org

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=bug-51982-4-Xx5VEIHs1C@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).