SAOC LLDB D integration: 15th Weekly Update

Luís Ferreira contact at
Wed Jan 5 04:34:31 UTC 2022

On Fri, 2021-12-31 at 17:03 +0000, Iain Buclaw via Digitalmars-d wrote:
> We do support native 128-bit floats in D, unless you meant in the 
> compiler implementation, in which case, all native floats (not 
> just real) are banned throughout the compiler.

Oh ok, didn't know about that. For now, I hardcoded 64, 80 and 128 bit
real type kinds. Later, if we end up finding out that `real` is
intended to direct map to `long double` I may use clang::TargetInfo,
which gives `long double` bit size according to a specified target

> Just have that `real` map to C `long double` and be done with it, 
> even if the hardware may support a bigger float. You don't want 
> to be incompatible with the system you're running on, else you'll 
> be locked out of using the C math library.

Well, I don't think that directly mapping it is correct. e.g. . Is this intended? Anyway, I still
think we should discuss specification wording about how real is
implemented for each target. Maybe worth mention `long double` if
direct mapping is intended? System V ABI is specific about `long
double` size and it is not the largest supported floating point, as I
mentioned above.

Luís Ferreira @

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the Digitalmars-d mailing list