WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] size_t and printk and Xen

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] size_t and printk and Xen
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sun, 12 Oct 2008 10:22:43 +0100
Cc:
Delivery-date: Sun, 12 Oct 2008 02:22:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1b70e8bc-7d46-4ad0-baad-9b9e985bf018@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcksTBSCUy+siZg/Ed22twAWy6hiGQ==
Thread-topic: [Xen-devel] size_t and printk and Xen
User-agent: Microsoft-Entourage/11.4.0.080122
On 11/10/08 15:05, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> I am adding code in Xen that printk's a size_t and find that
> I can't write code (short of ifdef'ing) that compiles on
> both 32-bit and 64-bit because size_t is typedef'd in Xen as an
> unsigned long.  C.f.

Cast to an int or to a long? Use %z?

> http://www.velocityreviews.com/forums/t438359-portable-way-to-printf-a-sizet-i
> nstance.html
> 
> It appears that the %z format is understood by Xen printk.
> 
> Is the typedef historical and should be removed?  Or is it
> necessary for some (older?) compilers?

Removing it would break the build, I think.

 -- Keir

> If it is not going to be removed, is there a workaround
> (other than ifdef'ing)?



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel