From: askb <askb23@gmail.com>
To: Siddu <siddu.sjce@gmail.com>
Cc: Rick Brown <rick.brown.3@gmail.com>,
kernelnewbies <kernelnewbies@nl.linux.org>,
linux-newbie@vger.kernel.org
Subject: Re: 32 bit processors / 64 bit processors
Date: Wed, 21 Oct 2009 13:13:03 +0530 [thread overview]
Message-ID: <1256110983.408.19.camel@linux-k65f.site> (raw)
In-Reply-To: <9b0a5b990910202239u7423e88du4786700f79a4bda9@mail.gmail.com>
On Wed, 2009-10-21 at 11:09 +0530, Siddu wrote:
>
>
> On Wed, Oct 21, 2009 at 8:32 AM, Rick Brown <rick.brown.3@gmail.com>
> 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?
>
>
> When they say its 32/64 bit machine its the capability of the system
> or processor to process so many bits at once !
Additionally, the virtual memory address is 64 bit. Also the main
difference is with sizeof(long int) and sizeof(void *) on both archs.
>
>
>
> 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?
>
> its dependent on processor being 32/64 bit
>
>
> 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.
>
> No ... 32 bit OS can run anything <= 32 bit
>
> A 64 bit processor may run a 32 or a 64 bit OS.
>
> yes thats right !
>
>
> A 32 bit
> compiler genrates code only to be run on a 32 bit OS; ditto
> for 64
> bit.
>
> Not sure about this let others have their say !
>
> Is this right?
It is possible to use the -m32 and -m64 flags with gcc for generating
32/64 bit compatible code.
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2009-10-21 7:43 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 [this message]
2009-11-07 10:20 ` hmthalib
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=1256110983.408.19.camel@linux-k65f.site \
--to=askb23@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rick.brown.3@gmail.com \
--cc=siddu.sjce@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.