From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=dRgv=4L=kernel.crashing.org=segher@sourceware.org>
Received: from gate.crashing.org (gate.crashing.org [63.228.1.57])
	by sourceware.org (Postfix) with ESMTP id AA8B63875B40;
	Tue, 13 Dec 2022 14:12:39 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AA8B63875B40
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=kernel.crashing.org
Received: from gate.crashing.org (localhost.localdomain [127.0.0.1])
	by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 2BDEBcn0016035;
	Tue, 13 Dec 2022 08:11:38 -0600
Received: (from segher@localhost)
	by gate.crashing.org (8.14.1/8.14.1/Submit) id 2BDEBc5G016034;
	Tue, 13 Dec 2022 08:11:38 -0600
X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f
Date: Tue, 13 Dec 2022 08:11:37 -0600
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Michael Meissner <meissner@linux.ibm.com>, gcc-patches@gcc.gnu.org,
        "Kewen.Lin" <linkw@linux.ibm.com>, David Edelsohn <dje.gcc@gmail.com>,
        Peter Bergner <bergner@linux.ibm.com>,
        Will Schmidt <will_schmidt@vnet.ibm.com>,
        William Seurer <seurer@gcc.gnu.org>
Subject: Re: Patch [0/3] for PR target/107299 (GCC does not build on PowerPC when long double is IEEE 128-bit)
Message-ID: <20221213141137.GK25951@gate.crashing.org>
References: <Y2HYSM7z8b5jDCZG@toto.the-meissners.org> <20221206145608.GZ25951@gate.crashing.org> <Y49Zx0Y96vKS8P8O@tucnak>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Y49Zx0Y96vKS8P8O@tucnak>
User-Agent: Mutt/1.4.2.3i
X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <gcc-patches.gcc.gnu.org>

On Tue, Dec 06, 2022 at 04:03:35PM +0100, Jakub Jelinek wrote:
> On Tue, Dec 06, 2022 at 08:56:09AM -0600, Segher Boessenkool wrote:
> > > 	In the past, _Float128 was a C extended type,
> > > 	but now it is a part of the C/C++ 2x standards.
> > 
> > Only if you select a new enough -std=, it still is an extended type if
> > not?
> 
> No, as an extension _Float{16,32,64,128}{,x} are available (where the backend
> has support for such IEEE format) even in older C or C++ modes,
> similarly the {f,F}{16,32,64,128} suffixes on literals (with pedwarn
> on everything but C++23).  In C++ it is in all language modes treated as
> distinct type from __float128, and _FloatNN is handled as extended floating
> point type per C++23 rules, while __float128 is not.

Right, so there is no "in the past" here, the actual situation is quite
different.

Reviewing these patches is harder and a lot more work than writing them
can ever have been :-( :-( :-(


Segher