From: Anthony Liguori <aliguori@us.ibm.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: David F Barrera <dfbp@us.ibm.com>,
xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: PIC register 'bx' clobbered in 'asm' - xen-unstable build error
Date: Fri, 25 Feb 2005 15:44:20 -0600 [thread overview]
Message-ID: <421F9C34.6000609@us.ibm.com> (raw)
In-Reply-To: <1109366255.5970.2.camel@thinkpad>
Jerone Young wrote:
>The big question is why are you clobbering bx , dx registers on get
>cpuid:
>
>
CPUID returns information in eax, ebx, ecx, and edx. With -fPIC you
have to push ebx onto the stack before calling cpuid and pop it
afterward as Bin points out is what the patch to xen-unstable does.
Regards,
> _asm__ __volatile__ ("cpuid"
> : "=a" (eax), "=c" (ecx)
> : "0" (1)
> : "bx", "dx");
>
>You can change this to:
>
> _asm__ __volatile__ ("cpuid"
> : "=a" (eax), "=c" (ecx)
> : "0" (1)
> );
>
>But I am not sure why this is there?
>
>
>
>On Fri, 2005-02-25 at 15:02 -0600, David F Barrera wrote:
>
>
>>I am trying to build xen-unstable on an x86 box, but it is failing with
>>the following message:
>>
>>gcc -DPIC -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I
>>../../tools/libxutil -I. -Wp,-MD,.xc_rrobin.opic.d -fPIC -c -o
>>xc_rrobin.opic xc_rrobin.c
>>gcc -DPIC -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -I
>>../../tools/libxutil -I. -Wp,-MD,.xc_vmx_build.opic.d -fPIC -c -o
>>xc_vmx_build.opic xc_vmx_build.c
>>xc_vmx_build.c: In function `vmx_identify':
>>xc_vmx_build.c:468: error: PIC register `bx' clobbered in `asm'
>>make[4]: *** [xc_vmx_build.opic] Error 1
>>make[4]: Leaving directory `/tmp/xen-unstable/tools/libxc'
>>make[3]: *** [all] Error 2
>>make[3]: Leaving directory `/tmp/xen-unstable/tools/libxc'
>>make[2]: *** [install] Error 2
>>make[2]: Leaving directory `/tmp/xen-unstable/tools'
>>make[1]: *** [tools] Error 2
>>make[1]: Leaving directory `/tmp/xen-unstable'
>>make: *** [world] Error 2
>>make world failed
>>
>>I have built xen-unstable on this machine before, so I don't believe it
>>is a setup problem. Has anyone else observed this?
>>
>>David F Barrera
>>
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/xen-devel
>>
>>
>>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-25 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 21:02 PIC register 'bx' clobbered in 'asm' - xen-unstable build error David F Barrera
2005-02-25 21:17 ` Jerone Young
2005-02-25 21:44 ` Anthony Liguori [this message]
[not found] ` <mailman.1109368025.9618@unix-os.sc.intel.com>
2005-02-25 23:19 ` Arun Sharma
2005-02-25 21:21 ` Bin Ren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=421F9C34.6000609@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=dfbp@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.