All of lore.kernel.org
 help / color / mirror / Atom feed
From: hmthalib <hmthalib@gmail.com>
To: Rick Brown <rick.brown.3@gmail.com>
Cc: kernelnewbies <kernelnewbies@nl.linux.org>, linux-newbie@vger.kernel.org
Subject: Re: 32 bit processors / 64 bit processors
Date: Sat, 07 Nov 2009 15:50:13 +0530	[thread overview]
Message-ID: <4AF549DD.9020103@gmail.com> (raw)
In-Reply-To: <7783925d0910202002ubcd5328nd8c82bb11e5f84ea@mail.gmail.com>

Rick Brown wrote:
> Hi,
> 
> Firstly, I'm trying to understand what exactly characterizes a
> procesor or an operating system as 32bit / 64 bit. I've read that it
> means the "native word size" of a machine. But what exactly is that?
> Register size? Address bus size? Anything else?

depends on the data bus with.

> Secondly, I'm trying to understand what exactly does a sizeof(int)
> depend on when we say it is "platform specific". Is it dependent of
> compiler being 32bit / 64 bit? Or the OS being 32bit / 64 bit? Or the
> processor being 32 / 64 bit?

the sizeof(int) depends on the limits.h which the complier uses.

> Lastly, How are "sizes" of compiler / OS / processor inter related?
> Here is my understanding. A 32 bit processor can only be running a 32
> bit OS. A 64 bit processor may run a 32 or a 64 bit OS. 

The 64bit processor gives you the option to run in 32 bit mode or 64bit 
mode. there should be register to switch between them. so refer the 
corresponding data sheet for that processor.

A 32 bit
> compiler generates code only to be run on a 32 bit OS; ditto for 64
> bit. Is this right?

yes .

> 
> TIA,
> 
> Rick
> 
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
> 
> 

--
Thalib

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ


  parent reply	other threads:[~2009-11-07 10:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21  3:02 32 bit processors / 64 bit processors Rick Brown
2009-10-21  5:39 ` Siddu
2009-10-21  6:02   ` 益牙
2009-10-21  6:36     ` Ryan Moore
2009-10-21  6:52     ` C
2009-10-23  5:05       ` Rajat Jain
2009-10-23  5:20         ` C
2009-10-23  6:23           ` Rajat Jain
2009-10-23  6:58             ` C
     [not found]               ` <eaf9549291394c8b53f26fba12024a86@virginbroadband.com.au>
     [not found]                 ` <b14bc42a0911060423g324caedw3992061796125ea@mail.gmail.com>
2009-11-07  4:41                   ` vkm
2009-11-07 10:10                   ` hmthalib
2009-11-07 10:30                     ` vkm
2009-11-07 10:49                       ` hmthalib
2009-11-09 18:27                   ` Pulkit Goel
2009-11-10  2:09                     ` Microbit_P43000
2009-10-21  7:43   ` askb
2009-11-07 10:20 ` hmthalib [this message]
2009-11-13  3:37 ` Drew

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=4AF549DD.9020103@gmail.com \
    --to=hmthalib@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=rick.brown.3@gmail.com \
    /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.