This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: -fomit-frame-pointer is evil
- From: root <root at ibe dot miee dot ru>
- To: carlo at alinoe dot com (Carlo Wood)
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 28 Dec 2001 23:36:17 +0300 (MSK)
- Subject: Re: -fomit-frame-pointer is evil
>
> On Fri, Dec 28, 2001 at 02:56:34PM +0300, root wrote:
> > Hello there guys,
> > seems like i`ve narrowed down the cause of gcc build failure
> > the difference between CFLAGS="-Os -pipe -fomit-frame-pointer"
> > and "-Os -pipe" seems to kill gcc build on unwind-dw2.c due
> > to segfault on the second stage.
> > this is all about gcc-3.0.3
> >
> > regards, Samium Gromoff
>
> I once reported a problem a-like and narrowed that
> down to the combination of -fdefer-pop -fomit-frame-pointer
> Can you check if your problem also is caused by
> that combination? Thus, use
> CFLAGS="-pipe -fdefer-pop -fomit-frame-pointer"
yeah sure, it can be, but i think it almost surely caused by
-fomit-frame-pointer, cause its the common case of my and yours
experiences...
in fact some time ago i`ve thought it was caused by cpu-specific cflags
like -march=pentium etc, but once i`ve tried those i`ve reported
i`m almost 100% sure its the -fomit... (since its the intersection
of my multiple build failures...)
>
> It might still be the same problem - that never was fixed.
>
> --
> Carlo Wood <carlo@alinoe.com>
>
regards, Samium Gromoff