And rather than trusting gcc
-march=native to do the work for you, you would probably be better off
checking `grep ^flags /proc/cpuinfo' anyway. :)
Gentoo runs not only on Linux (remember about Gentoo Prefix), and this feature
is
system-dependend
--
Regards,
Konstantin
On Mon, 13 Dec 2010 18:41:07 -0600
Ryan Hill dirtye...@gentoo.org wrote:
Absolutely, -march=native should be used if you aren't using distcc.
This is about setting CPU-based USE flags (mmx, sse, etc.).
Exactly, or x86 CPU extensions based USE flags, more exactly.
It seems the thread has been
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
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.
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
On Mon, 13 Dec 2010 18:13:08 -0600
William Hubbs willi...@gentoo.org wrote:
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?
Absolutely, -march=native should be used
El 12/12/2010 02:46 a.m., Ryan Hill escribió:
On Sat, 11 Dec 2010 19:01:16 +
Matt Turnermatts...@gentoo.org wrote:
On Sat, Dec 11, 2010 at 5:57 PM, Jeroen Rooversj...@gentoo.org wrote:
[snip]
I agree that this could be better. To me, most of the problems with
this are due to users not
On Sun, 12 Dec 2010 13:09:08 -0500
ross smith r...@umich.edu wrote:
Perhaps something along the lines of: If CPU_FLAGS is empty or not defined,
set flags based on the -march and -mtune variables. If CPU_FLAGS is set,
respect what has been set there and ignore the other logic for defaults.
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
On Sun, Dec 12, 2010 at 11:09:01PM -0600, Ryan Hill wrote:
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
Dirkjan Ochtman posted on Sat, 11 Dec 2010 20:03:39 +0100 as excerpted:
On Sat, Dec 11, 2010 at 20:01, Matt Turner matts...@gentoo.org wrote:
I agree that this could be better. To me, most of the problems with
this are due to users not knowing which of these should be set for
their particular
On Sat, 11 Dec 2010 18:57:58 +0100
Jeroen Roovers j...@gentoo.org wrote:
Among all CPU extensions USE flags you'll find:
3dnow
3dnowext
mmx
mmxext
sse
sse2
sse3
sse4
sse4a
sse5
ssse3
I probably missed a few, there.
sse4.1, sse4.2, avx
sse5 was a draft, it was never implemented.
On Sat, 11 Dec 2010 19:01:16 +
Matt Turner matts...@gentoo.org wrote:
On Sat, Dec 11, 2010 at 5:57 PM, Jeroen Roovers j...@gentoo.org wrote:
[snip]
I agree that this could be better. To me, most of the problems with
this are due to users not knowing which of these should be set for
13 matches
Mail list logo
