From: Avi Kivity <avi@redhat.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: guillaume.thouvenin@ext.bull.net, linux-kernel@vger.kernel.org
Subject: Re: [2.6.30-rc8 KVM] gcc 3.3 dies at emulate_2op_cl().
Date: Sun, 07 Jun 2009 09:24:14 +0300 [thread overview]
Message-ID: <4A2B5D0E.20002@redhat.com> (raw)
In-Reply-To: <200906050539.n555dwAQ077095@www262.sakura.ne.jp>
Tetsuo Handa wrote:
> (Continued from http://lkml.org/lkml/2009/6/4/14 )
> I tried to identify the location of gcc 3.3's internal error using
> "make CONFIG_DEBUG_INFO=1 arch/x86/kvm/x86_emulate.s", and it turned out that
> the location is emulate_2op_cl().
>
> Commenting out like below solves the gcc's internal error.
>
> diff --git a/arch/x86/kvm/x86_emulate.c b/arch/x86/kvm/x86_emulate.c
> index ca91749..561b9b6 100644
> --- a/arch/x86/kvm/x86_emulate.c
> +++ b/arch/x86/kvm/x86_emulate.c
> @@ -2070,7 +2070,7 @@ twobyte_insn:
> break;
> case 0xa4: /* shld imm8, r, r/m */
> case 0xa5: /* shld cl, r, r/m */
> - emulate_2op_cl("shld", c->src2, c->src, c->dst, ctxt->eflags);
> + //emulate_2op_cl("shld", c->src2, c->src, c->dst, ctxt->eflags);
> break;
> case 0xab:
> bts: /* bts */
> @@ -2080,7 +2080,7 @@ twobyte_insn:
> break;
> case 0xac: /* shrd imm8, r, r/m */
> case 0xad: /* shrd cl, r, r/m */
> - emulate_2op_cl("shrd", c->src2, c->src, c->dst, ctxt->eflags);
> + //emulate_2op_cl("shrd", c->src2, c->src, c->dst, ctxt->eflags);
> break;
> case 0xae: /* clflush */
> break;
>
> I think something is wrong with emulate_2op_cl() when compiled with gcc 3.3.5 .
>
>
This is on i386, not x86_64, yes?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-06-07 6:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 5:39 [2.6.30-rc8 KVM] gcc 3.3 dies at emulate_2op_cl() Tetsuo Handa
2009-06-07 6:24 ` Avi Kivity [this message]
2009-06-07 7:38 ` Tetsuo Handa
2009-06-07 8:29 ` Avi Kivity
2009-06-07 8:47 ` Tetsuo Handa
2009-06-07 9:01 ` Avi Kivity
2009-06-07 9:39 ` Tetsuo Handa
2009-06-07 9:40 ` Avi Kivity
2009-06-07 10:00 ` Tetsuo Handa
2009-06-07 10:03 ` Avi Kivity
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=4A2B5D0E.20002@redhat.com \
--to=avi@redhat.com \
--cc=guillaume.thouvenin@ext.bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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