From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 69549385842D; Mon, 5 Feb 2024 15:08:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 69549385842D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1707145739; bh=FgS1IuqLR2AF/cXOw8rNFPshwWhkdYf3DAxwKkDHaxM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QS8uXzoMF8yXoZDQV3eKPn31mK3IYssBfwJwq4MKDMf6afT6JaZEiAE9Rk+ZtP0XS Gy9C9q3HJqrkBSU++C5Q134ai6vWCFysbXSii77xor21toSywB51RLksCLpn9m0NO7 KU0tsDa4DTE11JwM7NxAG9IWtobxiUTmouZxnqF0= From: "kashi at waseda dot jp" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113770] _Float64x support on g++ 13.2.0 Date: Mon, 05 Feb 2024 15:08:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 13.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kashi at waseda dot jp X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113770 --- Comment #5 from Masahide Kashiwagi --- Thank you very much. I understand that g++ 13 no longer supports _Float64x in a very limited way. Does this mean that if I want to use 80-bit extended floating point numbers= in g++ 13 or later, is it best to use long double? Since long double may not be 80-bit on non-x86 architectures, I wanted to u= se _Float64x or __float80, which are clearly 80-bit, if possible.=