From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: printk and long long
Date: Wed, 11 Feb 2004 23:53:57 +0000 (UTC) [thread overview]
Message-ID: <c0efal$qfp$1@terminus.zytor.com> (raw)
In-Reply-To: yw1xn07pw6sy.fsf@kth.se
Followup to: <yw1xn07pw6sy.fsf@kth.se>
By author: mru@kth.se (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=)
In newsgroup: linux.dev.kernel
>
> Andreas Schwab <schwab@suse.de> writes:
>
> > mru@kth.se (Måns Rullgård) writes:
> >
> >> What is the proper way to deal with printing an int64_t when int64_t
> >> can be either long or long long depending on machine?
> >
> > PRId64 from <inttypes.h> (replace d with the desired format character).
> > This is for user space, not sure whether that is acceptable for kernel
> > code (<intttypes.h> is not one of the required headers for freestanding
> > implementations).
>
> That should work for userspace. What standard specifies those?
> What about kernel sources?
>
C99 defines those.
Another (frequently easier) way is to cast to (intmax_t) and use the %j size modifier:
printf("foo = %jd\n", (intmax_t)foo);
-hpa
--
PGP public key available - finger hpa@zytor.com
Key fingerprint: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74
"The earth is but one country, and mankind its citizens." -- Bahá'u'lláh
Just Say No to Morden * The Shadows were defeated -- Babylon 5 is renewed!!
next prev parent reply other threads:[~2004-02-11 23:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 12:49 printk and long long sting sting
2004-02-11 13:35 ` wdebruij
2004-02-11 13:48 ` Maciej Zenczykowski
2004-02-11 14:04 ` vda
2004-02-11 15:58 ` Maciej Zenczykowski
2004-02-11 19:41 ` H. Peter Anvin
2004-02-11 20:32 ` Måns Rullgård
2004-02-11 21:46 ` Chris Friesen
2004-02-11 22:38 ` Timothy Miller
2004-02-11 22:23 ` Andreas Schwab
2004-02-11 23:11 ` Måns Rullgård
2004-02-11 23:53 ` H. Peter Anvin [this message]
2004-02-11 16:59 ` Dick Streefland
2004-02-11 14:03 ` Måns Rullgård
2004-02-11 14:15 ` wdebruij
2004-02-11 15:23 ` Richard B. Johnson
2004-02-13 0:26 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2004-02-11 13:54 Bart Hartgers
2004-02-11 14:04 ` YOSHIFUJI Hideaki / 吉藤英明
2004-02-11 14:13 ` Andreas Schwab
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='c0efal$qfp$1@terminus.zytor.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.