Hi, On Tue, 23 Jul 2019, Jeff Law wrote:
> > great you found time to make this. It should become the default for > > -flto IMO. > I was going to hack it into the rpm configury bits since we have access > to the # cores there. But an auto-selector within GCC is even better. > > BTW, isn't this all going to wreck havoc with reproducible builds since > partitioning can affect code generation? That's one of our open > questions... See Richi for this, but the reason for -flto=auto (or just -flto, or whatever the endresult will be) is _also_ reproducible builds, because some packages like to encode the compile flags into their binaries and hence would change depending on build host just because of "-flto=32" vs. "-flto=64" even when the code remains exactly the same. Ciao, Michael.
