Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Honestly I think most of the people touting on about 64 bit being awesome in this forum have absolutely no idea what it means...
 
It is as 64bit as x64 gets. As is Snow Leopard if you change the boot flag so that it uses the real x64 kernel. The whole point of the AMD64 architecture is that all programs compiled for the regular i386 (x32) Intel architecture run without modification--there is no performance loss or emulation "danger" when running x32 programs on an x64 chip. In fact, I think that all x86 processors--no matter how advanced or altered from the original 80186 architecture they are--still have to spend the first few microseconds after initial power-on in 80186 "Real Mode" (the legacy 16bit mode) before they can switch to the modern standard "Protected/Long Mode."
 
Last edited:
Only two of all my processes are not 64-bits. Dropbox and FlashPlayer safari plugin
 
Bummer.

Thanks for the answer though.

Thats because you do not understand what 64bit really is.

Anyway, did you know that most apps run slower within 64bit (even 64bit compiled apps)? Uses more memory? Have bigger memoryleaks when not properly coded?
The only advantage that 64bit brings is, it can address more memory compared to 32bit. This can be a advantage but also a disadvantage.

Honestly I think most of the people touting on about 64 bit being awesome in this forum have absolutely no idea what it means...

Very true!
As a developer I wish 64bit never did see the light of day. 32bit is much easier to program without issues. Memoryleaks are a pain with 64bit. :-/

It is a hype created by Intel. Period.
 
Last edited by a moderator:
It is a hype created by Intel. Period.

I'm sorry but I have to disagree. A properly written 64 bit app and OS more efficiently use CPU cycles by reducing the number of loads into the various registers in the CPU core to handle large data sets. This means that the CPU can crunch more data every clock cycle. This may not make launching Firefox all that much faster, but crunching on a video transcode is. Or doing physics calculations for a video game. Or rendering an image out of its compressed format for displaying on the screen. (Before you mention MMX/SSE, I must remind you that one is still oft limited by the general purpose registers for a number of operations that MMX/SSE are not suited for)

Any time you are dealing with large pieces of data where repetitive instructions are necessary (basically all of modern computing) you see the benefits of 64 bit. Not to mention PAE is significantly slower than a direct page/memory address for +4gb of memory that 64 bit CPU's and OS's offer.

Like any new way of programming methods and techniques need to be augmented or changed, but in general it provides a not so insignificant performance boost.
 
A properly written 64 bit app and OS more efficiently use CPU cycles by reducing the number of loads into the various registers in the CPU core to handle large data sets. This means that the CPU can crunch more data every clock cycle.

Floating point calculations are about 20% slower in 64bit compared to 32bit.
Most video and audio has floating point calculations. That is why for example Handbrake 64bit is about 10-15% slower then Handbrake 32bit (especially noticeable when converting to H264).
Anyway, as you said, bigger amount of memory can be addressed but this not always makes up for the slower FP lag.
 
Floating point calculations are about 20% slower in 64bit compared to 32bit.
Most video and audio has floating point calculations. That is why for example Handbrake 64bit is about 10-15% slower then Handbrake 32bit (especially noticeable when converting to H264).
Anyway, as you said, bigger amount of memory can be addressed but this not always makes up for the slower FP lag.

When doing floating point you should be using MMX/SSE. FP calculations done by the general execution units are inaccurate and slow as all hell.
 
I'm pretty sure OS X went "true" x64 with 10.6.

I don't know when it went "true" x64, but I do know that the only computers Apple recommends booting into x64 mode are 2011 Macbook Pros, 2011 iMacs and Mac Pros dating a year or a few back.

Other/previous models will, but it's not supported per say.

From what I understand, 10.7 will always boot into 64 bit mode, hence the 64 bit CPU requirement.
 
I don't know when it went "true" x64, but I do know that the only computers Apple recommends booting into x64 mode are 2011 Macbook Pros, 2011 iMacs and Mac Pros dating a year or a few back.

Other/previous models will, but it's not supported per say.

From what I understand, 10.7 will always boot into 64 bit mode, hence the 64 bit CPU requirement.

According to an Apple support article I read yesterday, all iMacs from 2008 are capable so read the facts before you spread FUD.
 
Bummer.

Thanks for the answer though.

What the...? Why is 32-bit support a bummer?

Honestly I think most of the people touting on about 64 bit being awesome in this forum have absolutely no idea what it means...

The MacRumors forum is one of the most misinformed Mac communities I've seen when it comes to technical issues. Half the people don't even know what 64-bit means or that OS X's system frameworks were 64-bit back in 2007. The only thing changing for most users in Lion is that the kernel will be 64-bit, which will make no discernible difference to them anyway, yet for some reason people obsessively fret over whether or not they can boot the 64-bit kernel.

You don't need the 64-bit kernel to run 64-bit applications, so it's bizarre that anyone is even thinking about it. You should only care if you're a driver developer.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.