|
|
#1 | |
|
Is Core Duo 64-Bit?
![]() Hexus.net vaguely claimed that Intel's Core duo may have support for 64-bit processing. The report is poorly written so is difficult to gather much from it, however, several Mac websites have started reporting it, so it is now linked here for interest sake. It appears that even if the Core Duo had hidden 64-bit capabilities, it is not active on shipping models, making the point somewhat moot. It appears the basis of this rumor is that Intel's upcoming Sossaman processor is 64-bit, however, a recent press release specifically notes that Sossaman is a 32-bit processor. Quote:
|
||
|
|
0
|
|
|
#2 |
|
what would be the point of hiding these capabilities?
|
|
|
|
0
|
|
|
#3 | |
|
Quote:
__________________
Mac Pro 2.66 Ghz, 16GB Apple 20" Cinema Display MacBook Air REV B, 1.86 Ghz, 2GB iPods |
||
|
|
0
|
|
|
#4 |
|
Would raise a few questions if true, that's for sure.
|
|
|
|
0
|
|
|
#5 | |
|
Quote:
It wasn't ready so instead of either pushing back the chip to a later release date or releasing a buggy chip they disabled the feature on chip. Or at least that is my guess. *shrugs* PS- Someone might want to edit the title. I'm not a grammar Nazi or anything but "Is Core Duo is 64-Bit?" Sounds like someone hasn't had their 3AM caffeine fix.
__________________
-iPod Video 160GB
-MacBook Pro Core 2 Duo 2.33Ghz/3GB RAM/250GB -Newton 4700 (a.k.a iPaq 4700) -Dell 2405FPW 24" Widescreen |
||
|
|
0
|
|
|
#6 |
|
Intel "hid" the 64-bit EM64T extensions to the Pentium4 for quite some time, mainly because they weren't yet ready for prime-time. It makes sense for them to integrate the capabilities into chips for testing and evaluation purposes prior to "rolling out" the feature officially.
|
|
|
|
0
|
|
|
#7 |
|
Kind of getting a flashback to 1999 when the Intel Celeron 300A and 400A chips were released rathery quickly.
The Celeron 300A and Celeron 400A could be clocked higher than most of the Pentium chips at the time, plus they had a whole heap of other cool little specs on the Processor which Intel didn't count on too many users knowing about. I think the Duo and Solo has been rushed to be released and there will be quite a few nice little surprises found on both processors which Intel hasn't thought that users might find. The 64 Bit thing kind of makes sense because thats the way the industry in heading. Only time will tell
__________________
"There is a world elsewhere" - Coriolanus
|
|
|
|
0
|
|
|
#8 |
|
yes.
http://www.gizmodo.com/gadgets/intel...ers-153822.php http://web.mac.com/schappi/iWeb/Pers...FAEF603F6.html
__________________
MacBook Air • 17" MacBook Pro • iPod Nano • Apple TVCustom Windows 7 Desktop • Surface RT • WP7 experience comes from bad judgment." - Mulla Nasrudin |
|
|
|
0
|
|
|
#9 |
|
Hmm.
Both the iMac and MacBook Pro are physically limited to 2 GB of RAM, so even if the processors support 64-bit addressing, it doesn't make much difference. (64-bit arithmetic isn't very useful in everyday usage.) |
|
|
|
0
|
|
|
#10 | |
|
Quote:
|
||
|
|
0
|
|
|
#11 |
|
wait wait wait wait wait wait... hold the Fu-kuck up, if the new "core" chips are 32 bit processors, wouldn't that technically make them the same speed as the G5? (with the G5 having 64 bit omptimized OS and benchmarking) And thereby making Apple's Claim of the new chips being faster moot?
|
|
|
|
0
|
|
|
#12 | |
|
64-bit are for address space,not arithmetic
Quote:
I agree that for video processing, it may be useful to have 64-bits of address space, but the application must be compiled for 64-bit as well. If you really have that much data to crunch through, you're also going to need a huge amount of processing power. This is where a quad G5 makes sense with 8-16GB of memory and 64-bit processors have a role. |
||
|
|
0
|
|
|
#13 |
|
hmm, interesting
__________________
"any day that involves cat pee is a really bad day" - iBlue |
|
|
|
0
|
|
|
#14 | |
|
Quote:
With the largest modules currently offering only 2GB a piece (available for PMac), this could be a 4GB limit. That still doesn't make a difference, since a 32-bit register can address 4GB of RAM. However, this will change in the future and who's to say it won't happen before these iMacs and MacBooks get retired?
__________________
The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts. -- B. Russell |
||
|
|
0
|
|
|
#15 |
|
Ifthe core duo IS 64-bit, shouldn't that mean it will run XP? (XP-64 supports EFI doesn't it?
|
|
|
|
0
|
|
|
#16 | |
|
Quote:
If you actually check the tech specs of both Core Duo offerings from Apple, they both state a maximum of 2GB in total anyway.
__________________
Macintosh LCIII - PB 1400c - PB G3 'Lombard' - 12" PB G4 - 15" CD MBP - 24" iMac - 13" i5 MBP iPod Photo 60GB - 2G iPod nano - iPhone 3G - iPhone 4 |
||
|
|
0
|
|
|
#17 | |
|
Quote:
32-bit processors can handle up to 4GB of RAM (2^32 B), 64-bit will handle 18*10^9 GB of RAM (2^64 B), if there was a motherboard that could also handle it. Aqua, Quartz, core image, core video, etc. (slight assumption that they have been written for 64-bit processors along with Tiger) really gain from the extra maths capabilities a 64-bit processor has to offer (put the top G4 next to a 1.6GHz G5, and you'll see a difference in Finder). |
||
|
|
0
|
|
|
#18 |
|
Unfortunatly not...
So here's the deal guys. Even though there is little doubt in my mind that the core actually does have the 64-bit and VT extensions, Intel is very good about disabling them in the hardware itself. When they actually package the die, they are able to internally bridge various configuration jumpers (no pencil mods here
) Below is the actual sysctl output for the new Duo CPU on a iMac Duo:machdep.cpu.vendor: GenuineIntel machdep.cpu.brand_string: Genuine Intel(R) CPU 1400 @ 1.83GHz machdep.cpu.model_string: Unknown Intel P6 Family machdep.cpu.family: 6 machdep.cpu.model: 14 machdep.cpu.extmodel: 0 machdep.cpu.extfamily: 0 machdep.cpu.feature_bits: -1075184641 49577 machdep.cpu.extfeature_bits: 1048576 0 machdep.cpu.stepping: 8 machdep.cpu.signature: 1768 machdep.cpu.brand: 0 machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM SSE3 MON VMX EST TM2 TPR machdep.cpu.extfeatures: XD machdep.cpu.logical_per_package: 2 machdep.cpu.cores_per_package: 2 The fact is that Intel could trivially enable these extensions, and they will. They will sell those chips under a different name for way more money though That's awfully clever of them, don't you think? Yeah, it's sad that all that potential is wasted. On bit of hopeful news though, when 64 bit and Virtual Machine support becomes a factor (say when Apple transitions the xServe to x86) there will be little stopping you from slapping in the faster/64bit enabled CPU's as they are not currently soldered to the motherboard.Bakafish |
|
|
|
0
|
|
|
#19 | |
|
Quote:
For example, many operating systems allow reading and writing of files on your harddisk through "memory mapping": A file is mapped to an area of memory, a program can manipulate the data in the file as if it was in memory. Instead of calling operating system functions to read and write data from the file, this is handled by virtual memory. The problem is: On a 32 bit system, the total size of all everything including memory mapped files must be less than 4 GB. There is no way that a ten GB digital video file could be memory mapped. On a 64 bit OS, no problem. Also important: In 64 bit mode, Intel and AMD processors have 16 general purpose register and sixteen floating point/vector registers instead of 8. |
||
|
|
0
|
|
|
#20 | |
|
Quote:
In the Intel world, when they moved from 16-bit to 32-bit it was a big deal, mostly for the change from a segment-offset memory model to a flat 32-bit memory model. Here the ability to get access to > 4gb memory is the big deal, and they've been able to put in some hacks/shortcuts to work around this for several years. Just to illustrate how 64-bit isn't always better, let's imagine doing an add for two 32-bit integers with the same values at the assembly (register) level: 00000000000000000000000000000001 + 00000000000000000000000000000010 versus 64-bit: 0000000000000000000000000000000000000000000000000000000000000001 + 0000000000000000000000000000000000000000000000000000000000000010 For this simple add, the 64-bit int is more work and doesn't yield any benefit. Microsoft learned this lesson with Windows 95. Remember, they started with 16-bit Windows 3.1 and added 32-bit extensions to it. But the fact was that in many cases the 16-bit code was faster (partly due to years of optimization) so key parts of Windows 95's subsystem stayed 16-bit internally and used 32-bit thunking to talk to their 32-bit "other halves".
__________________
Way too much stuff, 15" rMBP, iPhone 5, iPad 3 Last edited by janstett; Feb 12, 2006 at 07:15 PM. |
||
|
|
0
|
|
|
#21 |
|
I should have been more clear.
That output I showed above clearly indicates that 64 bit and all of the new Virtual thread / Virtual machine extensions are disabled on these chips. So this is a non-story from a technical aspect.
|
|
|
|
0
|
|
|
#22 | |
|
Sossaman not 32-bit, so neither is Yonah.
Quote:
http://www.intel.com/pressroom/kits/...4gelsinger.pdf http://www.supermicro.com/newsroom/p...ress020706.cfm I trust the VP in charge of Intel's CPU division, and an official Press Release from a major Intel server motherboard producer a LOT more than a random rumor on Gizmodo, or a blog of unknown origin. If you follow all of the 'proof' links out there, they all lead back to the same Hexus.net source. (Gizmodo and your blog both point to the same Hexus source, so they're not two sources, only one.) (And in all of The Register's info on Sossaman, even they never once mention 64-bit.) I don't even know where Gizmodo got their info, as they say that "Intel openly admits that its Sossaman chips are 64-bit..." but there has been no such admission, and Hexus is their stated source. But Hexus just says "And it transpires that Sossaman supports iAMD64..." With no sourcing of any kind. The Register reports "Sossaman takes Yonah and adds dual-processor support, along with a 36-bit physical address bus to allow the chip to handle up to 64GB of physical memory..." I'm guessing someone saw 'non-32-bit', and '64 GB', and inferred 64-bit, which is wrong. It's a 32-bit chip, which processes data in 32-bit chunks, that happens to have a 36-bit memory address space. (In fact, the original Pentium II Xeon could address 36-bits of memory, so this isn't even new to the P6 line, of which Yonah and Sossaman are a part of.)
__________________
20" Aluminum iMac 7,1 (mid-2007, Santa Rosa,) upgraded to 2.6 GHz Penryn, 6 GB RAM, 1 TB HD, 4 TB total external hard drive |
||
|
|
0
|
|
|
#23 | |
|
Quote:
I'd be interested to see an explanation of why there is a 1GB-per-module limit associated with 32-bit processors -- but my suspicion is that this is really about what is commercially available. I don't ever recall hearing that there is something about the slot that limits the RAM amount. When Apple says that a computer has a "max RAM amount," it really means that this is the most RAM that you can get installed through them. Since they only sell 1GB modules for the Core Duo Macs and each has two slots, the official Apple math is simple -- a max of 2GB. Of course, without the expansion slots, it's all just hot air....
__________________
The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts. -- B. Russell |
||
|
|
0
|
|
|
#24 | |
|
Money.
Quote:
same processor core. However they cripple one so that it can sell at a competitive price while leaving the uncrippled version at full-price. There really isn't much difference between Celeron,P4 and Xeon... howver intel can charge alot more for the xeon's and P4's because the Celerons are lame. So, Intel will sell Core Duo (Yonar) for one price and an identical (or near idential) chip as a Xeon at a much higher price. As a side note, The Sossaman based CPU's would seem an obvious choise for XServes. Anyone want to start a rumor about when the "iServe" will ship?
__________________
Umax Apus 2000 PPC 603e/240; Apple Mac LC475 (no case) 68040/25Mhz; Apple Mac Classic 68000/8Mhz; IBM 8482 - 2.8GHz P4; Compaq N800v P4M 1.7GHz |
||
|
|
0
|
|
|
#25 | |
|
Quote:
As others have already said, this doesn't mean very much for most programs. If your application has no need for more than 4G of RAM or wide registers, 64-bit code can actually run slower than 32-bit code (because memory pointers are larger, meaning apps use more memory and consume more cache.) The reasoon 64-bit chips historically run faster than 32-bit chips is because they usually have higher clock speeds, faster busses, or larger caches. Applying those same factors to a 32-bit chip will speed them up just as much. Taking a CoreDuo and flipping some internal bit to activate 64-bit features will not speed it up. It will have the same size and speed cache. It will have the same bus. It will have the same clocking. This might be useful if you have some application that requires a 64-bit processor (like some Photoshop plugins that can take advantage of huge memory sizes), but that won't mean anything to an iMac owner, since the hardware can't support more than 2G of RAM anyway.
__________________
In theory, theory is the same as practice. In practice, it isn't. |
||
|
|
0
|
![]() |
|
«
Previous Thread
|
Next Thread
»
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| thread | Thread Starter | Forum | Replies | Last Post |
| Is Core Duo going to be ok in the long-run? | jfox8 | Buying Tips and Advice | 3 | Dec 28, 2008 02:35 AM |
| Is There A Big Speed Difference Between The Mac Mini Core Duo and the Core 2 Duo? | NyMetsFan08 | Mac mini | 2 | Sep 26, 2008 06:30 PM |
| is this core duo or core 2 duo? | fromalk | Buying Tips and Advice | 6 | Jan 5, 2008 05:01 PM |
| Intel Core Duo is 64 bit? | thejadedmonkey | Mac Pro | 1 | Feb 12, 2006 12:34 AM |
All times are GMT -5. The time now is 02:15 PM.








MacBook Air • 17" MacBook Pro • iPod Nano • Apple TV


) Below is the actual sysctl output for the new Duo CPU on a iMac Duo:
That's awfully clever of them, don't you think? Yeah, it's sad that all that potential is wasted. On bit of hopeful news though, when 64 bit and Virtual Machine support becomes a factor (say when Apple transitions the xServe to x86) there will be little stopping you from slapping in the faster/64bit enabled CPU's as they are not currently soldered to the motherboard.
Linear Mode

