From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8616 invoked by alias); 3 Apr 2002 10:36:06 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 8585 invoked by uid 61); 3 Apr 2002 10:36:05 -0000 Date: Wed, 03 Apr 2002 02:36:00 -0000 Message-ID: <20020403103605.8584.qmail@sources.redhat.com> To: Daniel.Diaz@univ-paris1.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: rth@gcc.gnu.org Reply-To: rth@gcc.gnu.org, Daniel.Diaz@univ-paris1.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@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 X-SW-Source: 2002-04/txt/msg00208.txt.bz2 List-Id: 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