[Bug bootstrap/112422] Build process does a redundant number of checks ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112422 --- Comment #4 from Eric Gallager --- (In reply to Sam James from comment #3) > There's some stuff we could cache for sure but it wouldn't be the majority > of the checks - stuff like finding tools like awk, sed should work > regardless of which stage we're in and so on. gawk and sed were potential host modules at one point previously, too, but it looks like they've been removed, so yeah I guess it'd be safe for them now... anything that might fall in this category should get checked against Makefile.def to make sure there aren't already potential modules for them for people trying to combine trees or something...
[Bug bootstrap/112422] Build process does a redundant number of checks ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112422 Sam James changed: What|Removed |Added Blocks||84402 CC||sjames at gcc dot gnu.org --- Comment #3 from Sam James --- There's some stuff we could cache for sure but it wouldn't be the majority of the checks - stuff like finding tools like awk, sed should work regardless of which stage we're in and so on. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84402 [Bug 84402] [meta] GCC build system: parallelism bottleneck
[Bug bootstrap/112422] Build process does a redundant number of checks ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112422 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org Keywords||build --- Comment #2 from Eric Gallager --- A lot of that's just the way that autoconf works. You'd probably have to change the upstream implementation of certain autoconf macros to fix this. Alternatively, you could also try configuring with the "-C" flag to your configure script, which should cause configure results to be cached, but that can be rather fragile, as the config.cache files can stop your build if the slightest things to change. I suppose GCC could try sharing its config.cache files more widely between its various subdirectories, but that would be somewhat risky, given that some of the things that configure checks for could change due to the whole bootstrap process (fixincludes changes the headers available, the new compiler getting built changes which compiler should be found, and what features it has, the new runtime libraries getting built change what functions are available, and so on...)
[Bug bootstrap/112422] Build process does a redundant number of checks ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112422 Andrew Pinski changed: What|Removed |Added Component|c |bootstrap --- Comment #1 from Andrew Pinski --- I doubt configure is where most of the time is spent these days.
