public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Morten Welinder <mwelinder@gmail.com>
Cc: Joseph Myers <josmyers@redhat.com>,
	linux-man@vger.kernel.org,  libc-help@sourceware.org
Subject: Re: floor/ceil man pages
Date: Wed, 11 Feb 2026 00:38:07 +0100	[thread overview]
Message-ID: <aYvBRnDPb3e6RZSD@devuan> (raw)
In-Reply-To: <CANv4PNm4HCsNK6+pprzxw2Db_s8JEfpxn2kzZ+BsWA3K8-G9wA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

Hi Morten, Joseph,

On 2026-01-29T13:08:43-0500, Morten Welinder wrote:
> For NaN, it comes down to the ieee spec.  Ieee-754-2008 in Section 6.3
> specifies that the only operations delivering a defined sign for NaNs
> are: copy, abs, negate, and copysign.  "For all other operations, this
> standard does not specify the sign bit of a NaN result, even when
> there is only one input NaN, or when the NaN is produced from an
> invalid operation."
> 
> The glibc people have in the past defended the freedom to return
> whatever sign on NaN they feel like.  See
> https://sourceware.org/bugzilla/show_bug.cgi?id=31104 for an example
> where float/double/long double versions of various functions disagree
> on what sign to return for NaN.
> 
> I don't think the man page should promise more than some standard
> requires unless the implementation is specifically offering further
> guarantees.

Agree.  Would you want to send a patch?


Have a lovely night!
Alex

> 
> M.

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-02-10 23:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 14:51 floor/ceil man pages Morten Welinder
2026-01-29 15:37 ` Alejandro Colomar
2026-01-29 16:27   ` Joseph Myers
2026-01-29 18:08     ` Morten Welinder
2026-02-10 23:38       ` Alejandro Colomar [this message]

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=aYvBRnDPb3e6RZSD@devuan \
    --to=alx@kernel.org \
    --cc=josmyers@redhat.com \
    --cc=libc-help@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mwelinder@gmail.com \
    /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