Another relevant benchmark is x32 vs. x86. In a memory constrained environment you may be forced to use x86. x32 gives you the ability to get the performance benefits of x86-64 (possibly plus some) while staying in your memory constraints.
Re:X32 ABI
by frozenport on Wednesday October 09, 2013 @10:28PM
(#6525333)
30% performance boost in Java, which we know is lies built on pointers. Also maybe Scala.
This is not true. Since this optimization helps Java so much, it is already implemented in HotSpot itself without changing ABI.
https://wiki.openjdk.java.net/display/HotSpot/CompressedOops
Re:X32 ABI
by frozenport on Thursday October 10, 2013 @02:34AM
(#6526027)
Does this break vectorization? Specifically, saxpy (Y=M*X+B) requires extra operations to dereference every element and won't let you insert an FMA instruction.
Wikipedia notes that "On average x32 is 5–8% faster on the SPEC CPU integer benchmarks compared to x86-64 but it can as likely be much slower. There is no speed advantage over x86-64 in the SPEC CPU floating point benchmarks."
Perhaps the reason that no tier-one Linux distro ships with x32 images is that the additional complexity of supporting an additional ABI is not seen to be worth the modest performance increases.
[1]: http://www.spec.org/cpu2000/CINT2000/181.mcf/docs/181.mcf.ht...