GCC build speed and backlog
andrew.stubbs at linaro.org
Wed Mar 28 11:02:10 UTC 2012
On Tue 27 Mar 2012 22:03:45 BST, Michael Hope wrote:
> The PandaBoard auto builders are having a hard time keeping with
> longer build and test times of 4.7 and the re-enabled libstdc++ tests.
> For reference, here's how much each step costs:
> Bootstrap GCC with C, C++, Fortran, and Obj-C: 9 hours
> Test GCC: 9.5 hours
> Test libstdc++: 4.4 hours
> Test libgomp: 0.9 hours
> Other tests: 0.2 hours
> for a grand total of 23.8 hours. Every new commit gives a merge
> request and trunk build for both A9 and ARMv5 giving 95 hours of
> compute time. GCC 4.6 takes five hours to build and 5.5 to test.
> This is just a FYI. I'll think about ways of speeding things up or
> adding capacity. An i.MX6 with 2 GB of RAM and SATA would be nice...
Have you experimented with --disable-build-with-cxx and/or
--disable-build-poststage1-with-cxx? (Actually, I think only the latter
is enabled by default.) I know C++ takes longer to compile, so maybe C
takes longer with the C++ compiler also?
Of course, it might be that this ceases to be an option sooner or
later, if GCC takes the plunge and uses C++ features.
More information about the linaro-toolchain