public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/61605] Potential optimization: Keep unclobbered argument registers live across function calls
Date: Sun, 28 Sep 2014 07:22:00 -0000 [thread overview]
Message-ID: <bug-61605-4-LqrzOZAu8r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61605-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61605
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andi Kleen from comment #1)
> This is in theory implemented in mainline with -fuse-caller-save
> It doesn't seem to work for me though. I also didn't see the option doing
> anything on a larger program.
Most likely because it is not fully implemented for x86 :).
next prev parent reply other threads:[~2014-09-28 7:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 11:39 [Bug rtl-optimization/61605] New: " patrick at parcs dot ath.cx
2014-09-28 7:15 ` [Bug rtl-optimization/61605] " andi-gcc at firstfloor dot org
2014-09-28 7:22 ` pinskia at gcc dot gnu.org [this message]
2014-09-28 7:36 ` andi-gcc at firstfloor dot org
2014-09-29 10:24 ` vries at gcc dot gnu.org
2014-09-30 10:25 ` vries at gcc dot gnu.org
2014-09-30 10:29 ` vries at gcc dot gnu.org
2014-10-16 9:16 ` vries at gcc dot gnu.org
2014-10-17 6:37 ` vries at gcc dot gnu.org
2014-10-17 6:37 ` vries 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-61605-4-LqrzOZAu8r@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).