From: Jochen Roth <jroth@linux.vnet.ibm.com>
To: kvm@vger.kernel.org
Subject: potential gcc bug causes kvm-userspace build break
Date: Wed, 11 Mar 2009 19:10:08 +0100 [thread overview]
Message-ID: <49B7FE80.1010307@linux.vnet.ibm.com> (raw)
FYI
I just discovered a potential gcc bug which causes kvm-userspace builds
to break.
I looks like it happens only with the latest fedora rawhide gcc 4.4
https://bugzilla.redhat.com/show_bug.cgi?id=489753
The following patch circumvents this problem by just renaming R to REG.
People facing the same problem might find this patch useful.
diff --git a/user/test/x86/apic.c b/user/test/x86/apic.c
index 9c6205b..ec3777c 100644
--- a/user/test/x86/apic.c
+++ b/user/test/x86/apic.c
@@ -35,9 +35,9 @@ typedef struct {
} isr_regs_t;
#ifdef __x86_64__
-# define R "r"
+# define REG "r"
#else
-# define R "e"
+# define REG "e"
#endif
extern char isr_entry_point[];
@@ -54,14 +54,14 @@ asm (
"push %r9 \n\t"
"push %r8 \n\t"
#endif
- "push %"R"di \n\t"
- "push %"R"si \n\t"
- "push %"R"bp \n\t"
- "push %"R"sp \n\t"
- "push %"R"bx \n\t"
- "push %"R"dx \n\t"
- "push %"R"cx \n\t"
- "push %"R"ax \n\t"
+ "push %"REG"di \n\t"
+ "push %"REG"si \n\t"
+ "push %"REG"bp \n\t"
+ "push %"REG"sp \n\t"
+ "push %"REG"bx \n\t"
+ "push %"REG"dx \n\t"
+ "push %"REG"cx \n\t"
+ "push %"REG"ax \n\t"
#ifdef __x86_64__
"mov %rsp, %rdi \n\t"
"callq *8*16(%rsp) \n\t"
@@ -70,14 +70,14 @@ asm (
"calll *4+4*8(%esp) \n\t"
"add $4, %esp \n\t"
#endif
- "pop %"R"ax \n\t"
- "pop %"R"cx \n\t"
- "pop %"R"dx \n\t"
- "pop %"R"bx \n\t"
- "pop %"R"bp \n\t"
- "pop %"R"bp \n\t"
- "pop %"R"si \n\t"
- "pop %"R"di \n\t"
+ "pop %"REG"ax \n\t"
+ "pop %"REG"cx \n\t"
+ "pop %"REG"dx \n\t"
+ "pop %"REG"bx \n\t"
+ "pop %"REG"bp \n\t"
+ "pop %"REG"bp \n\t"
+ "pop %"REG"si \n\t"
+ "pop %"REG"di \n\t"
#ifdef __x86_64__
"pop %r8 \n\t"
"pop %r9 \n\t"
diff --git a/user/test/x86/vmexit.c b/user/test/x86/vmexit.c
index bd57bfa..bc81be9 100644
--- a/user/test/x86/vmexit.c
+++ b/user/test/x86/vmexit.c
@@ -19,9 +19,9 @@ static inline unsigned long long rdtsc()
#define N (1 << 22)
#ifdef __x86_64__
-# define R "r"
+# define REG "r"
#else
-# define R "e"
+# define REG "e"
#endif
int main()
@@ -31,7 +31,7 @@ int main()
t1 = rdtsc();
for (i = 0; i < N; ++i)
- asm volatile ("push %%"R"bx; cpuid; pop %%"R"bx"
+ asm volatile ("push %%"REG"bx; cpuid; pop %%"REG"bx"
: : : "eax", "ecx", "edx");
t2 = rdtsc();
printf("vmexit latency: %d\n", (int)((t2 - t1) / N));
next reply other threads:[~2009-03-11 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 18:10 Jochen Roth [this message]
2009-03-11 18:11 ` potential gcc bug causes kvm-userspace build break Glauber Costa
2009-03-11 18:30 ` Jochen Roth
2009-03-11 18:32 ` Glauber Costa
2009-03-11 18:41 ` Anthony Liguori
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=49B7FE80.1010307@linux.vnet.ibm.com \
--to=jroth@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox