qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tom Musta <tommusta@gmail.com>
To: Richard Henderson <rth@twiddle.net>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Thomas Huth <thuth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Bug in PPC TCG for rlwimi ?
Date: Tue, 13 May 2014 16:59:14 -0500	[thread overview]
Message-ID: <537295B2.8050407@gmail.com> (raw)
In-Reply-To: <5372914E.7080801@twiddle.net>

On 5/13/2014 4:40 PM, Richard Henderson wrote:
> On 05/13/2014 02:32 PM, Tom Musta wrote:
>> Here is the -d op output.  What does the "mov_i32 tmp0,r4" op mean
>> when r4 is an i64?
> 
> It's supposed to be the truncate.
> 
> I believe I know what's going on.  I've introduced this bug yesterday, of
> course.  Thomas Huth bisected a problem with an s390 host, and I strongly
> suspect that it's the same bug.  (I haven't been able to reserve an s390 build
> system today to verify.)
> 
> Try the tree prior to af3cbfbe8018ccc16fb3a0048e928f66f0d05e87 and see
> if things work.
> 
> Ho hum.  Patch coming soon.
> 
> 
> r~
> 

Yes ... that worked ... sort of.

I had to back up prior to this:

fdd8ec71847b5167a4be524c2d22d186fc3b6e3a is the first bad commit

to get to a point that built.

Thanks, Peter and Richard for the help.

      reply	other threads:[~2014-05-13 21:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 20:56 [Qemu-devel] Bug in PPC TCG for rlwimi ? Tom Musta
2014-05-13 21:09 ` Peter Maydell
2014-05-13 21:11   ` Richard Henderson
2014-05-13 21:32     ` Tom Musta
2014-05-13 21:40       ` Richard Henderson
2014-05-13 21:59         ` Tom Musta [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=537295B2.8050407@gmail.com \
    --to=tommusta@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@linux.vnet.ibm.com \
    /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).