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] sizeof(long) different under windows x64 and linuxx64

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] sizeof(long) different under windows x64 and linuxx64
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 23 Jan 2008 08:04:01 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Daniel Stodden <dns@xxxxxxxxxxxx>
Delivery-date: Wed, 23 Jan 2008 00:04:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0131A8B7@trantor>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchdW4p34/o0V6x/QIKObXgZsSaouAABRIgwAAGtcDAAC8w/DA==
Thread-topic: [Xen-devel] sizeof(long) different under windows x64 and linuxx64
User-agent: Microsoft-Entourage/11.3.6.070618
On 23/1/08 02:30, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>> That'll do nicely :)
> 
> Can I get some feedback from the people-who-make-decisions if a patch
> changing all 'unsigned long's in the public .h files to uintptr_t's
> would be accepted? If not, what type should I use?
> 
> Under Windows, I'm already using typedef's to create int8_t, uint8_t,
> etc, so I don't have a problem if the uintptr_t type isn't valid in
> windows natively either.

See my previous mail. Yes, we might, but if we don't there is hardly much
downside for you. In this case, well, I suppose it would make the headers
clearer. The approach for upstream would be to typedef a xen_uintptr_t,
def'ed to unsigned long in old values of XEN_INTERFACE_VERSION and uintptr_t
in the latest XEN_INTERFACE_VERSION.

 -- Keir



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

<Prev in Thread] Current Thread [Next in Thread>