| 1 |
Hi all, |
| 2 |
|
| 3 |
On Mon, Dec 13, 2010 at 07:07:10PM +0100, Francesco R wrote: |
| 4 |
> 2010/12/13 Konstantin Tokarev <annulen@××××××.ru> |
| 5 |
> |
| 6 |
> > |
| 7 |
> > |
| 8 |
> > 13.12.2010, 18:53, "Francesco R" <vivo75@×××××.com>: |
| 9 |
> > > 2010/12/13 Ryan Hill <dirtyepic@g.o> |
| 10 |
> > >> On Sun, 12 Dec 2010 09:01:13 -0400 |
| 11 |
> > >> "Sergio D. Rodr?guez Inclan" <srinclan@×××××.com> wrote: |
| 12 |
> > >> |
| 13 |
> > >>> El 12/12/2010 02:46 a.m., Ryan Hill escribi?: |
| 14 |
> > >>> > I think the fewer sources of magic USE flags the better. Maybe we |
| 15 |
> > could |
| 16 |
> > >>> > document how to figure out what instruction sets a processor supports |
| 17 |
> > in the |
| 18 |
> > >>> > handbook instead. |
| 19 |
> > >> |
| 20 |
> > >>> A good manual would be greatly appreciated :) |
| 21 |
> > >> |
| 22 |
> > >> I wrote a guide a couple weeks ago that might be a good starting point. |
| 23 |
> > >> |
| 24 |
> > >> http://en.gentoo-wiki.com/wiki/Hardware_CFLAGS |
| 25 |
> > > |
| 26 |
> > > if I read correctly the article on the wiki it does circa what the script |
| 27 |
> > reported below does. |
| 28 |
> > > would be possible to adopt something similar for automatic C*FLAGS |
| 29 |
> > selection if someone step in willing to take the pain to mantain it. |
| 30 |
|
| 31 |
I've been reading this thread, but I don't understand why we need to |
| 32 |
worry about this since the newer versions of gcc can figure it out automatically |
| 33 |
by using -march=native? Does -mcpu also have a native option for those |
| 34 |
who need to use -mcpu? |
| 35 |
|
| 36 |
William |
Archives