From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KUdiL-0000GP-Pp
	for qemu-devel@nongnu.org; Sun, 17 Aug 2008 04:34:17 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KUdiK-0000Ff-3T
	for qemu-devel@nongnu.org; Sun, 17 Aug 2008 04:34:17 -0400
Received: from [199.232.76.173] (port=46068 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KUdiK-0000Fa-06
	for qemu-devel@nongnu.org; Sun, 17 Aug 2008 04:34:16 -0400
Received: from wf-out-1314.google.com ([209.85.200.172]:9057)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1KUdiJ-0007hg-Od
	for qemu-devel@nongnu.org; Sun, 17 Aug 2008 04:34:15 -0400
Received: by wf-out-1314.google.com with SMTP id 27so2411674wfd.4
	for <qemu-devel@nongnu.org>; Sun, 17 Aug 2008 01:34:14 -0700 (PDT)
Message-ID: <f43fc5580808170134ydd6f2e8w89b9ad9d41caa3fa@mail.gmail.com>
Date: Sun, 17 Aug 2008 11:34:14 +0300
From: "Blue Swirl" <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] sparc64 correct 32bit carry flag for add
	instruction
In-Reply-To: <b2fa41d60808170054h4197b208o3b1995337d569c14@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <b2fa41d60808170054h4197b208o3b1995337d569c14@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 8/17/08, Igor Kovalenko <igor.v.kovalenko@gmail.com> wrote:
> Hi!
>
>  The attached sparc64-add-carry-icc.patch should fix a problem with
>  setting 32bit carry flag after add instruction.
>  This at least fixes a problem with silo vprinf printing only least
>  significant digit of integers (now it can output address where it
>  loads kernel instead of 0x0)
>
>  Please apply.

Thanks, applied.