std.math performance (SSE vs. real)

Walter Bright via Digitalmars-d digitalmars-d at puremagic.com
Sun Jun 29 12:19:57 PDT 2014


On 6/29/2014 12:02 PM, David Nadlinger wrote:
> 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.

Exactly. C/C++ has implementation-defined types, but D types are nailed down.



More information about the Digitalmars-d mailing list