From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44332)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1WkKRJ-0000DJ-5Q
	for qemu-devel@nongnu.org; Tue, 13 May 2014 17:40:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1WkKRA-0004UM-5O
	for qemu-devel@nongnu.org; Tue, 13 May 2014 17:40:45 -0400
Received: from mail-qc0-x235.google.com ([2607:f8b0:400d:c01::235]:57596)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1WkKR9-0004UF-T5
	for qemu-devel@nongnu.org; Tue, 13 May 2014 17:40:36 -0400
Received: by mail-qc0-f181.google.com with SMTP id m20so1339798qcx.26
	for <qemu-devel@nongnu.org>; Tue, 13 May 2014 14:40:34 -0700 (PDT)
Sender: Richard Henderson <rth7680@gmail.com>
Message-ID: <5372914E.7080801@twiddle.net>
Date: Tue, 13 May 2014 14:40:30 -0700
From: Richard Henderson <rth@twiddle.net>
MIME-Version: 1.0
References: <5372870A.5010107@gmail.com>
	<CAFEAcA9JGV3i2K9VG7BwgfxypAWuVb+3GqpvrBLsybxqtwEANA@mail.gmail.com>
	<53728A80.1070107@twiddle.net> <53728F74.1000302@gmail.com>
In-Reply-To: <53728F74.1000302@gmail.com>
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: Tom Musta <tommusta@gmail.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>, Thomas Huth <thuth@linux.vnet.ibm.com>

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~