https://bugs.kde.org/show_bug.cgi?id=338252
Ivo Raisr <iv...@ivosh.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iv...@ivosh.net
--- Comment #15 from Ivo Raisr <iv...@ivosh.net> ---
(In reply to Дилян Палаузов from comment #14)
> Autoconf users willing to compile everything with LTO just by calling
> ./configure put in /usr/local/etc/config.site:
>
> CFLAGS="-O3 -fno-fat-lto-objects -flto" CXXFLAGS="-O3 -fno-fat-lto-objects
> -flto" LDFLAGS="-Wl,-O1,-s -flto=4"
>
> And then any ./configure implies LTO. Just as other programs relying on
> autoconf doing the right thing do not offer --enable-lto option in
> ./configure --help, can be compiled with LTO, valgrind./configure --help
> shall not print --enable-lto. Programmer printing on --help "--enable-lto"
> don't understand autoconf. This applies also for artificially added -g or
> -O2 from configure.ac or contained in Makefile*
Thank you for this insight and sharing your approach. It is really helpful to
know that other possibilities exists.
However I modifying /usr/local/etc/config.site affects all projects build on a
box. Also we cannot force Valgrind users and maintainers to modify global
configuration file [consider shared build machines, for example in the gcc
build farm]. Perhaps a merged approach could be found?
--
You are receiving this mail because:
You are watching all bug changes.
