From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 150E83955405; Tue, 18 May 2021 13:43:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 150E83955405 From: "ppalka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvMTAwMzYxXSBnY2MtMTEgZm9yIG1zcDQz?= =?UTF-8?B?MC1lbGYgZmFpbHMgdG8gYnVpbGQ6IHNyYy9jKysxNy9mbG9hdGluZ190b19j?= =?UTF-8?B?aGFycy5jYzoxMDc6IGQyZml4ZWRfZnVsbF90YWJsZS5oOjEyODM6MjM6IGVy?= =?UTF-8?B?cm9yOiBzaXplIG9mIGFycmF5IOKAmFBPVzEwX1NQTElUXzLigJkgZXhjZWVk?= =?UTF-8?B?cyBtYXhpbXVtIG9iamVjdCBzaXplIOKAmDMyNzY34oCZ?= Date: Tue, 18 May 2021 13:43:05 +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: 11.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: ppalka at gcc dot gnu.org X-Bugzilla-Status: NEW 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 May 2021 13:43:06 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D100361 --- Comment #3 from Patrick Palka --- (In reply to Jonathan Wakely from comment #2) > Patrick, is the table an optimization, or essential? We might be able to > avoid it, but he functions would be much slower. The tables are essential for Ryu's d2exp_buffered_n and d2fixed_buffered_n routines, which we use for fast explicit-precision formatting of float/doub= le. >=20 > Maybe we should just disable the floating-point to_chars for 16-bit targe= ts. Agreed.. though in theory we could just go through printf as a fallback for d2exp_buffered_n and d2fixed_buffered_n on these targets. Btw, we already disable the floating-point to_chars on targets without a binary64 double. So is our test for detecting binary64 not accurate enough= , or are these 16-bit targets whose double type really is binary64?=