From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: porting xen-detect ASM code into a shared library
Date: Thu, 10 Jul 2008 13:44:14 +0100
Message-ID: <C49BC2AE.23DDF%keir.fraser@eu.citrix.com>
References: <487603F9.7020703@inria.fr>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <487603F9.7020703@inria.fr>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Guillaume Rousse <Guillaume.Rousse@inria.fr>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org




On 10/7/08 13:43, "Guillaume Rousse" <Guillaume.Rousse@inria.fr> wrote:

>> It's gcc and x86 specific of course. Beyond that it is portable (across OSes
>> for example).
> What's the point of #ifdef __i386__ for the %ebx register usage issue,
> if whose cpuid function is x86-only ? Or is it actually a way to
> distinguish between gcc and other compilers ?
> 
> And are they alternative for non-i386 arches ?

__i386__ versus __x86_64__

 -- Keir