Quantcast
You are not logged in, click here to log in.
7 Replies Last post: Jun 15, 2007 3:06 AM by extreme343GS  
Click to view extreme343GS's profile New Member 164 posts since
Dec 6, 2006
Reply

Jun 12, 2007 6:10 AM

Core duo 64 bit??

ok let me get something clear. core duo is a 32-bit processor. core 2 duo & above is 64-bit. but steve jobs said ( from PCmag)


Quote:<hr />
Full 64-bit Functionality Jobs pointed out that, except for the Mac Mini, all Apple products are based on Intel's 64-bit chips. So, Leopard now fully supports 64-bit processing and is backward compatible with all software that is written for 32-bit apps as well.


<hr />



wikipedia:

Quote:<hr />
32-bit processes only. 64-bit processes are not supported. (See the Intel Core 2 successor, which is a 64-bit processor.)

<hr />



so what exactly does he mean?
will my 1gen MB work with leopard?
Reply
Click to view MacosNerd's profile Member 319 posts since
Jun 8, 2007
1. Jun 12, 2007 7:40 AM in response to: extreme343GS
Re: Core duo 64 bit??
Well from the quote you provided OSX is now full 64bit (older versions were not completely 64bit) but even though its 64bit you still can run your older software,i.e., no need to upgrade your apps if you upgrade to leopard.

You're quote did not mention any thing relating to machine compatability but I would assume that apple would not exclude such a large percentage of users by having leopard only run on 64bit intel platforms. I'm sure leopard will run on the PPC and 32bit cputs (core duo and G4s) will work fine

Mike
Click to view drmbb's profile Old Hand 2,353 posts since
Jun 14, 2001
3. Jun 14, 2007 1:06 PM in response to: extreme343GS
Re: Core duo 64 bit??
Leopard will (and does now, as developer beta) run on 32-bit processors. So Apple is not leaving the G4's and G5's and early intel users out of the upgrade loop. Of course, on a 64-bit machine, it will now run fully native 64-bit (that is, instead of just partial 64-bit support - which is a royal PITA with Tiger and things like 64-bit builds of R ).

But there won't be two physically shipped versions - there will be one installer DVD, and the installer app will put the appropriate version in place, with the appropriate support/features, based on what hardware it finds. Just as, to remind you, the Tiger installer currently does.
Click to view MacosNerd's profile Member 319 posts since
Jun 8, 2007
5. Jun 14, 2007 1:29 PM in response to: drmbb
Re: Core duo 64 bit??
Quote:<hr />
So Apple is not leaving the G4's and G5's and early intel users out of the upgrade loop.

<hr />


Actually G5's are 64bit but you're correct Apple isn't about to cut off a large percentage of mac users by making the OS compatible with only the latest set of hardware.
Click to view drmbb's profile Old Hand 2,353 posts since
Jun 14, 2001
6. Jun 14, 2007 2:03 PM
Re: Core duo 64 bit??
It means that Leopard basically exists as two OS's - one 32-bit and one 64-bt. But the installer on the retail DVD will handle the installation of the appropriate version based on the hardware it detects. And on 64-bit machines, it will install duplicate versions of libraries, drivers and such to allow both 64-bit and 32-bit code to run (although only one version of the MACH kernel will be installed - all of this is just like Tiger already is, it's just that Leopard will complete the 64-bit side, while Tiger was not fully transitioned on that part of things). In this sense, Leopard really is merely evolutionary, not revolutionary (as engadget or somebody put it) - Leopard is just completing a transition that Tiger started.

IF - your machine has a 64-bit cpu and architecture, then you will be able to run and compile both 32-bit code and 64-bit code

IF - your machine has a 32-bit cpu and architecture, then you will only be able to run and compile 32-bit code (I'd assume, though do not know, that the version of the developer code that ships with Leopard will install gcc with the appropriate default switches - which of course you can always override anyway).

There will be no performance hit running on a 32-bit machine, as you will be running native 32-bit code.

And note that 64-bit does not automatically mean faster code. There are actually instances where certain types of apps (eg. database search apps) may even run slower in 64-bit then in 32-bit as long as they do not have memory requirements beyond 4GB. The reason being that a 64-bit version of an app loads with inherently greater overhead then the same application compiled in with 32-bit optimization. If the app needs or can make use of memory beyond 4GB, then certainly 64-bit has a great advantage, but it's really mainly in the ability to use more memory that 64-bit really shows an improvement in performance.

So your typical uses of things like web browsers, word processors, and such run no faster in 64-bit then they do in 32-bit. And on a 64-bit machine with 4GB of RAM or less, you may actually want to use a 32-bit optimized application and avoid the unnecessary overhead of loading up a 64-bit version of the same app.