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 12:01:53 +0300 [thread overview]
Message-ID: <4A2B8201.8050904@redhat.com> (raw)
In-Reply-To: <200906071747.FFJ57396.MSOOQFVHtFOJLF@I-love.SAKURA.ne.jp>
Tetsuo Handa wrote:
> Avi Kivity wrote:
>
>> Does the attached patch help?
>>
> Unfortunately, no.
>
>
What if you change "rm" in the patch to "m"?
--
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 9:02 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 [this message]
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=4A2B8201.8050904@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