All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Morrow <cmorrow@YottaYotta.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: sizeof(long) different under windows x64 and linux x64
Date: Wed, 23 Jan 2008 13:41:20 -0700	[thread overview]
Message-ID: <4797A670.9090604@YottaYotta.com> (raw)
In-Reply-To: <1201045195.2837.37.camel@lute.groveronline.com>

Andy Grover wrote:

> I think it's very hard to be LP64/LLP64-clean without actual testing on
> both.

Printf format statements need to reflect whether the 64 bit type is a 
long or a long long.

uintptr_t foo
printf("%lx", foo) or printf("%llx", foo);

This can be a pain to resolve. /usr/include/inttypes.h has defines that 
are supposed to help with this, but they are ugly to use.

-- 
Chris Morrow	YottaYotta Inc. email: cmorrow@yottayotta.com
phone: (780) 989 6814           web:   http://www.yottayotta.com

  parent reply	other threads:[~2008-01-23 20:41 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
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 [this message]
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=4797A670.9090604@YottaYotta.com \
    --to=cmorrow@yottayotta.com \
    --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.