From: Roger Sayle <roger@eyesopen.com>
To: "Joseph S. Myers" <jsm@polyomino.org.uk>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR 16373: -fomit-frame-pointer when optimizing on x86
Date: Mon, 12 Jul 2004 02:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0407111725120.9462-100000@www.eyesopen.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407112325450.15563@digraph.polyomino.org.uk>
On Sun, 11 Jul 2004, Joseph S. Myers wrote:
> Performance statistics (compile time, run time and code size)? After all,
> the point of this change is presumably that it improves performance.
Do you have any doubt at all that this patch won't improve run-time,
reduce code size and speed up a bootstrapped compiler? :>
The bugzilla PR reports performance increases of up to 40% on some
benchmarks, and indeed the Intel and Microsoft C/C++ compilers omit
frame pointers by default. I'd hope that any gains will help redress
some of the tree-ssa related compile-time slow-down, but I haven't
done any timings. The benefits of -fomit-frame-pointer are otherwise
well documented by Robert Scott Ladd and others.
But the real reason I submitted the patch was to decrease the maintenance
burden of the six additional lines in i386.c that provide target dependent
defaults for flag_omit_frame_pointer, but break the documented semantics
of the CAN_DEBUG_WITHOUT_FP target macro. Any other side-effects of this
patch are unintentional and purely coincidental. :> The alternative
fix to PR middle-end/16373 is to change the documentation.
Roger
--
next prev parent reply other threads:[~2004-07-11 23:49 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 [this message]
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
[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.0407111725120.9462-100000@www.eyesopen.com \
--to=roger@eyesopen.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jsm@polyomino.org.uk \
/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).