mirror of
https://github.com/gentoo-mirror/gentoo.git
synced 2026-11-08 06:17:07 -08:00
33056c4e55b76cfdcee02c206acbfd770d7ae378
Get tests passing when LTO is used and rework USE=pgo handling while at it, as it's interlinked with LTO b/c of the upstream infra for it. This follows on from: *1764651a4f*f900949be8*f900949be8where I kept hitting misc issues where the build for the live ebuild failed with LTO or otherwise. With this, I only needed one patch to libctf's tests [0] which I've now pinged upstream. (I also had an odd single gprofng failure I haven't looked at yet.) * For LTO + (tests || pgo), always filter '-Wa,*'. This is an unfortunate one, but the bootstrap test fails with it. * USE=pgo no longer implies LTO. If -flto is being used, then we pass --enable-pgo-build=lto. If not, we pass --enable-pgo-build=yes. * For USE=pgo, filter out LTO after we applied the build system configuration, because otherwise there's a risk we're going to break the tests used for profiling. * In src_test, use a subshell to localise the filtering of flags we do. * For tests, pass {C,CXX,LD}FLAGS_FOR_TARGET to make, as otherwise it'll use what it found from configure (and e.g. pick up LTO again -> many tests fail as they're not intended to be used with it). [0] https://inbox.sourceware.org/binutils/87sf2evr35.fsf@esperi.org.uk/ Signed-off-by: Sam James <sam@gentoo.org>
…
…
Description
No description provided
9.8 GiB
Languages
Shell
98%
Roff
1.3%
Emacs Lisp
0.2%
C
0.1%