Compilation time (was Re: GCC 3.3)

Scott Wheeler wheeler@kde.org
Thu May 1 21:07:00 GMT 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 30 April 2003 20:45, Phil Edwards wrote:

> > I would suggest qt-3.1.1 for C++ sources -- no fancy things though.
 
>     compiling Qt without -ftime-report takes about an hour (and about
>     thrice that time with -ftime-report) on my pentium 4 (2GHz) box
>     running a GNU/Linux system.
> 
> Five hours falls into the hellishly long category.

Well, that's four hours (1 + 3) not five, but yes that's quite a while.

However, it really shouldn't take that long.  Qt specifically is built as 
(primarily) one shared library, plus some tools and plugins.  If you just 
build that shared library on my machine (1.4 GHz Athlon, Linux) it takes just 
under 11 minutes of CPU time for a "normal" build of just that shared 
library.  That roughly doubles to compile all of Qt (tools and plugins, but 
not examples).

Presuming that just this lib could be built in the benchmark and that the 
ratios above hold true, I think that 44 minutes != hellishly long.

This should be a reasonable metric for how C++ is used in the KDE project and 
would hopefully be beneficial to both the GCC folks and the KDE developers 
(who spend on average 14% of our lives staring at GCC's C++ output.  ;-) ).

Cheers,

- -Scott
 
- -- 
I believe that a scientist looking at nonscientific problems is just as dumb 
as the next guy. 
- --Richard Feynman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+sWVfQu0ByfY5QTkRAlTBAJ4jCWZXQ1vmr9JTTC8DEWCjBAY8HgCeMjID
tK3LJvv0GU4AUmHgWD2LrFA=
=PS5B
-----END PGP SIGNATURE-----



More information about the Gcc mailing list