std.math performance (SSE vs. real)

[Walter Bright via Digitalmars-d]

On 6/28/2014 3:33 AM, Russel Winder via Digitalmars-d wrote:
> By being focused on Intel chips, D has failed to get floating point
> correct in avery analogous way to C failing to get floating point types
> right by focusing on PDP.

Sorry, I do not follow the reasoning here.

> Yes using 80-bit on Intel is good, but no-one
> else has this. Floating point sizes should be 32-, 64-, 128-, 256-bit,
> etc. D needs to be able to handle this. So does C, C++, Java, etc. Go
> will be able to handle it when it is ported to appropriate hardware as
> they use float32, float64, etc. as their types. None of this float,
> double, long double, double double rubbish.
>
> So D should perhaps make a breaking change and have types int32, int64,
> float32, float64, float80, and get away from the vagaries of bizarre
> type relationships with hardware?

D's spec says that the 'real' type is the max size supported by the FP hardware. 
How is this wrong?