On Wed, Aug 8, 2012 at 5:56 PM, Ruben Van Boxem <[email protected]>wrote:
> 2012/8/8 Jean-Claude Beaudoin <[email protected]>
>
>>
>>
>> On Wed, Aug 8, 2012 at 1:39 AM, Dongsheng Song
>> <[email protected]>wrote:
>>
>>> I recommend you use '-march=x86-64' instead of '-march=nocona'.
>>>
>>
> I don't see that option listed
> here<http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html>,
> although my 32-bit GCC 4.6.3 seems to accept it. "nocona" is the last
> generation P4, Intel's first attempt at x86_64, and AMD's support of it
> isn't much worse. Again, see:
> http://en.wikipedia.org/wiki/SSE3
>
> I build optimized toolchains, and reserve my artistic right to fail on
> older systems (see PS for the very limited cases in which it actually
> matters)
>
>
>From gcc/config/i386/i386.c:processor_alias_table
gcc/config/i386/i386.c:processor_alias_table
{"prescott", PROCESSOR_NOCONA, CPU_NONE, PTA_MMX | PTA_SSE | PTA_SSE2 |
PTA_SSE3},
{"nocona", PROCESSOR_NOCONA, CPU_NONE, PTA_64BIT | PTA_MMX | PTA_SSE |
PTA_SSE2 | PTA_SSE3 | PTA_CX16 | PTA_NO_SAHF},
{"x86-64", PROCESSOR_K8, CPU_K8, PTA_64BIT | PTA_MMX | PTA_SSE |
PTA_SSE2 | PTA_NO_SAHF},
Nocona have PTA_SSE3 and PTA_CX16, this is not acceptable, e.g. pentium3,
pentium4, prescott,
K8, opteron, athlon64 and athlon-fx do not support these instructions.
But x86-64 have SSE2 and common x64 instructions, this should be enough.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
