https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55930
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-02
Known to work| |4.7.4
Summary|libatomic build failure if |[7/8/9 Regression]
|configured with |libatomic build failure if
|--disable-dependency-tracki |configured with
|ng |--disable-dependency-tracki
| |ng
Ever confirmed|0 |1
Known to fail| |4.8.0, 7.4.0, 8.3.0, 9.0
Severity|normal |minor
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Richard Purdie from comment #6)
> Its part of a Yocto Project build and we would only ever build it once so we
> don't need/want the overhead of the dependency tracking information.
But is there any noticeable overhead when using GCC to bootstrap?
Automake documents the option as:
Some compilers do not offer any practical way to derive the list of
dependencies as a side-effect of the compilation, requiring a separate
run (maybe of another tool) to compute these dependencies. The performance
penalty implied by these methods is important enough to disable them by
default.
That doesn't apply here though, because GCC is generating the dependencies via
-MD as a side effect of compilation. So there should be no need to use the
option (other than saving a bit of disk space during the build).
