From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48866)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tommusta@gmail.com>) id 1WkKjS-0008Ag-1O
	for qemu-devel@nongnu.org; Tue, 13 May 2014 17:59:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tommusta@gmail.com>) id 1WkKjJ-00020y-0f
	for qemu-devel@nongnu.org; Tue, 13 May 2014 17:59:29 -0400
Received: from mail-yh0-x229.google.com ([2607:f8b0:4002:c01::229]:65424)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tommusta@gmail.com>) id 1WkKjI-00020r-Sw
	for qemu-devel@nongnu.org; Tue, 13 May 2014 17:59:20 -0400
Received: by mail-yh0-f41.google.com with SMTP id f73so947927yha.28
	for <qemu-devel@nongnu.org>; Tue, 13 May 2014 14:59:20 -0700 (PDT)
Message-ID: <537295B2.8050407@gmail.com>
Date: Tue, 13 May 2014 16:59:14 -0500
From: Tom Musta <tommusta@gmail.com>
MIME-Version: 1.0
References: <5372870A.5010107@gmail.com>
	<CAFEAcA9JGV3i2K9VG7BwgfxypAWuVb+3GqpvrBLsybxqtwEANA@mail.gmail.com>
	<53728A80.1070107@twiddle.net> <53728F74.1000302@gmail.com>
	<5372914E.7080801@twiddle.net>
In-Reply-To: <5372914E.7080801@twiddle.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Bug in PPC TCG for rlwimi ?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

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.