From: Uros Bizjak <ubizjak@gmail.com>
To: Michael Witten <mfwitten@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>,
Richard Guenther <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>,
Mark Mitchell <mark@codesourcery.com>,
Richard Henderson <rth@redhat.com>,
jh@suse.cz, "H.J. Lu" <hjl.tools@gmail.com>,
Andi Kleen <andi@firstfloor.org>, Andrew Haley <aph@redhat.com>,
David Daney <ddaney@caviumnetworks.com>,
Xinliang David Li <davidxl@google.com>,
Chris Lattner <clattner@apple.com>
Subject: Re: Turn on -fomit-frame-pointer by default for 32bit Linux/x86
Date: Sun, 08 Aug 2010 15:30:00 -0000 [thread overview]
Message-ID: <AANLkTim+RsVU983qExmKM987ZeXqmuc7BN=fXqX5pFkM@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimgyd1Hi7V0r7oQ23MEJ4zstaoC1gvgi5_AApHO@mail.gmail.com>
On Sun, Aug 8, 2010 at 5:00 PM, Michael Witten <mfwitten@gmail.com> wrote:
> On Sun, Aug 8, 2010 at 09:56, Uros Bizjak <ubizjak@gmail.com> wrote:
>>
>> IMO, we have to bite the bullet from time to time in order to improve
>> the generated code.
>
> What's your performance function?
See measurements at [1].
>
> I like backtraces.
>
So, you will be able to use --enable-frame-pointer configure option.
[1] http://gcc.gnu.org/ml/gcc-patches/2010-07/msg02034.html
Uros.
next prev parent reply other threads:[~2010-08-08 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 15:08 Uros Bizjak
2010-08-08 15:17 ` Michael Witten
2010-08-08 15:30 ` Uros Bizjak [this message]
2010-08-08 16:56 ` Bernd Schmidt
2010-08-08 17:01 ` Andi Kleen
2010-08-08 22:54 ` Michael Witten
2010-08-09 5:21 ` Andi Kleen
2010-08-08 17:07 ` Michael Witten
2010-08-10 19:54 ` H.J. Lu
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='AANLkTim+RsVU983qExmKM987ZeXqmuc7BN=fXqX5pFkM@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=andi@firstfloor.org \
--cc=aph@redhat.com \
--cc=clattner@apple.com \
--cc=davidxl@google.com \
--cc=ddaney@caviumnetworks.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=jh@suse.cz \
--cc=mark@codesourcery.com \
--cc=mfwitten@gmail.com \
--cc=rguenther@suse.de \
--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).