From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 10 Jul 2025 16:44:48 +0000 (-0700)
Subject: ftoastr: suggest a better algorithm
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d62a0e4ccfae71ac9fb1bbff80252e4259836d3a;p=thirdparty%2Fgnulib.git

ftoastr: suggest a better algorithm

* lib/ftoastr.c: In comment, suggest Ryū instead of Errol.
---

diff --git a/lib/ftoastr.c b/lib/ftoastr.c
index 250b840365..1cef8bb6c7 100644
--- a/lib/ftoastr.c
+++ b/lib/ftoastr.c
@@ -114,10 +114,8 @@ FTOASTR (char *buf, size_t bufsize, int flags, int width, FLOAT x)
   /* The following method is simple but slow.
      For ideas about speeding things up, please see:
 
-     Andrysco M, Jhala R, Lerner S. Printing floating-point numbers:
-     a faster, always correct method. ACM SIGPLAN notices - POPL '16.
-     2016;51(1):555-67 <https://doi.org/10.1145/2914770.2837654>; draft at
-     <https://cseweb.ucsd.edu/~lerner/papers/fp-printing-popl16.pdf>.  */
+     Adams U. Ryū: fast float-to-string conversion.
+     PLDI 2018. 270–282. <https://doi.org/10.1145/3192366.3192369>.  */
 
   PROMOTED_FLOAT promoted_x = x;
   char format[sizeof "%-+ 0*.*Lg"];