From: Keith Owens <kaos@ocs.com.au>
To: Chad Schwartz <cwslist@main.cornernet.com>
Cc: 64738 <schwung@rumms.uni-mannheim.de>, linux-kernel@vger.kernel.org
Subject: Re: Kernel bits
Date: Tue, 28 Nov 2000 00:31:11 +1100 [thread overview]
Message-ID: <2091.975331871@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 27 Nov 2000 07:36:22 MDT." <Pine.LNX.4.30.0011270734470.20724-100000@main.cornernet.com>
On Mon, 27 Nov 2000 07:36:22 -0600 (CST),
Chad Schwartz <cwslist@main.cornernet.com> wrote:
>int main(void) {
> printf("Size of an unsigned long is %d bytes\n",sizeof(unsigned long));
> return(0);
>}
>
>That simple program will tell you that an unsigned long is 4 bytes, or 8
>bytes.
>
>It is then a safe assumption - that if you get back '8', that you're
>running a 64bit kernel, on a 64bit processor.
No, that only tells you the size of a long under the compiler you used.
If you are on an Intel IA64 (64 bit kernel) but you compile with gcc
for ix86 (32 bit userspace) then sizeof(long) is 4. IA64 runs both
native and ix86 code, sizeof(any userspace field) tells you nothing
about the kernel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-27 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 8:25 Kernel bits 64738
2000-11-27 13:36 ` Chad Schwartz
2000-11-27 13:31 ` Keith Owens [this message]
2000-11-27 14:22 ` Chad Schwartz
2000-11-27 13:53 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2000-11-22 8:25 64738
2000-11-22 9:29 ` Matti Aarnio
2000-11-22 9:46 ` 64738
2000-11-22 10:09 ` Matti Aarnio
2000-11-23 1:15 ` Pavel Machek
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=2091.975331871@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=cwslist@main.cornernet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwung@rumms.uni-mannheim.de \
/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