[Bug bootstrap/68873] excessive duplicate checking during build

2016-08-31 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68873

Andrew Pinski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from Andrew Pinski  ---
> 26 checking how to hardcode library paths into programs... immediate

This is just a shell switch statement so it does not do much.

> 23 checking whether the C compiler works... yes

This is done by default by normal autoconf and caching it does not help because
the newly build gcc might not work.

Anyways caching won't help cross builds here.

[Bug bootstrap/68873] excessive duplicate checking during build

2015-12-12 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68873

Andrew Pinski  changed:

   What|Removed |Added

  Component|other   |bootstrap
   Severity|normal  |enhancement

--- Comment #1 from Andrew Pinski  ---
Basically each library that uses libtool does this.  Each multilib could use
its own cache instead of each library which would improve this.  But with -j48,
the time spent in configure scripts is minor still.