Greg Schafer wrote:
Matthew Burgess wrote:
I assume they've fixed all the problems with -fomit-frame-pointer?
What problems?
I can't remember definitive examples, I'm afraid. I just know that some
software either didn't compile or demonstrated erratic behaviour with
that flag specified.
Greg Schafer wrote:
In a nutshell, if you build x86 GCC4 with `make bootstrap' you end up with a
compiler that was itself compiled with `-O2 -g -fomit-frame-pointer'. If you
build x86 GCC4 with plain old `make' you end up with a compiler that was
itself compiled with `-O2 -g'. Notice the lack
Greg Schafer wrote:
GCC Makefile variable `XCFLAGS'. Something like the following sed (ONLY for
GCC Pass2 and Ch 6 GCC) achieves the desired effect for me:
sed -i '/^XCFLAGS/s/$/ -fomit-frame-pointer/' gcc/Makefile.in
Please forgive me if I'm missing something here, but I'm not quite sure
Jeremy Huntwork wrote:
Please forgive me if I'm missing something here, but I'm not quite sure
I'm seeing how this could work.
# grep -c XCFLAGS Makefile.in
0
Apologies on the above - of course this is down to my failing. My eyes
missed the gcc, so I ran grep on Makefile.in and not
Jeremy Huntwork wrote:
In any case, what would be the difference between what you're trying to
accomplish with a sed and the results of something like:
make CFLAGS=-g -O2 -fomit-frame-pointer
Still curious about the difference of the sed vs. the above command...
Yes, that was how I
Matthew Burgess wrote:
I assume they've fixed all the problems with -fomit-frame-pointer?
What problems? In the past some software certainly broke with it, but I'm
not sure where the blame lied.
But that is orthogonal to this discussion anyway. The GCC devs believe
that compiling GCC-4.x