public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: Daniel.Diaz@univ-paris1.fr, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: optimization/6004: gcc 3.0.4 always compiles main() with frame (and ebp) even with -fomit-frame-pointer and -ffixed-ebp
Date: Wed, 03 Apr 2002 02:36:00 -0000 [thread overview]
Message-ID: <20020403103605.8584.qmail@sources.redhat.com> (raw)
Synopsis: gcc 3.0.4 always compiles main() with frame (and ebp) even with -fomit-frame-pointer and -ffixed-ebp
State-Changed-From-To: analyzed->closed
State-Changed-By: rth
State-Changed-When: Wed Apr 3 02:36:04 2002
State-Changed-Why:
Correct analysis. One cannot absolutely prevent the
compiler from using the hard frame pointer.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6004
next reply other threads:[~2002-04-03 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 2:36 rth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 1:57 jakub
2002-03-19 9:36 Daniel.Diaz
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=20020403103605.8584.qmail@sources.redhat.com \
--to=rth@gcc.gnu.org \
--cc=Daniel.Diaz@univ-paris1.fr \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).