My experience is that use of the "-fomit-frame-pointer" switch will also 
break C++ code compiled with RedHat's compiler.  Sometimes the problem is 
manifested as an ICE (Mozilla 0.9.2) and sometimes the code will compile 
but cause a fault at runtime (kdelibs 2.1.x).

Good: "-march=i686 -O2"
Bad: "-march=i686 -O2 -fomit-frame-pointer"

FYI.


On Wednesday 08 August 2001 10:25 am, Kathy Bieltz wrote:
> I submitted a report to bugzilla and
> received the following comment:
> "+-fschedule-insns is not to be used on register starved machines like
> i386.
> +It generally creates much worse code on those, plus results in reload
> errors
> +too.
> +-fschedule-insns2 is more appropriate on i386, but -O2 already enables
> it
> +by default.
> "
> I removed the '--schedule-insns' option and
> my C++ library compiled fine.
>
> My thanks to the folks at redhat who answered
> so promptly.
>
> Kathy Bieltz
>
> Kathy Bieltz wrote:
> > The same C++ code that compiles with kgcc and gcc-2.91-66 fails when
> > I attempt to compile it with gcc-2.96-85.  Here is the log of the make:
> > /usr/bin/gcc -c -Wall -O2 -I. --schedule-insns -DINTEL -DUNIX -DLINUX
> > -DSVR4 Array.cpp -fPIC -DPIC -o obj/Array.o
> > /usr/bin/gcc -c -Wall -O2 -I. --schedule-insns -DINTEL -DUNIX -DLINUX
> > -DSVR4 Cache.cpp -fPIC -DPIC -o obj/Cache.o
> > Cache.cpp: In method `Bool Cache::Remove (MntrObject *, int)':
> > Cache.cpp:128: Unable to find a register to spill in class `AREG'.
> > Cache.cpp:128: confused by earlier errors, bailing out
> > make[4]: *** [obj/Cache.o] Error 1
> > make[3]: *** [releaseso] Error 2
> > make[2]: *** [releaseso] Error 2
> > make[1]: *** [releaseso] Error 2
> > make: *** [releaseso] Error 2
> >
> > I need to compile this C++ library with gcc-2.96-85 so I can link it
> > into other executables compiled with gcc-2.96-85.  I can't compile
> > working executables for RH 7.1 until I get this fixed.
> >
> > Any ideas on work-around or fix would be appreciated.
> >
> > Thanks!
> > Kathy Bieltz
> >
> > _______________________________________________
> > Seawolf-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/seawolf-list
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to