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.
On 12/28/11 3:29 PM, Lu, Hongjiu wrote:
__LP64__ isn't the part of x86-64 psABI while GCC always define __LP64__
for 64bit long on x86. I can check if other compilers do the same.
In most cases, __amd64__ is checked for 64bit instructions and we have
ported those we have found so far to x32 so
On Wed, 28 Dec 2011 12:45:03 -0800
Alan Coopersmith alan.coopersm...@oracle.com wrote:
On 12/28/11 12:29, Lu, Hongjiu wrote:
From: Lu, Hongjiuhongjiu...@intel.com
Date: Wed, 28 Dec 2011 14:34:09 +
__AMD64__ is defined when 64bit x86 instruction set is used,
which is true for x32.
On 12/28/11 06:34, Lu, Hongjiu wrote:
__AMD64__ is defined when 64bit x86 instruction set is used,
which is true for x32. The difference is x32 doesn't define
__LP64__.
Then you have explictly designed your ABI to break existing
software, and it is broken by design and should not be adopted.
Cc: Lu, Hongjiu; xorg-devel@lists.x.org
Subject: Re: [xproto: PATCH] Xmd.h: amd64-x32 ABI defines sizeof(long) ==
sizeof (void*) == 4
On 12/21/11 09:24, Sergei Trofimovich wrote:
What do you think of changing predefined __amd64__ define in gcc to
something
distinct?
If it's
On 12/28/11 07:33, Lu, Hongjiu wrote:
On 12/28/11 06:34, Lu, Hongjiu wrote:
__AMD64__ is defined when 64bit x86 instruction set is used,
which is true for x32. The difference is x32 doesn't define
__LP64__.
Then you have explictly designed your ABI to break existing
software, and it is broken
On 12/28/11 06:34, Lu, Hongjiu wrote:
__AMD64__ is defined when 64bit x86 instruction set is used,
which is true for x32. The difference is x32 doesn't define
__LP64__.
Then you have explictly designed your ABI to break existing
software, and it is broken by design and should not be
From: Lu, Hongjiu hongjiu...@intel.com
Date: Wed, 28 Dec 2011 14:34:09 +
__AMD64__ is defined when 64bit x86 instruction set is used,
which is true for x32. The difference is x32 doesn't define
__LP64__.
Chapter 7, Development Environment, of the AMD64 ABI (the non-x32
version) does
On 12/28/11 12:29, Lu, Hongjiu wrote:
From: Lu, Hongjiuhongjiu...@intel.com
Date: Wed, 28 Dec 2011 14:34:09 +
__AMD64__ is defined when 64bit x86 instruction set is used,
which is true for x32. The difference is x32 doesn't define
__LP64__.
Chapter 7, Development Environment, of the
From: Lu, Hongjiu hongjiu...@intel.com
Date: Wed, 28 Dec 2011 14:34:09 +
__AMD64__ is defined when 64bit x86 instruction set is used,
which is true for x32. The difference is x32 doesn't define
__LP64__.
Chapter 7, Development Environment, of the AMD64 ABI (the non-x32
[ CCing H.J.
context:
the thread start:
http://www.mail-archive.com/xorg-devel@lists.x.org/msg27303.html
reply to: http://www.mail-archive.com/xorg-devel@lists.x.org/msg27338.html
]
What would you prefer?
...
Is there any real benefit to AMD64-x32 over simply x86-32
Whole
On 12/21/11 09:24, Sergei Trofimovich wrote:
What do you think of changing predefined __amd64__ define in gcc to something
distinct?
If it's not an option, how about adding one more define for those who like to
check
for this exact feature on all compilers (and not only gcc)?
So thread
On 12/20/11 08:37, Sergei Trofimovich wrote:
+ (defined(__amd64__) defined(__LP64__)) /* skip x32 */ || \
+ defined(amd64) || \
Really? Someone defined __amd64__ on a non LP64 platform and didn't expect
to break tons of software? Amazing...
I'd expect damage from such idiocy to go
On 12/20/11 11:41 AM, Alan Coopersmith wrote:
On 12/20/11 08:37, Sergei Trofimovich wrote:
+ (defined(__amd64__) defined(__LP64__)) /* skip x32 */ || \
+ defined(amd64) || \
Really? Someone defined __amd64__ on a non LP64 platform and didn't expect
to break tons of software? Amazing...
Date: Tue, 20 Dec 2011 08:41:44 -0800
From: Alan Coopersmith alan.coopersm...@oracle.com
Are you sure that every real amd64 platform that uses __amd64__
defines __LP64__ as well?
Not sure if you'd call 64-bit Windows a real amd64 platform, but given
that Microsoft made the brilliant
On Tue, 20 Dec 2011 08:41:44 -0800
Alan Coopersmith alan.coopersm...@oracle.com wrote:
On 12/20/11 08:37, Sergei Trofimovich wrote:
+ (defined(__amd64__) defined(__LP64__)) /* skip x32 */ || \
+ defined(amd64) || \
Really? Someone defined __amd64__ on a non LP64 platform and
On 12/20/11 09:02, Mark Kettenis wrote:
Date: Tue, 20 Dec 2011 08:41:44 -0800
From: Alan Coopersmithalan.coopersm...@oracle.com
Are you sure that every real amd64 platform that uses __amd64__
defines __LP64__ as well?
Not sure if you'd call 64-bit Windows a real amd64 platform, but given
that
On Tue, 20 Dec 2011 18:02:18 +0100 (CET)
Mark Kettenis mark.kette...@xs4all.nl wrote:
Date: Tue, 20 Dec 2011 08:41:44 -0800
From: Alan Coopersmith alan.coopersm...@oracle.com
Are you sure that every real amd64 platform that uses __amd64__
defines __LP64__ as well?
Not sure if you'd
On 12/20/11 12:26, Sergei Trofimovich wrote:
What would you prefer?
I'd prefer not supporting broken hacks pretending to be new ABI models.
Is there any real benefit to AMD64-x32 over simply x86-32 or AMD64 for X
applications?
--
-Alan Coopersmith-alan.coopersm...@oracle.com
On 12/20/11 13:09, Sergei Trofimovich wrote:
On 12/20/11 12:26, Sergei Trofimovich wrote:
What would you prefer?
I'd prefer not supporting broken hacks pretending to be new ABI models.
Is there any real benefit to AMD64-x32 over simply x86-32
Whole AMD64 ISA is accessible: twice as much
On 12/20/11 08:37, Sergei Trofimovich wrote:
+ (defined(__amd64__) defined(__LP64__)) /* skip x32 */ || \
+ defined(amd64) || \
Really? Someone defined __amd64__ on a non LP64 platform and didn't expect
to break tons of software? Amazing...
A bit will break, yes. But
On 12/20/11 12:26, Sergei Trofimovich wrote:
What would you prefer?
I'd prefer not supporting broken hacks pretending to be new ABI models.
Is there any real benefit to AMD64-x32 over simply x86-32
Whole AMD64 ISA is accessible: twice as much registers (including xmm/ymm),
instruction
22 matches
Mail list logo
