From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guillaume Rousse Subject: Re: porting xen-detect ASM code into a shared library Date: Thu, 10 Jul 2008 14:43:37 +0200 Message-ID: <487603F9.7020703@inria.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser a =E9crit : >=20 >=20 > On 10/7/08 13:30, "Guillaume Rousse" wrote: >=20 >> Many thanks, it worked. I just hope this is not an error in original >> xc_cpuid_x86.c ccode (borrowed from >> http://lxr.xensource.com/lxr/source/tools/libxc/xc_cpuid_x86.c) >> >> Can I ensure upstream cfengine maintainer about portability of this co= de >> among various platforms and systems ? >=20 > 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,=20 if whose cpuid function is x86-only ? Or is it actually a way to=20 distinguish between gcc and other compilers ? And are they alternative for non-i386 arches ? --=20 Guillaume Rousse Moyens Informatiques - INRIA Futurs Tel: 01 69 35 69 62