Hi!
On Wed, Oct 07, 2020 at 08:00:49PM -0400, Michael Meissner wrote:
> I looked into this a bit, and I think we want to keep the current behavior (as
> modified by the patches). As Joseph says, the _Float types have their own
> types, but may/may not use the same modes as other types. Obviously
On Tue, Sep 29, 2020 at 05:34:55PM +0100, Jonathan Wakely wrote:
> On Mon, 28 Sep 2020 at 23:15, Joseph Myers wrote:
> >
> > On Mon, 28 Sep 2020, Michael Meissner via Gcc wrote:
> >
> > > > I'm not sure which patch in the series is supposed to be implementing
> > > > that, but C requires that long
On Tue, 29 Sep 2020, Jonathan Wakely via Gcc wrote:
> I imagine C++ will want to support _Float128 at some point, with
> similar semantics to C.
Unless it chooses a class-based approach like that used for
std::decimal::decimal128.
--
Joseph S. Myers
jos...@codesourcery.com
On Mon, 28 Sep 2020 at 23:15, Joseph Myers wrote:
>
> On Mon, 28 Sep 2020, Michael Meissner via Gcc wrote:
>
> > > I'm not sure which patch in the series is supposed to be implementing
> > > that, but C requires that long double and _Float128 are distinct types (so
> > > you can use _Generic to ch
On Mon, 28 Sep 2020, Michael Meissner via Gcc wrote:
> > I'm not sure which patch in the series is supposed to be implementing
> > that, but C requires that long double and _Float128 are distinct types (so
> > you can use _Generic to choose between them, for example) even if they
> > have the s
On Mon, Sep 28, 2020 at 05:07:55PM -0400, Michael Meissner wrote:
> On Mon, Sep 28, 2020 at 04:38:51PM +, Joseph Myers wrote:
> > On Thu, 24 Sep 2020, Michael Meissner wrote:
> >
> > > As per the discussion in this thread, I did decide to keep things to two
> > > types
> > > within the compil
On Mon, Sep 28, 2020 at 04:38:51PM +, Joseph Myers wrote:
> On Thu, 24 Sep 2020, Michael Meissner wrote:
>
> > As per the discussion in this thread, I did decide to keep things to two
> > types
> > within the compiler. This means that an explicit __float128 or _Float128
> > will
> > use the
On Thu, 24 Sep 2020, Michael Meissner wrote:
> As per the discussion in this thread, I did decide to keep things to two types
> within the compiler. This means that an explicit __float128 or _Float128 will
> use the same type node and TFmode as long double uses if the default for long
> double is
