mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: herbert@13thfloor.at
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] sizeof C types ...
Date: Mon, 25 Aug 2003 12:29:06 -0700	[thread overview]
Message-ID: <20030825122906.79d755d4.rddunlap@osdl.org> (raw)
In-Reply-To: <20030825191339.GA28525@www.13thfloor.at>

On Mon, 25 Aug 2003 21:13:39 +0200 Herbert Pötzl <herbert@13thfloor.at> wrote:

| 
| Hi Everyone!
| 
| this time not sooo off topic but ...
| 
| anyway, ist there some kind of overview how
| large the basic C types are on the different
| architectures Linux runs on?
| 
| char, short, int, long, long int, long long, ...

>From gcc mailing list today: <quote>

All GCC targets (except perhaps some specialized targets for certain DSPs
and microcontrollers) support 64-bit integers.

Almost all GCC targets are either "ILP32" or "LP64".

For ILP32:
	short is 16 bits
	int, long, pointers are 32 bits
	"long long" is 64 bits

For LP64:
	short is 16 bits
	int is 32 bits
	long, pointers, and "long long" are 64 bits

None of this requires a specific version, as all these types have been
around for a long time.
</quote>

Also see Ch. 10 of the LDD book:
  http://www.xml.com/ldd/chapter/book/ch10.html

--
~Randy   [mantra:  Always include kernel version.]
"Everything is relative."

  parent reply	other threads:[~2003-08-25 19:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25 19:13 Herbert Pötzl
2003-08-25 19:27 ` Christoph Hellwig
2003-08-25 19:38   ` Herbert Pötzl
2003-08-25 22:37     ` Erik Andersen
2003-08-25 21:19   ` J.A. Magallon
2003-08-25 22:09     ` Zwane Mwaikambo
2003-08-26  7:30     ` Christoph Hellwig
2003-08-25 19:29 ` Randy.Dunlap [this message]
2003-08-25 19:41   ` Herbert Pötzl
2003-08-25 19:44   ` Christoph Hellwig
2003-08-25 19:56     ` Herbert Pötzl

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=20030825122906.79d755d4.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=herbert@13thfloor.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®