From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Uros Bizjak <ubizjak@gmail.com>
Subject: Re: Turn on -fomit-frame-pointer by default for 32bit x86?
Date: Tue, 13 Jul 2010 21:44:00 -0000 [thread overview]
Message-ID: <AANLkTik3lscBi701mjd2WXMdniBwHKd1L2Q6DY2hvpYA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim6oFDFKcYeuuNO8qbGu-BXzy5MPUST0-HAT1Tn@mail.gmail.com>
On Tue, Jul 13, 2010 at 2:02 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> On Tue, Jul 13, 2010 at 2:01 PM, Andrew Pinski <pinskia@gmail.com> wrote:
>> On Tue, Jul 13, 2010 at 1:59 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>> What will stop working when -fomit-frame-pointer is on?
>>
>> backtraces when debugging information is not turned on.
>
> See http://gcc.gnu.org/ml/gcc-patches/2004-08/msg01033.html and many
> more. This is not the first time this has been discussed.
Most of 32bit x86 assembly codes in glibc have .eh_frame section.
If backtrace is absolutely needed, they can add -fasynchronous-unwind-tables
or -fno-omit-frame-pointer.
--
H.J.
next prev parent reply other threads:[~2010-07-13 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 18:15 H.J. Lu
2010-07-13 20:40 ` Richard Guenther
2010-07-13 20:59 ` H.J. Lu
2010-07-13 21:02 ` Andrew Pinski
2010-07-13 21:03 ` Andrew Pinski
2010-07-13 21:44 ` H.J. Lu [this message]
2010-07-14 8:09 ` Richard Guenther
2010-07-14 13:47 ` H.J. Lu
2010-07-14 21:55 ` H.J. Lu
2010-07-14 12:00 ` Dave Korn
2010-07-16 19:35 ` Andi Kleen
2010-07-16 19:43 ` Jeff Law
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=AANLkTik3lscBi701mjd2WXMdniBwHKd1L2Q6DY2hvpYA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=ubizjak@gmail.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).