From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 97A3F3864A32 for ; Tue, 6 Dec 2022 15:03:49 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 97A3F3864A32 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1670339029; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=UWWDZvlJhYY+gPSesGx2D3qHYBMVPigrr3hs3aW8+m8=; b=Gjp93gw9QFrMOJyPUuqMD+SJJJ/vclnc+MHbKMXAFFFkC2PguYLcNWFaIT0a/GUhF/yUYA XML0++7BdfYuquB87vG7DpGOIGw9y71W+Vh4mz66YitZHdGvAT0HWjazExM398HaFdieOr rW/MLZaNcHvjFr2rNQ7rGmf2Ty+doSo= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-287-UbRAKXwCMYyY-02E9ckOzA-1; Tue, 06 Dec 2022 10:03:47 -0500 X-MC-Unique: UbRAKXwCMYyY-02E9ckOzA-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E6C953817969; Tue, 6 Dec 2022 15:03:46 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.195.114]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 98A604A9256; Tue, 6 Dec 2022 15:03:46 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 2B6F3cu5601854 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 6 Dec 2022 16:03:39 +0100 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 2B6F3ZGl601853; Tue, 6 Dec 2022 16:03:35 +0100 Date: Tue, 6 Dec 2022 16:03:35 +0100 From: Jakub Jelinek To: Segher Boessenkool Cc: Michael Meissner , gcc-patches@gcc.gnu.org, "Kewen.Lin" , David Edelsohn , Peter Bergner , Will Schmidt , William Seurer Subject: Re: Patch [0/3] for PR target/107299 (GCC does not build on PowerPC when long double is IEEE 128-bit) Message-ID: Reply-To: Jakub Jelinek References: <20221206145608.GZ25951@gate.crashing.org> MIME-Version: 1.0 In-Reply-To: <20221206145608.GZ25951@gate.crashing.org> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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. Though, the libstdc++ support for the new extended floating point types is mostly enabled only for C++23 (one exception is std::format). Jakub