From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Large block device patch, part 1 of 9
Date: 2 Dec 2002 16:03:44 -0800 [thread overview]
Message-ID: <asgsd0$ovi$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209030900410.1997-100000@home.transmeta.com
Followup to: <Pine.LNX.4.44.0209030900410.1997-100000@home.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> I wonder if the right answer isn't to just make things like "__u64" be
> "long long" even on 64-bit architectures (at least those on which it is 64
> bit, of course. I _think_ that's true of all of them). And then just use
> "llu" for it all.
>
> Of course, the really _best_ option would be to have gcc's printf string
> format be extensible and dynamic.
>
> Davem, is sparc64 "long long" 64-bit?
>
Some C libraries have "Ixx" as an extension meaning (u)intXX_t -- it's
used in the same way as the other size modifiers, i.e. %I64x instead
of %lx. This might be a useful extension to mimic.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-12-02 23:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 5:47 Large block device patch, part 1 of 9 Peter Chubb
2002-08-23 7:07 ` Andreas Dilger
2002-08-27 15:23 ` Pavel Machek
2002-08-27 22:58 ` Benjamin LaHaise
2002-08-27 23:40 ` Peter Chubb
2002-09-03 10:01 ` Neil Brown
2002-09-03 16:04 ` Linus Torvalds
2002-09-03 16:21 ` Thunder from the hill
2002-09-03 23:06 ` Neil Brown
2002-12-03 0:03 ` H. Peter Anvin [this message]
2002-09-03 19:42 ` Daniel Phillips
2002-09-03 19:50 ` Benjamin LaHaise
2002-09-03 20:02 ` Daniel Phillips
2002-09-03 20:04 ` Benjamin LaHaise
2002-09-03 20:19 ` Daniel Phillips
2002-09-03 20:25 ` Daniel Phillips
2002-09-03 20:05 ` Thunder from the hill
2002-09-03 20:19 ` Daniel Phillips
2002-12-03 0:05 ` H. Peter Anvin
[not found] <15732.34929.657481.777572@notabene.cse.unsw.edu.au.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0209030900410.1997-100000@home.transmeta.com.suse.lists.linux.kernel>
2002-09-03 16:23 ` Andi Kleen
2002-09-03 8:19 ` Linus Torvalds
2002-09-03 16:43 ` Nikita Danilov
2002-09-03 8:45 ` Linus Torvalds
2002-12-03 0:06 ` H. Peter Anvin
2002-12-05 10:58 ` Pavel Machek
2002-12-05 21:15 ` H. Peter Anvin
[not found] <825516963@toto.iv>
[not found] ` <15734.37217.686498.162782@wombat.chubb.wattle.id.au>
2002-09-05 0:04 ` Benjamin LaHaise
2002-09-05 0:38 ` Daniel Phillips
2002-09-05 1:31 ` Benjamin LaHaise
2002-09-05 4:05 ` Daniel Phillips
[not found] <fa.l4d1mqv.1ghm1h2@ifi.uio.no>
[not found] ` <fa.j8nq6dv.14lihor@ifi.uio.no>
2002-12-03 8:45 ` Giacomo Catenazzi
2002-12-03 17:40 ` H. Peter Anvin
2002-12-03 17:48 ` Giacomo Catenazzi
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='asgsd0$ovi$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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 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.