From: dvm9999@gmail.com (dharmvir kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to identity processor architecture
Date: Thu, 27 Jan 2011 12:45:47 +0530 [thread overview]
Message-ID: <AANLkTimYvDayesj9EAbwq28A=njfsUzatErQsskoyzr5@mail.gmail.com> (raw)
In-Reply-To: <DD57B7CE-5EDF-46A1-B135-74A75F7932F7@cs.ucsd.edu>
64-bit processors have lm ("long mode") in the flags section of
cpuinfowhereas 32-bit processors have not.
regards
Dharmvir Kumar
On Thu, Jan 27, 2011 at 12:24 PM, Enrico Granata <egranata@ucsd.edu> wrote:
> On Jan 26, 2011, at 10:45 PM, Mulyadi Santosa wrote:
>
> On Thu, Jan 27, 2011 at 13:40, prabhu <prabhum@msys-tech.com> wrote:
>
> No, because 32bit code will tell the datatype size and i think pointer
>
> variable depends on architecture.
>
> So 64 bit processor needs 64 address line to point the data location. So
>
> pointer variable needs to be 8 byte.
>
>
> Please don't top post and please use the new list address, ok? :)
>
> IMO, I second your opinion. And as addition, I think it's worth to
> check /proc/cpuinfo too in "address sizes" field
>
> NB: I was thinking, if in x64, it is operating in full 32 bit mode
> (not hybrid one), it is supposed to yield 32 bit address too, right?
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
> I guess a 64bit processor does need 64bit addresses to reference memory.
> But at the same time, if 32 bit programs are to run unmodified on 64 bit
> architectures there needs to be ways in which 32bit pointers can still work.
> So, I am almost 100% sure that compiling 32bit code, even on a 64bit
> processor, should yield 4 for sizeof(void*)
>
> *Enrico Granata*
> *Computer Science & Engineering Department (EBU3B) - **Room 3240*
> *office phone 858 534 9914*
> *University of California, San Diego*
> *
> *
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110127/e349ee2a/attachment-0001.html
next prev parent reply other threads:[~2011-01-27 7:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 6:07 How to identity processor architecture prabhu
2011-01-27 6:26 ` Enrico Granata
2011-01-27 6:31 ` arun kumar
2011-01-27 6:40 ` prabhu
2011-01-27 6:45 ` Mulyadi Santosa
2011-01-27 6:54 ` Enrico Granata
2011-01-27 7:15 ` dharmvir kumar [this message]
2011-01-27 7:24 ` Mandeep Sandhu
2011-01-27 8:20 ` prabhu
2011-01-27 8:22 ` Enrico Granata
2011-01-27 9:53 ` prabhu
2011-01-27 11:15 ` Henry Gebhardt
2011-01-27 11:32 ` Thirugnanam Balamurugan
2011-01-27 11:44 ` Pravin Shedage
2011-01-27 12:33 ` prabhu
2011-01-27 9:23 ` Busybox for powerpc doesnt compile Giriprasad Deviprasad
2011-01-27 10:11 ` yy Hong
2011-01-27 13:47 ` Anuz Pratap Singh Tomar
2011-01-29 5:50 ` Giriprasad Deviprasad
2011-01-30 13:23 ` Giriprasad Deviprasad
2011-01-27 7:07 ` How to identity processor architecture prabhu
2011-01-27 7:13 ` Mulyadi Santosa
2011-01-27 19:27 ` mindentropy
2011-01-27 20:01 ` Denis Kirjanov
-- strict thread matches above, loose matches on Subject: below --
2011-01-27 3:28 Added about new kernel on old distro (was Re: most likely, i'll be giving a kernel talk at ottawa LUG next week) Mulyadi Santosa
2011-01-27 6:09 ` How to identity processor architecture prabhu
2011-01-26 18:08 most likely, i'll be giving a kernel talk at ottawa LUG next week Robert P. J. Day
2011-01-27 6:17 ` How to identity processor architecture prabhu
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='AANLkTimYvDayesj9EAbwq28A=njfsUzatErQsskoyzr5@mail.gmail.com' \
--to=dvm9999@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.