From: "H. Peter Anvin" <hpa@zytor.com>
To: "Blower, Melanie" <melanie.blower@intel.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"avi@redhat.com" <avi@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: compilation issue, inline assembly arch/x86/kvm/emulate.c fails at -O0
Date: Wed, 21 Nov 2012 13:35:03 -0800 [thread overview]
Message-ID: <50AD4907.5040102@zytor.com> (raw)
In-Reply-To: <B3584E72CFEBED439A3ECA9BCE67A4EF1B17AF90@FMSMSX107.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
On 11/14/2012 11:45 AM, Blower, Melanie wrote:
> [1.] gcc -O0 assembly arch/x86/kvm/emulate.c gets compilation failure -- incorrect register restrictions
> [2.] Full description of the problem/report:
> I'm trying to compile this file at -O0, but gcc chokes in register allocation at the inline assembly.
>
> In the ordinary Linux build, this file compiles with gcc at -O2, without compilation errors.
>
> At -O0, gcc chokes with this message:
> gcc -w -c ./emulateE.c // (using preprocessed file)
> ./emulateE.c: In function `em_mul_ex':
> ./emulateE.c:1918:5: error: can't find a register in class `AREG' while reloading `asm'
> ./emulateE.c:1918:5: error: `asm' operand has impossible constraints
>
> Explanation:
> The file contains an inline asm of a kind:
>
> __asm__ __volatile__ ( " ..... " :
>
> "=m" ((ctxt)->eflags), "=&r" (_tmp), "+a" (*rax), "+d" (*rdx), "+qm"(ex) :
> "i" (11), "m" ((ctxt)->src . val), "a" (*rax), "d" (*rdx));
>
> Note that "+a" in inputs already means that eax is the return value. An then "a" is used as an output constraint too.
>
Hi Melanie,
Can you test the attached patch?
-hpa
[-- Attachment #2: 0001-x86-kvm-Remove-incorrect-redundant-assembly-constrai.patch --]
[-- Type: text/x-patch, Size: 1425 bytes --]
>From f8d8e2842ca05fd89788e35c087f02c6159b023a Mon Sep 17 00:00:00 2001
From: "H. Peter Anvin" <hpa@linux.intel.com>
Date: Wed, 21 Nov 2012 13:29:20 -0800
Subject: [PATCH] x86, kvm: Remove incorrect redundant assembly constraint
In __emulate_1op_rax_rdx, we use "+a" and "+d" which are input/output
constraints, and *then* use "a" and "d" as input constraints. This is
incorrect, but happens to work on some versions of gcc.
However, it breaks gcc with -O0 and icc, and may break on future
versions of gcc.
Reported-by: Melanie Blower <melanie.blower@intel.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Link: http://lkml.kernel.org/r/B3584E72CFEBED439A3ECA9BCE67A4EF1B17AF90@FMSMSX107.amr.corp.intel.com
---
arch/x86/kvm/emulate.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index 39171cb..bba39bf 100644
--- a/arch/x86/kvm/emulate.c
+++ b/arch/x86/kvm/emulate.c
@@ -426,8 +426,7 @@ static void invalidate_registers(struct x86_emulate_ctxt *ctxt)
_ASM_EXTABLE(1b, 3b) \
: "=m" ((ctxt)->eflags), "=&r" (_tmp), \
"+a" (*rax), "+d" (*rdx), "+qm"(_ex) \
- : "i" (EFLAGS_MASK), "m" ((ctxt)->src.val), \
- "a" (*rax), "d" (*rdx)); \
+ : "i" (EFLAGS_MASK), "m" ((ctxt)->src.val)); \
} while (0)
/* instruction has only one source operand, destination is implicit (e.g. mul, div, imul, idiv) */
--
1.7.11.7
next prev parent reply other threads:[~2012-11-21 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 19:45 PROBLEM: compilation issue, inline assembly arch/x86/kvm/emulate.c fails at -O0 Blower, Melanie
2012-11-15 0:14 ` H. Peter Anvin
2012-11-15 15:09 ` Blower, Melanie
2012-11-15 15:09 ` Blower, Melanie
2012-11-21 21:35 ` H. Peter Anvin [this message]
2012-11-21 22:31 ` Blower, Melanie
2012-11-21 22:31 ` Blower, Melanie
2012-11-21 22:41 ` [PATCH] x86, kvm: Remove incorrect redundant assembly constraint H. Peter Anvin
2012-11-26 7:22 ` Paolo Bonzini
2012-11-26 22:48 ` H. Peter Anvin
2012-11-26 23:48 ` Marcelo Tosatti
2012-11-26 23:49 ` H. Peter Anvin
2012-11-27 0:53 ` Marcelo Tosatti
2012-11-27 0:01 ` [tip:x86/urgent] " tip-bot for H. Peter Anvin
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=50AD4907.5040102@zytor.com \
--to=hpa@zytor.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=melanie.blower@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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.