SAOC LLDB D integration: 15th Weekly Update

Iain Buclaw ibuclaw at
Wed Jan 5 21:52:07 UTC 2022

On Wednesday, 5 January 2022 at 04:34:31 UTC, Luís Ferreira wrote:
> 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 triple.

This is always the case with gdc, so that would be highly 

>> 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?

Looks like ldc is in the wrong there, real.sizeof should always 
be 113 on RISC-V.

More information about the Digitalmars-d mailing list