From: Roger Sayle <roger@eyesopen.com>
To: Richard Henderson <rth@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 16373: -fomit-frame-pointer when optimizing on x86
Date: Fri, 16 Jul 2004 23:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0407161355390.27525-100000@www.eyesopen.com> (raw)
In-Reply-To: <20040716191641.GB28693@redhat.com>
On Fri, 16 Jul 2004, Richard Henderson wrote:
> As for treating %ebp as fixed... well, I guess we could see what
> kind of improvement that gives.
Thanks, I'd really appreciate it.
If nothing else, the performance numbers would answer Zack's question
about the relative performance overhead of setting up and restoring the
frame pointer vs. the benefit of having %ebp available as a general
purpose register during register allocation.
Roger
--
next prev parent reply other threads:[~2004-07-16 20:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 0:54 Roger Sayle
2004-07-12 1:43 ` Joseph S. Myers
2004-07-12 2:19 ` Roger Sayle
2004-07-12 7:07 ` Jakub Jelinek
2004-07-12 8:18 ` Roger Sayle
2004-07-12 8:28 ` Andrew Pinski
2004-07-12 8:38 ` Michael Matz
2004-07-12 12:42 ` Jakub Jelinek
2004-07-12 18:03 ` Florian Weimer
2004-07-12 18:06 ` Paolo Bonzini
2004-07-12 18:19 ` Paolo Bonzini
2004-07-12 19:06 ` Florian Weimer
2004-07-12 19:07 ` Giovanni Bajo
2004-07-12 19:24 ` Jakub Jelinek
2004-07-12 19:31 ` Paolo Bonzini
2004-07-12 19:09 ` Jakub Jelinek
2004-07-12 23:43 ` Richard Henderson
2004-07-15 14:44 ` Roger Sayle
2004-07-15 14:54 ` Richard Henderson
2004-07-15 15:07 ` Roger Sayle
2004-07-15 16:04 ` Richard Henderson
2004-07-16 20:36 ` Roger Sayle
2004-07-16 21:12 ` Zack Weinberg
2004-07-17 0:41 ` Roger Sayle
2004-07-16 22:34 ` Richard Henderson
2004-07-16 23:27 ` Geert Bosch
2004-07-16 23:28 ` Roger Sayle [this message]
[not found] <Pine.LNX.4.44.0407111933390.11880-100000@nondot.org>
2004-07-12 3:11 ` Roger Sayle
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=Pine.LNX.4.44.0407161355390.27525-100000@www.eyesopen.com \
--to=roger@eyesopen.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rth@redhat.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).