RFA: Set default optimization level to -O2 for -flto
Basile Starynkevitch
basile@starynkevitch.net
Fri Mar 19 14:32:00 GMT 2010
H.J. Lu wrote:
>
> Should we record compiler options in .o files? For some targets, you may need
> -fPIC with -flto if -fPIC is used to build .o files.
I thought it was already the case....
Anyway, to check compatibility of compile versus link time optimisation
flag, we need to store them somewhere...
But yes, I believe that at least in -flto mode, we better should store
all the compile flags (those listed in comments when running
-fverbose-asm -S) somewhere in the object file.
BTW, are we talking about patching 4.5 before its release or about 4.6?
If 4.5 can be patched to improve a new feature, I respectfully ask for
someone to review the
http://gcc.gnu.org/ml/gcc-patches/2010-03/msg00644.html patch which
enables short plugin names like -fplugin=treehydra instead of
-fplugin=/some/distribution/path/to/treehydra.so
Cheers
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
More information about the Gcc-patches
mailing list