Hi
Matt, as maintainer of the GCC4 branch you should be aware of an issue
affecting the GCC4 build on x86. Some folks may consider this minor but I
believe it is important.
The issue arises as a side effect of the build method. To be precise, only
GCC Pass1 is run as `make bootstrap'. The other
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
On Mon, 1 Aug 2005, Randy McMurchy wrote:
Hi all,
A minor nit I noticed in the Chapter 5 GCC instructions (all versions):
Noted in the SBU times between Pass 1 and Pass 2 is that they seem to
be reversed. Pass 1 is shown to be 4.4 SBU and Pass 2 is 11.0. Shouldn't
these be the other way
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
just going by the numbers then, and that pass 1 is ~3 times the work,
11 is far too much, but does g++ actually add that much to the compile
time? ... granted i don't recall make test taking more than about
20-30 mins (3-4) SBU on my box ... so i guess 14 with the tests does
fall around the same
Greg Schafer wrote:
This should hopefully go onto the 3.4 branch soon.. which of course
means it'll be in 3.4.5. We can always backport it to 3.4.4 if
deemed necessary.
Here is the final patch as committed:
http://gcc.gnu.org/ml/gcc-cvs/2005-08/msg00052.html
In summary, if you need
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
