On 2011-12-30 15:07, Sergei Trofimovich wrote:
> On Wed, 28 Dec 2011 12:45:03 -0800
> Alan Coopersmith <alan.coopersm...@oracle.com> wrote:
>
>> C code checking __amd64__ mostly does so to find out the size of long &
>> pointers. Instructions are usually at the assembly level, not the C code
>> level.
>
> It's a very generic tet. Such software is already broken for very popular MSVC
> compiler
No, since MSVC defines _M_X64 instead. It does not define __amd64__.
> (or mingw64-gcc).
(mingw64-gcc is arguably broken too).
FWIW, I agree with Alan. __amd64__ has had a very specific meaning for
almost a decade. Please don't try to change the meaning now.
Peter Harris
--
Open Text Connectivity Solutions Group
Peter Harris http://connectivity.opentext.com/
Research and Development Phone: +1 905 762 6001
phar...@opentext.com Toll Free: 1 877 359 4866
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
