very nice shearing with you.
let me know your Facebook ID.
Unfourtunatly most of the benchmarks used are microbenchmarks usually not relevant for desktop systems.
Execpt for the encoding tests, but even though thats client-workload, is usually not something frequently done.
would it be possible to have 2 32bit operations done in parallel in one 64bit operation? would it be a software or hardware implementation?
Can anyone explain what these fingerprints are?
What makes x86_64 code usually faster is the higher amount of registers and to a limited degree the availability of 64-bit operations without using special registers.
Pointers beeing 64-bit large is never a performance win ;)
and you have some sources for that claim? because I read it here first....
and please - whoever mentioned x32 - forget it. As fast as you can. It was created by Intel to make Atom suck a bit less. Breaking all and everything just to make a crap CPU look better is NOT a good thing to do.
Regular Phoronix readers will certainly know what CPU flag designates 64 bit. You may mention it anyway.
It is "lm" in the flags (less -p lm /proc/cpuinfo).
Btw, the late Pentium 4s had 64 bit back then. Looong ago.
64-bit addressing can map all the memory in a sane way. With 32-bit addressing you have to use different indirections to map all the memory (especially with PAE) so it take CPU time to calculate this.
Processors are natively 64-bit, so they must handle 64-bit address natively too. There is no reason that 64-bit address are slower to access. I even would say the contrary...