std.math performance (SSE vs. real)

[David Nadlinger via Digitalmars-d]

On Sunday, 29 June 2014 at 18:17:06 UTC, Russel Winder via 
Digitalmars-d wrote:
> This is getting way off the original thread, but…
>
> The issue is what hardware representations are supported: what 
> does
> float mean? This is a Humpty Dumpty situation and "something 
> must be
> done". Hence Go stops with the undefined words and gives 
> definite global
> meanings to type names. It would be helpful if D eschewed the 
> C/C++
> heritage as well and got more definite about type names.

There is nothing Humpty Dumpty about the current situation. You 
are simply missing the fact that float and double are already 
defined as 32 bit/64 bit IEEE 754 compliant floating point 
numbers in the spec.

There is nothing ambiguous about that, just as char/int/long have 
defined bit-widths in D.

David