From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5D6013857733; Tue, 16 May 2023 18:47:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5D6013857733 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684262865; bh=Elk+i5t9S7+TLNhKQE/Z1oAtIKom7nlN4w+CL3+4xIs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=O5dNHpYxEDVVfMciK1zIAOMg+W0M5B4LwA+Qd0NwKxZfM2v1FVp/oCU+sLeJkx0PC /ACSKdgSpt+SUxfk3ayooKSJ/uRyzQnouuMUs3U618ZBRVyMW2NeafKJYjOuLFSQzS qvdMWKtoEwq6uDw9CUUmLqyJ4CMDJ+++co5s6H8Q= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/43622] Incomplete C++ library support for __float128 Date: Tue, 16 May 2023 18:47:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: bkoz at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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=3D43622 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #29 from Jonathan Wakely --- (In reply to Marc Glisse from comment #22) > __float128 is still missing a specialization of numeric_limits. We're still missing that, but I created PR libstdc++/104772 for it. I don't think we need full and I/O support for __float128, so let's close t= his one.=