Hi all, On Mon, Dec 13, 2010 at 07:07:10PM +0100, Francesco R wrote: > 2010/12/13 Konstantin Tokarev <annu...@yandex.ru> > > > > > > > 13.12.2010, 18:53, "Francesco R" <viv...@gmail.com>: > > > 2010/12/13 Ryan Hill <dirtye...@gentoo.org> > > >> On Sun, 12 Dec 2010 09:01:13 -0400 > > >> "Sergio D. Rodr?guez Inclan" <srinc...@gmail.com> wrote: > > >> > > >>> El 12/12/2010 02:46 a.m., Ryan Hill escribi?: > > >>> > I think the fewer sources of magic USE flags the better. Maybe we > > could > > >>> > document how to figure out what instruction sets a processor supports > > in the > > >>> > handbook instead. > > >> > > >>> A good manual would be greatly appreciated :) > > >> > > >> I wrote a guide a couple weeks ago that might be a good starting point. > > >> > > >> http://en.gentoo-wiki.com/wiki/Hardware_CFLAGS > > > > > > if I read correctly the article on the wiki it does circa what the script > > reported below does. > > > would be possible to adopt something similar for automatic C*FLAGS > > selection if someone step in willing to take the pain to mantain it.
I've been reading this thread, but I don't understand why we need to worry about this since the newer versions of gcc can figure it out automatically by using -march=native? Does -mcpu also have a native option for those who need to use -mcpu? William
pgpdtGAkSilGP.pgp
Description: PGP signature
