From: Paolo Bonzini <pbonzini@redhat.com>
To: Jay Foad <jay.foad@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: gcc 4.4 miscompiling cpu_exec() ?
Date: Tue, 23 Feb 2010 19:18:34 +0100 [thread overview]
Message-ID: <4B841BFA.8010609@redhat.com> (raw)
In-Reply-To: <ee2e06e91002231017q24a55763t6f2d63f6938341c2@mail.gmail.com>
On 02/23/2010 07:17 PM, Jay Foad wrote:
>> Can you try this patch:
>
> It works! Thanks.
>
>> and if it works, possibly only each hunk of it?
>
> Just the first hunk: works!
> Just the second hunk: doesn't work
>
> Can you explain why the volatile is necessary? Or is it working around
> a problem with the compiler?
I don't know exactly without checking, but these were the main changes
introduced by my 24ebf5f31a178051cff1a4aab5ba621037191577 patch. I'll
send it out shortly.
Paolo
next prev parent reply other threads:[~2010-02-23 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 14:50 [Qemu-devel] gcc 4.4 miscompiling cpu_exec() ? Jay Foad
[not found] ` <4B840A59.3060407@aurel32.net>
2010-02-23 17:57 ` Jay Foad
2010-02-23 17:58 ` [Qemu-devel] " Paolo Bonzini
2010-02-23 18:17 ` Jay Foad
2010-02-23 18:18 ` Paolo Bonzini [this message]
2010-02-23 18:21 ` [Qemu-devel] [PATCH] declare saved_env_reg as volatile Paolo Bonzini
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=4B841BFA.8010609@redhat.com \
--to=pbonzini@redhat.com \
--cc=jay.foad@gmail.com \
--cc=qemu-devel@nongnu.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.