From: "Sam Lauber" <sam124@operamail.com>
To: "Eric Botcazou" <ebotcazou@libertysurf.fr>, gcc@gcc.gnu.org
Subject: Re: Unomitted frame pointers
Date: Sat, 11 Dec 2004 16:15:00 -0000 [thread overview]
Message-ID: <20041211161501.E0D6723CE8@ws5-3.us4.outblaze.com> (raw)
Then why does -fomit-frame-pointer work on x86 at all? Then that option to omit a frame pointer shall be omitted ;). At least on x86. As for ABI, I simply don't understand this kind of stuff, because there is not enough information and documentation, and I don't have the time to check out the GCC source tree every time I want to look at something. And I _still_ don't recall any warning. I ran strings on GCC, and the only thing I saw was in the builtin specs saying "-pg and -fomit-frame-pointer are incompatible". You must be using 4.0 or 3.3. Why does it have to dynamically align the frame pointer? And _I'm_ not using an old 8086, I've got a Pentium III! I find your comment a bit insulting. And what's the valid reason this time?
Samuel Lauber
----- Original Message -----
From: "Eric Botcazou" <ebotcazou@libertysurf.fr>
To: "Sam Lauber" <sam124@operamail.com>
Subject: Re: Unomitted frame pointers
Date: Sat, 11 Dec 2004 09:08:31 +0100
>
> > What messages?
>
> I already posted the same advice once.
>
> > I HAD to call my function main, because it was main.
>
> You don't understand. Don't do your experiment on a function called 'main',
> it is very special in C. The bottom line is that it must dynamically align
> the stack pointer on x86 because of an antiquated ABI, thus preventing
> -fomit-frame-pointer to be effective.
>
> And keep in mind that GCC has been working on x86 for more than 15 years, so
> it can't do as dumb things as you think it does. There is almost always a
> valid reason.
>
> --
> Eric Botcazou
--
_____________________________________________________________
Web-based SMS services available at http://www.operamail.com.
From your mailbox to local or overseas cell phones.
Powered by Outblaze
next reply other threads:[~2004-12-11 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 16:15 Sam Lauber [this message]
2004-12-11 17:00 ` Eric Botcazou
2004-12-11 18:10 ` Robert Dewar
2004-12-13 6:16 ` Ranjit Mathew
2004-12-13 14:22 ` Robert Dewar
2004-12-13 23:36 ` Ben Elliston
-- strict thread matches above, loose matches on Subject: below --
2004-12-11 16:29 Sam Lauber
2004-12-12 1:33 ` Ian Lance Taylor
2004-12-11 16:26 Sam Lauber
2004-12-11 16:42 ` Nathan Sidwell
2004-12-12 0:09 ` Peter Barada
2004-12-11 2:44 Sam Lauber
2004-12-11 15:40 ` Nathan Sidwell
2004-12-11 15:45 ` Andreas Schwab
2004-12-11 2:37 Sam Lauber
2004-12-10 15:44 Thomas R. Truscott
2004-12-10 16:05 ` jlh
2004-12-10 16:25 ` Dave Korn
2004-12-10 16:30 ` Nathan Sidwell
2004-12-10 16:41 ` Dave Korn
2004-12-10 17:54 ` Nathan Sidwell
2004-12-10 16:33 ` Andreas Schwab
2004-12-10 16:40 ` Dave Korn
2004-12-10 16:55 ` Thomas R. Truscott
2004-12-10 17:26 ` Paul Brook
2004-12-11 11:53 ` Kai Henningsen
2004-12-10 5:26 Sam Lauber
2004-12-10 7:22 ` Eric Botcazou
2004-12-10 9:08 ` Richard Guenther
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=20041211161501.E0D6723CE8@ws5-3.us4.outblaze.com \
--to=sam124@operamail.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).