From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 05/28] kvm tools: 64-bit tidy; use PRIx64 when printf'ing
 u64s and link appropriately
Date: Tue, 6 Dec 2011 21:05:38 +1100
Message-ID: <20111206100538.GA8178@bloggs.ozlabs.ibm.com>
References: <cover.1323141075.git.matt@ozlabs.org>
 <4EDD8E4D.5000309@ozlabs.org>
 <1323159238.3882.6.camel@lappy>
 <20111206082827.GA30062@elte.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Sasha Levin <levinsasha928@gmail.com>,
	Matt Evans <matt@ozlabs.org>, kvm@vger.kernel.org,
	kvm-ppc@vger.kernel.org, Pekka Enberg <penberg@cs.helsinki.fi>
To: Ingo Molnar <mingo@elte.hu>
Return-path: <kvm-ppc-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20111206082827.GA30062@elte.hu>
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Tue, Dec 06, 2011 at 09:28:27AM +0100, Ingo Molnar wrote:
> 
> * Sasha Levin <levinsasha928@gmail.com> wrote:
> 
> > Ingo actually got us to remove all the PRI* specifiers, but 
> > that was back when we only did x86 :)
> > 
> > Ingo, does it make sense to use them now when we support 
> > different architectures?
> 
> Not at all - ppc should use a sane u64/s64 definition, i.e. 
> int-ll64.h instead of the int-l64.h crap.
> 
> The powerpc maintainers indicated that they'd fix that, a couple 
> of years ago, but nothing appears to have come out of that.

We changed it for the kernel, but not for userspace (i.e. glibc)
because of concerns about possibly breaking existing userspace
programs.  I haven't looked closely at Matt's patches, but it should
be possible to use [un]signed long long for the u64/s64 types, I would
think.

Paul.