Generally, a 64 bit processor can help you with three things:
- Faster calculations with big numbers
- Accessing more than 4 GB of memory
- Using SIMD instructions on wider registers (128 bits for the PPC970)
(Okay, so this is a bit simplified, but that's the benefits for most people.) A 64 bit processor is not automatically twice as fast as a 32 bit processor.
IMHO, it is actually better for perl to stay 32 bit for a while: perl is known to be a memory hog (as a trade-off for higher speed), and going 64 bit would mean using double the amount of memory for pointers. Which is just not worth the marginal benefits.
My guess is that perl's 64 bit support will be enhanced for those that need it, and will stay an optional switch during compilation for quite some time to come. 64 bit processors like AMD's Opteron or IBM's PPC970 (hopefully to be used in Apples soon :)) can handle 32 bit code just fine.
Update: The PowerPC 970 is made by IBM, of course, not by Intel... thanks, elusion!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.