From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Daniel Stodden <dns@somacoma.net>
Subject: Re: sizeof(long) different under windows x64 and linuxx64
Date: Wed, 23 Jan 2008 01:01:08 +0000 [thread overview]
Message-ID: <20080123010108.GC6741@implementation> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0131A8B2@trantor>
James Harper, le Wed 23 Jan 2008 11:55:50 +1100, a écrit :
> > >
> > > Any suggestions as to what the type should be called?
> >
> > Just the standard name: uintptr_t
> >
>
> Can you qualify 'standard' in that context (eg Linux, gcc, POSIX, etc).
C99
> I don't ever remember hearing of that field before. Is it a type defined
> as 'an integer with the same width as a pointer'?
« The following type designates an unsigned integer type with the property
that any valid pointer to void can be converted to this type, then
converted back to pointer to void, and the result will compare equal to
the original pointer: uintptr_t »
Samuel
next prev parent reply other threads:[~2008-01-23 1:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 23:01 sizeof(long) different under windows x64 and linux x64 James Harper
2008-01-22 23:26 ` Daniel Stodden
2008-01-22 23:34 ` sizeof(long) different under windows x64 and linuxx64 James Harper
2008-01-22 23:41 ` James Harper
2008-01-23 0:01 ` Daniel Stodden
2008-01-23 0:47 ` Samuel Thibault
2008-01-23 0:55 ` James Harper
2008-01-23 1:01 ` Samuel Thibault [this message]
2008-01-23 1:38 ` James Harper
2008-01-23 2:30 ` James Harper
2008-01-23 8:04 ` Keir Fraser
2008-01-23 14:25 ` John Levon
2008-01-23 14:33 ` Keir Fraser
2008-01-23 14:45 ` Christoph Egger
2008-01-23 8:48 ` Christoph Egger
2008-01-22 23:39 ` sizeof(long) different under windows x64 and linux x64 Andy Grover
2008-01-23 8:00 ` Keir Fraser
2008-01-23 20:41 ` Chris Morrow
2008-01-23 21:18 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080123010108.GC6741@implementation \
--to=samuel.thibault@eu.citrix.com \
--cc=dns@somacoma.net \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.