From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: u64 vs %llu format
Date: Wed, 11 Feb 2004 19:26:20 +0000 [thread overview]
Message-ID: <20040211192620.GE10901@cup.hp.com> (raw)
In-Reply-To: <20040211181730.GC10901@cup.hp.com>
On Wed, Feb 11, 2004 at 10:47:42AM -0800, David Mosberger wrote:
> >>>>> On Wed, 11 Feb 2004 10:17:30 -0800, Grant Grundler <iod00d@hp.com> said:
>
> Grant> Why is __u64 defined as "unsigned long" and not "unsigned long long"?
>
> Because that's the way it is for pretty much every other 64-bit
> UNIX-like platform. 64-bit UNIX/Linux platforms existed long before
> "long long" was widely supported.
ok. I initially read this as "64-bit unix source compat is more important
than ILP32-linux compat". But that's not a fair statement since it implies
alot more than this silly %llu vs u64 issue.
> Grant> will generate this warning:
> Grant> <file>:<line>: warning: long long unsigned int format, __u64 arg (arg 2)
>
> Just cast "i" to (unsigned long long) and the code will be fine.
Yes, or use "unsigned long long" instead of u64 in the first place.
I'll try to convince the code owner to only use "u64" for stuff
representing HW or other "shared" data structures. The distinction
is artificial since both are the same size on LP64 platforms.
But it would reduce the number of warnings we need to fix.
thanks,
grant
prev parent reply other threads:[~2004-02-11 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 18:17 u64 vs %llu format Grant Grundler
2004-02-11 18:47 ` David Mosberger
2004-02-11 19:26 ` Grant Grundler [this message]
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=20040211192620.GE10901@cup.hp.com \
--to=iod00d@hp.com \
--cc=linux-ia64@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox