All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: "Måns Rullgård" <mru@kth.se>, linux-kernel@vger.kernel.org
Subject: Re: printk and long long
Date: Wed, 11 Feb 2004 17:38:04 -0500	[thread overview]
Message-ID: <402AAECC.1010606@techsource.com> (raw)
In-Reply-To: <402AA2CE.2060104@nortelnetworks.com>



Chris Friesen wrote:
> Måns Rullgård wrote:
> 
>> 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?
> 
> 
> Print it as long long, and even if there is an arch where that is 128 
> bits it'll still work.


In that case you'll want to cast it to (long long) before you pass it so 
as to be sure that "%lld" and the parameter are the same size.  Right?


  reply	other threads:[~2004-02-11 22:33 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 [this message]
2004-02-11 22:23             ` Andreas Schwab
2004-02-11 23:11               ` Måns Rullgård
2004-02-11 23:53                 ` H. Peter Anvin
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=402AAECC.1010606@techsource.com \
    --to=miller@techsource.com \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    /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.