public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 13:03:50 +0300	[thread overview]
Message-ID: <4A2B9086.20309@redhat.com> (raw)
In-Reply-To: <200906071900.GED43277.OtJOQFOFSMHVFL@I-love.SAKURA.ne.jp>

Tetsuo Handa wrote:
> Avi Kivity wrote:
>   
>> I can eliminate _tmp by using lahf/sahf, but it's not going to be a 
>> trivial patch.
>>     
>
> I don't know what's happening here.
>
> If I comment out (_dst).bytes == 2 , it compiles.
> The problem happens only "w" + "unsigned short" case.
>
> # diff -urp arch/x86/kvm/x86_emulate.c~ arch/x86/kvm/x86_emulate.c
> --- arch/x86/kvm/x86_emulate.c~ 2009-06-03 12:07:25.000000000 +0900
> +++ arch/x86/kvm/x86_emulate.c  2009-06-07 17:52:05.591542272 +0900
> @@ -461,8 +461,8 @@ static u32 group2_table[] = {
>         do {                                                                    \
>                 switch ((_dst).bytes) {                                         \
>                 case 2:                                                         \
> -                       __emulate_2op_cl(_op, _cl, _src, _dst, _eflags,         \
> -                                               "w", unsigned short);           \
> +                       /* __emulate_2op_cl(_op, _cl, _src, _dst, _eflags,      \
> +                          "w", unsigned short); */             \
>                         break;                                                  \
>                 case 4:                                                         \
>                         __emulate_2op_cl(_op, _cl, _src, _dst, _eflags,         \
>   

It's a gcc register allocator bug.  Bugs don't have to be reasonable.


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


      reply	other threads:[~2009-06-07 10:04 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
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 [this message]

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=4A2B9086.20309@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