• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

64-bit

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
I disagree, because extending the general purpose registers to 64 bits also gives some unanticipated benefits.

Example: Stuff two 32-bit integers into the same register and perform the same op. (See also what Intel has been doing with MMX, SSE, but on a grander scale and in the arithmetic unit(s) themselves.)

Scaling MHz-wise is not an issue when architectural improvements are made with each progressive revision. And Newbie's Law No. 3 states:

Larger clock speeds do not necessarily indicate higher performance; and comparisons of clock speeds should ONLY be done when the processors are of the same core design and to be really picky, of the same step code and batch.
 
Its a very interesting topic as more bits does not necessarily equate to better performance either. I dug up a great article someone posted a while back.

"A few final words about performance


Note that I attributed the CS performance increase to x86-64's larger number of registers, and not the increased register width. On applications that do not require the extended dynamic range afforded by larger integers (and this covers the vast majority of applications, including games), the only kind of performance increase that you can expect from a straight 64-bit port is whatever additional performance you get from having more memory available. As I said earlier, 64-bitness, by itself, doesn't really improve performance for anything but the rare 64-bit integer application. In the case of x86-64, it's the added registers and other changes that actually account for better performance on normal apps like games."

http://arstechnica.com/cpu/03q1/x86-64/x86-64-1.html


ps that is a great site for CPU info. Take some time and check it out if you can.
 
Somebody fire him. Seriously.

Sure, not everyone needs 64bit, but lets dupe them into thinking they do so we can reap the benefits. Someone has to push the envelope, and its people like him that slow everyone else down.
 
Unless the application is heavily renaming registers, then there is no support for the extended registers unless the instruction fetch/decode unit is automatically assigning different arguments to different registers. :rolleyes:

Dude, forget this x86 bullcrap. Let's all go RISC. Right now!
 
Example: Stuff two 32-bit integers into the same register and perform the same op.

Has amd added instructions for that? I could feeding the high and low halves of registers to things, but amd doesn't let you address just the high half of a 64-bit register.


I Third that motion!! It's time to move on. Everything else in the PC Industry moves FORWARD with technology....why move laterly with processors?!

Because everyone wants to be able to run their old programs.
 
XWRed1 said:
quotesnip
Has amd added instructions for that? I could feeding the high and low halves of registers to things, but amd doesn't let you address just the high half of a 64-bit register.

quotesnip

Because everyone wants to be able to run their old programs.

I shall check up on the instruction-register thing. Assembly wise, being careful for overflow, I don't think it would be that difficult to do. MMX does it in the 80-bit FPU registers anyway, why not speed it up and move it into the GPRs?

But it's compatibility that has shackled x86 into the hodgepodge mess that it is now.
 
Back