From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: libc-alpha@sourceware.org
Subject: document the fact that "Known Maximum Errors" might not be maximal
Date: Fri, 16 Feb 2024 09:48:07 +0100 [thread overview]
Message-ID: <p9u0a5o03id4.fsf@coriandre.loria.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
Hi,
the attached patch documents the fact that the "Known Maximum Errors" given in
the reference manual might not be maximal.
See thread starting at
https://sourceware.org/pipermail/libc-alpha/2023-December/153279.html.
Paul
[-- Attachment #2: 0001-document-the-fact-that-Known-Maximum-Errors-might-no.patch --]
[-- Type: application/octet-stream, Size: 1042 bytes --]
From f08ba79e35de677decef10982a8ecf5230b8456a Mon Sep 17 00:00:00 2001
From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Date: Fri, 16 Feb 2024 09:41:14 +0100
Subject: [PATCH] document the fact that "Known Maximum Errors" might not be
maximal
---
manual/math.texi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/manual/math.texi b/manual/math.texi
index 2f6ee253b9..3abd83c835 100644
--- a/manual/math.texi
+++ b/manual/math.texi
@@ -1276,7 +1276,9 @@ extensions.
@cindex ulps
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
measure for the relative error. For a number @math{z} with the
representation @math{d.d@dots{}d@mul{}2^e} (we assume IEEE
floating-point numbers with base 2) the ULP is represented by
--
2.34.1
next reply other threads:[~2024-02-16 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 8:48 Paul Zimmermann [this message]
2024-02-16 9:43 ` Vincent Lefevre
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=p9u0a5o03id4.fsf@coriandre.loria.fr \
--to=paul.zimmermann@inria.fr \
--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).