On Wed, 20 Feb 2013, Woodhouse, David wrote: > On Wed, 2013-02-20 at 09:06 -0500, Nicolas Pitre wrote: > > On Wed, 20 Feb 2013, Woodhouse, David wrote: > > > > > On Wed, 2013-02-20 at 08:36 -0500, Nicolas Pitre wrote: > > > > You'll have the same issue wrt the above whether or not the source > > > > file is C or assembly. > > > > > > Hm, true. I was thinking of the code itself (which is > > > position-independent anyway), rather than the flags in the object file. > > > > > > So just ship a .S file and for the decompressor (if we need it at all) > > > rebuild it just the same as we do the *other* libgcc code like ashldi3.S > > > etc. > > > > ... in which case there is no harm shipping a .c file and trivially > > enforcing -O2, the rest being equal. > > For today's compilers, unless the wind changes.
We'll adapt if necessary. Going with -O2 should remain pretty safe anyway. Nicolas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
