From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc64-dev@ozlabs.org, David Edelsohn <dje@watson.ibm.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: CONFIG_FRAME_POINTER on ppc/ppc64?
Date: Tue, 16 Aug 2005 11:44:33 +0200 [thread overview]
Message-ID: <62a65a7989df38a7e4b1400150dcb2e5@kernel.crashing.org> (raw)
In-Reply-To: <473FD762-FB04-4B63-93E9-11931492AC60@freescale.com>
>> Because -fomit-frame-pointer and -fno-omit-frame-pointer have no
>> effect on ppc or ppc64, I assume. :)
>
> I'm assuming that's a guess. The reason I ask that is my memory
> serves correctly r31 is used as the frame pointer if compiled that
> way. Maybe some GCC expert can chime in. I'll copy David Edelsohn
> and see if I get a response :)
Yes, GPR31 is used as frame pointer. All optimization
levels other than -O0 enable -fomit-frame-pointer. But
-fno-omit-frame-pointer certainly works.
Segher
prev parent reply other threads:[~2005-08-16 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 18:25 CONFIG_FRAME_POINTER on ppc/ppc64? Kumar Gala
2005-08-15 23:08 ` Paul Mackerras
2005-08-16 3:41 ` Kumar Gala
2005-08-16 4:03 ` David Edelsohn
2005-08-16 5:23 ` Paul Mackerras
2005-08-16 9:44 ` Segher Boessenkool [this message]
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=62a65a7989df38a7e4b1400150dcb2e5@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje@watson.ibm.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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 NNTP newsgroup(s).