From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7E1743858C35; Sun, 7 Apr 2024 05:20:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7E1743858C35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712467250; bh=0UZTlgPve0oN0QWfxJ04l2jQXpF8MaMQi8qYQZd7DbQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lZwpIDBpeZIQEHH56/pajesFbsF9bnjXK0ybLFgBUvhMFp8hvn8gz1oq9jmbyFIR8 03HcFZjwpjmQZfAINsBJ3X3CFP+EjK0dGoXNzBIJJHXk15qKwGKeVMvgCAC2wlLwjg E3h8FG5f+WC2CAwzGUj+l4FXwxB5fGWp7pcFWRxU= From: "g.peterhoff@t-online.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug libquadmath/114623] sqrtq and std::numeric_limits<__float128>::max() Date: Sun, 07 Apr 2024 05:20:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libquadmath X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: g.peterhoff@t-online.de 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=3D114623 --- Comment #4 from g.peterhoff@t-online.de --- That is precisely the design error of C/C++/etc. There should be no float/double/long double/__float128/etc, but *only* floatN_t. Then there wouldn't be these discrepancies (if necessary you have to emulate by SW). But that's just my humble opinion ... and now we have to face reality and m= ake the best of it.=20 One step might be to put std::float128_t and __float128 on a common/uniform code base :-) cu Gero=