his is incorrect on several accounts. First off, the AMD64 ISA differs in substantial ways from the ia32 ISA. Athlon XP is ia32 compatible, and has no mode that resembles amd64. The Opteron very cleverly retains opcode compatibility with ia32, but is essentially a 64-bit RISC-y chip in its native instruction set. Registers on amd64 are all GP (unlike ia32), and there are a lot more of them, which is very important for code optimization. (Ironically, on modern CPUs, CISC opcodes are easier to optimize on silicon for performance.)
This is incorrect on several significant points.
First of all like it or not, simple Fact, Opteron is heavily based on AMD Athlon XP architecture. Thats not necessarily a bad thing since the Athlon XP is a great chip, but trying to argue otherwise is a bit pointless.
One only has to look at the exhaustive reviews that have been posted EVERYWHERE, to acknowledge that the Opteron is essentially based on an Athlon XP. Its fpu unit has remained completed unchanged as has its integer unit. Most of the internal pathway, the number of instructions it will handle in flight, hell even the internal pathways are pretty much identical. Adding more General purpose registers is correct however essentially to take proper advantage the chip must be in 64 bit mode. Like the G5 there is not 64 bit os currently.
I hope idon't sound condescending but why not head over to arstechnica and read the dissection of the AMD 64 architecture or anandtech etc....
Anyway, basing a processor on an older design and proven design like the athlon means that the athlon 64 is able to take advantage of optimized code. Incidentally there is extremely advanced Athlon optimization available in GCC..... 3d now, extended 3d now, SSE, SSE2 & x86-64 (if athlon 64) etc... before we say anything about the code being optimized for its internal pathways which again it does do. Funnily enough the Athlon does better with the Intel compiler than with the GCC.... but again this compiler does optimize code for it, generates SSE and SSE2 code automatically where possible, and does a great job of unrolling code to prevent branch mis predictions etc...
Simple fact is in 32 bit mode, the Opteron IS as optimized as it will get presently. The very fact that the Athlon has to remain ISA x86 compatible will always be a limiting factor. Also the Opteron can take advantage of years of optimizing for the Athlon arch in compilers.
Regardless the results speak for themselves. The G5 is far more heavily removed from its "predecessor" G4 than the Athlon 64 is from the Athlon XP.
Any in depth review i have seen has said that the G5/970 is so far removed from previous PPC architecture that running older uncompiled legacy software it will only be running at 50% best case scenario of its peak. Even when recompiled with GCC 3.3 most case scenario the chip is only running 50% its potential. A recompile with XLC and XLF definately substantiates this.
Also the G5 was designed to have lots of instructions flying around in flight (ignore apple marketing speak), and to have its units running in parallel. That was the design decission and this pretty much leaves the older PPC design decisions behind. However as arstechnica pointed out in their analysis of the chip, this is brilliant, great for performance , when software and compilers catch up. The present GCC 3.3 does NOT optimize the code properly for the internal pathways etc... How else can you explain a 300% increase in performace when moving to the XLC and XLF compilers...... there has to be something more to it than minimising branch misprediction. Indeed this would certainly point out and highlight arstechnica's theory that initial compilers would only be using 50% efficiency of the chip in best case scenario and that code would have to be compiled with a compatible compiler before the performance of the chip could be unlocked...... I would reckon from my own testing that this is very much the case. In heavy integer and floating point mathematical work i was seeing practically 200% improvement if not more by moving to XLC and XLF compiler. Others in the thread that i linked to have found identical results.
Can you honestly tell me that presently the Athlon 64 is running at only 50% of its potential....no it runs pretty much close to its peak 4.5 GFlops. When all instruction units of 970 are filled (which requires a compatible compiler.... not GCC!) it runs at peak 8GFlops, but presently with most GCC compiled code it only runs peak 4GFlops, again this information has been sourced from ars forums.
I use a dual Opteron 2 Ghz in work thats about nearly 1 month old. We actually compared results with the 970 G5 and were blown away. while merely competitive and neck and neck with GCC compiled code it blew the Opteron away when we re ran with XLF compiled code.
why dont you test for yourself and see if it does anything for you like maybe doubling your results!

. remember this doesn't contain any SIMD autovectoring ...yet!

But as you already mentioned you don't need Altivec for your code etc....
Im too lazy to go look for your post and find the remark about Altivec being of little use for hte majority of code... but i just wanted to say that i completely disagree.
A huge amount of people who buy macs are creative professionals who work with graphics, music, film etc... for these apps Altivec makes a massive difference where used.
If you are working with science based code like BLAST alitvec makes a huge difference again. Unfortunately for Apple they never managed to get an autovectorising compiler out like intel and amd had. but again this is changing. An autovectoring compiler would use Alitvec where ever possible ... so even an app that you wouldn't expect to make use of alitvec at all, might show a slight 3 -5% performance increase.
Kind Regards
i_wolf
P.S. when i have been comparing processors so far i have been comparing in 32 bit mode for both. I do agree that there is some work to be done optimizing for 64 bit mode athlon 64, the same as there would be for 64 bit mode G5. But thats another analysis thread! and presently there is no pure 64 bit os for either, bar linux for x86-64. ..... rumors of a G5 64 bit gentoo have been heard mentioned though
