From: Richard Henderson <rth@twiddle.net>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
qemu-devel <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-ppc TCG assert with git master
Date: Fri, 13 Mar 2015 12:27:37 -0700 [thread overview]
Message-ID: <55033A29.9020906@twiddle.net> (raw)
In-Reply-To: <5502235B.2030004@ilande.co.uk>
On 03/12/2015 04:38 PM, Mark Cave-Ayland wrote:
> Ah great, you're able to reproduce the same issue locally. Hopefully
> this will give you both enough information to figure out what is
> happening in the optimiser...
Yep, just sent a simple fix.
r~
next prev parent reply other threads:[~2015-03-13 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 8:41 [Qemu-devel] qemu-system-ppc TCG assert with git master Mark Cave-Ayland
2015-03-12 10:30 ` Mark Cave-Ayland
2015-03-12 14:55 ` Bastian Koppelmann
2015-03-12 23:34 ` Mark Cave-Ayland
2015-03-12 15:41 ` Richard Henderson
2015-03-12 16:51 ` Bastian Koppelmann
2015-03-12 23:38 ` Mark Cave-Ayland
2015-03-13 19:27 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-12 23:49 Richard Henderson
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=55033A29.9020906@twiddle.net \
--to=rth@twiddle.net \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).