IEEE Interchange floating point and extended floating point for C++

[Jonathan Wakely]

On Fri, 12 Mar 2021, 21:55 Joseph Myers, <joseph@codesourcery.com> wrote:

> On Fri, 12 Mar 2021, Jonathan Wakely via Gcc wrote:
>
> > I see less value in adding additional distinct types that don't add
> > anything you can't already do. _Float16 gives you access to an entirely
> new
> > data type. _Float32 just complicates overloading of it's a new type with
>
> So would you then support _Float128, and the corresponding f128/F128
> literal suffixes, in C++, as a "more standard" version of __float128, in
> the case where it has a different format from long double (e.g. x86_64)
> but not when it has the same format as long double?
>

Or support it in both cases, but for the latter case as an alias for long
double rather than as a distinct type.

I can ask the WG21 Numerics study group what they think makes sense for
C++, because I'm not certain my choices are the right ones.