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

       Hi Vincent,

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

this is one solution I proposed in
https://sourceware.org/pipermail/libc-alpha/2023-December/153279.html,
and Carlos answered:

> (a) There are known defects where ULPs may reach values that are not useful
>     for talking about the library in general.
> 
> (b) There is value in being clear about the worst case known ULPs for an
>     implementation of a given algorithm.
> 
> If a test is marked as XFAIL then it is clearly (a) and listing that worst
> case ULPs in the manual may not be useful.

thus the proposed patch documents the existence of the "XFAIL" entries.

Paul

  reply	other threads:[~2024-02-16 10:02 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
2024-02-16 10:02   ` Paul Zimmermann [this message]
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=p9u04je83ewv.fsf@coriandre.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=libc-alpha@sourceware.org \
    --cc=vincent@vinc17.net \
    /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).