This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc compile-time performance


> > Many of the "proprietary compilers" will shame GCC under the table
> > for compilation times.
>
> The front end of GNAT is very fast, so usually by far the larger part
> of the time is spent in the backend.  How does this compare with the
> C++ case?

I use two or three different C and, to a lesser degree, C++ compilers.
I'm sure you can stack the deck either way, but I'll say in loose terms
that it's *really* hard to stack the deck to allow GCC to "win" a
compilation time contest.   Whether or not that is an important criteria
to the GCC team isn't my point; my point is that GCC compile times are
out of line.

I started to included examples, but I'd rather not get into that level
of detaill yet.

RJL


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]