On 8/20/2010 11:52 PM, Carsten Munk wrote:
[this is -not- a SSSE3 discussion thread nor should it turn into one]
We were having some discussions around in some bugs that things should
in general follow OBS project optflags/CFLAGS/CXXFLAGS. For MeeGo.com
builds this is naturally optimized for Atom.
I noticed the following default patch (see further down) in MeeGo gcc,
which seems to make the optflags a bit of a null-op as it overrides
them for x86 anyway.
Would it be saner to remove/disable this patch and solely rely on
CFLAGS/CXXFLAGS/optflags for MeeGo builds? This would be more
ecosystem-friendly and allow for proper flexibility of compilation
flags for any given target.
having gcc default to the MeeGo defaults is actually very sane (yes I
wrote this patch),
and I do not think you can argue anything else than that to be honest.
It would be the same as defaulting to -march=native, except that we
don't build on native exactly (we build on Core i7 like boxes)...
Having good defaults that we MeeGo want... are you really trying to
argue against that?
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
