From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 085853858C55; Sun, 10 Mar 2024 09:41:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 085853858C55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710063705; bh=TMUBRR4n+8h679WrIaXshBoYHR9PIE9ZwB4TnRsKH0E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VG3jXznC3GmmqcOuaHS2r+Bmj7xoWRxF8bMNXFZqMClIQCLK1pUILgOd8jIMDDSZ7 mlXQ4zfsb1H8JNBi2ZLprgAtQ5Yj9rD13mzJuuyXuG804vQ4aV0hC8QWCz9u7Jtzq5 6AzenddfjDVkh98uT4wYNVM8WKlZNUsebfjSFtO8= From: "thenlich at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/93727] Fortran 2018: EX edit descriptor Date: Sun, 10 Mar 2024 09:41:42 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: thenlich at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: jvdelisle 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=3D93727 --- Comment #6 from Thomas Henlich --- (In reply to Jerry DeLisle from comment #5) > I have been studying this a bit by looking at the 2023 std and functional= ity > of printf(). > Specifically printf() provides the 'A' descriptor which can be used for > float (kind=3D4) and double (kind=3D8). It will accept a long double (80= bit > aka kind=3D10). I am noticing that the results of double and long double = are > identical, no extra precision visible. It is very possible I am not doing > that correctly. >=20 > I do not see anything related to quad precision floats. I am posting this > as i think we will have to do some of our own translating byte portions of > floats ourselves. Portability may be an issue. For example IBM 360 128bit > precision or some other processor may not follow the same internal > representations. >=20 > Regardless I have preliminary code for the frontend that results in calli= ng > anew fucntion write_ex in transfer.c >=20 > I think that kind=3D4 and kind=3D8 will be fine. Any thoughts on kind=3D1= 0 or > kind=3D16 I would appreciate as I further explore this. Just some thoughts: Have you tried "%LA" for long double? Have you tried quadmath_snprintf (https://gcc.gnu.org/onlinedocs/libquadmath/quadmath_005fsnprintf.html) with "%QA" for quad precision?=