https://bugs.kde.org/show_bug.cgi?id=490651
--- Comment #11 from Mark Wielaard <m...@klomp.org> --- (In reply to Philippe Waroquiers from comment #10) > (In reply to Mark Wielaard from comment #9) > > It is definitely noticeable for me. And I have seen much longer build times > > on some non-x86_64 arches. > Effectively this gives more difference than my measurements. Yeah, I am really surprised you aren't seeing any difference with and without the one partition. Especially given you are using many more threads to build. > How much does the testing add ? make check is ~5 times slower with --enable-lto, adding CFLAGS="--lto-partition=one" makes it another ~3 times slower. make check -j12 real 0m6.492s user 0m25.506s sys 0m10.960s --enable-lto make check -j12 real 0m31.975s user 3m27.578s sys 0m24.597s CFLAGS="--lto-partition=one" real 1m30.105s user 2m6.856s sys 0m15.383s make regtest shows the opposite, it gets faster, but just a few seconds difference. All tests pass in all cases: == 922 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == make regtest real 10m42.997s user 6m57.130s sys 1m13.850s --enable-lto make regtest real 10m31.466s user 6m46.754s sys 1m14.648s CFLAGS="--lto-partition=one" make regtest real 10m27.229s user 6m42.505s sys 1m14.506s So it does indeed look like --enable-lto gives a slightly faster valgrind. Adding --lto-partition=one does make it a little faster, but not that much more. -- You are receiving this mail because: You are watching all bug changes.
