This is the mail archive of the
mailing list for the GCC project.
Re: GCC 4.1: Buildable on GHz machines only?
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: pkoning at equallogic dot com (Paul Koning)
- Cc: pinskia at physics dot uc dot edu, gcc at gcc dot gnu dot org, matt at 3am-software dot com
- Date: Wed, 27 Apr 2005 17:35:32 -0400 (EDT)
- Subject: Re: GCC 4.1: Buildable on GHz machines only?
> >>>>> "Andrew" == Andrew Pinski <firstname.lastname@example.org> writes:
> >> However, I can always tell when a GCC build has hit the libjava
> >> build -- that's when the *whole system* suddenly slows to a crawl.
> >> Maybe it comes from doing some processing on 5000 foo.o files all
> >> at once... :-(
> Andrew> But that is not GCC fault that binutils cannot handle that
> Andrew> load.
> Perhaps not. But perhaps there are workarounds that allow the gcc
> build to do its job without using binutils in a way that stresses it
> beyond its ability to cope.
Well on ppc-darwin, linking libjava takes almost no time with only 256MB
of memory. What times the time on ppc-darwin with libjava is libtool
generating the list of files to link. So again this is a binutils problem
as it works just fine with a good linker.