linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Reuben D. Budiardja" <techlist@pathfinder.phys.utk.edu>
To: linux-c-programming@vger.kernel.org
Subject: Disadvantage of using long long int
Date: Wed, 22 Feb 2006 12:35:42 -0500	[thread overview]
Message-ID: <200602221235.43058.techlist@pathfinder.phys.utk.edu> (raw)


Hello,
In terms of performance and raw speed, is there any disadvantage of using 
"long long int" instead of "long int", "long double" instead of "double" on 
32-bit machine ? Are there any other disadvantage that I should consider?

Thank you.
RDB
-- 
Reuben D. Budiardja
Dept. Physics and Astronomy
University of Tennessee, Knoxville, TN

             reply	other threads:[~2006-02-22 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 17:35 Reuben D. Budiardja [this message]
2006-02-22 17:46 ` Disadvantage of using long long int Glynn Clements
2006-02-22 17:54 ` Steve Graegert
2006-02-22 18:55   ` Glynn Clements
2006-02-22 19:09     ` Steve Graegert

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=200602221235.43058.techlist@pathfinder.phys.utk.edu \
    --to=techlist@pathfinder.phys.utk.edu \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).