From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3736 invoked by alias); 25 Oct 2002 20:43:12 -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 3717 invoked by uid 61); 25 Oct 2002 20:43:12 -0000 Date: Fri, 25 Oct 2002 13:43:00 -0000 Message-ID: <20021025204312.3716.qmail@sources.redhat.com> To: davmac@ozonline.com.au, 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, davmac@ozonline.com.au, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: other/8335: problems with __builtin_frame_address when -fomit-frame-pointer used X-SW-Source: 2002-10/txt/msg01034.txt.bz2 List-Id: Synopsis: problems with __builtin_frame_address when -fomit-frame-pointer used State-Changed-From-To: open->feedback State-Changed-By: rth State-Changed-When: Fri Oct 25 13:43:12 2002 State-Changed-Why: Describe "doesn't work correctly". The result should be the address of the stack frame, with or without a frame pointer. The frame is at a known offset from the stack pointer, after all. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8335