public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: libc-alpha@sourceware.org
Subject: Re: document the fact that "Known Maximum Errors" might not be maximal
Date: Fri, 16 Feb 2024 10:43:34 +0100	[thread overview]
Message-ID: <20240216094334.GA3653@qaa.vinc17.org> (raw)
In-Reply-To: <p9u0a5o03id4.fsf@coriandre.loria.fr>

On 2024-02-16 09:48:07 +0100, Paul Zimmermann wrote:
> the attached patch documents the fact that the "Known Maximum Errors"
> given in the reference manual might not be maximal.

 This section lists the known errors of the functions in the math
-library.  Errors are measured in ``units of the last place''.  This is a
+library.  However, for some functions like the Bessel functions,
+larger errors are known, but are documented elsewhere (bugzilla).
+Errors are measured in ``units of the last place''.  This is a

Instead of saying that they are "documented elsewhere", shouldn't the
manual be updated?

BTW, the manual contains

fmaf	-	-	-	-	-
fma	-	-	-	-	-
fmal	-	-	-	-	-
fmaf128	-	-	-	-	-
fma_ldoublef	-	-	-	-	-
fma_ldouble	-	-	-	-	-
fma_ldoublel	-	-	-	-	-
fma_ldoublef128	-	-	-	-	-

However, correct rounding is required for these functions.

And I can't see any reference to f128, ldoublef, etc. in the manual
except in this table.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

  reply	other threads:[~2024-02-16  9:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16  8:48 Paul Zimmermann
2024-02-16  9:43 ` Vincent Lefevre [this message]
2024-02-16 10:02   ` Paul Zimmermann
2024-02-16 10:22     ` Vincent Lefevre
2024-02-16 10:54       ` Paul Zimmermann
2024-02-16 12:39         ` Vincent Lefevre
2024-02-16 17:32           ` Joseph Myers
2024-02-16 17:22   ` Joseph Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240216094334.GA3653@qaa.vinc17.org \
    --to=vincent@vinc17.net \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).