From: Matthew House <mattlloydhouse@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Morten Welinder <mwelinder@gmail.com>, linux-man@vger.kernel.org
Subject: Re: frexp man page: FLT_RADIX vs. 2
Date: Tue, 2 Jan 2024 22:50:51 -0500 [thread overview]
Message-ID: <20240103035053.212096-1-mattlloydhouse@gmail.com> (raw)
In-Reply-To: <ZZS9LDDna5lnjA_K@debian>
On Tue, Jan 2, 2024 at 8:49 PM Alejandro Colomar <alx@kernel.org> wrote:
> The value of that macro is defined to be 2; it can't have any other
> value.
>
> ISO C defines it in
> <http://port70.net/~nsz/c/c11/n1570.html#5.2.4.2.2p11>.
>
> POSIX defines it in
> <https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/float.h.html>.
>
> Maybe the definition of frexp() by ISO C and POSIX should be changed to
> define it in terms of FLT_RADIX instead of 2.
>
> Have a lovely day,
> Alex
Every version of ISO C says (emphasis mine):
The values given in the following list shall be replaced by constant
expressions with implementation-defined values that are *greater or
equal* in magnitude (absolute value) to those shown, with the same sign:
-- radix of exponent representation, b
FLT_RADIX 2
And POSIX defines it similarly. So FLT_RADIX can be greater than 2 (unless
the implementation defines __STDC_IEC_559__), it just can't be any less.
Indeed, the subsequent EXAMPLE 1 in ISO C sets FLT_RADIX to 16.
Thus, since frexp(3) is defined to return a power of 2, interpreting it as
a power of FLT_RADIX is incorrect in the general case.
Thank you,
Matthew House
next prev parent reply other threads:[~2024-01-03 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 1:29 frexp man page: FLT_RADIX vs. 2 Morten Welinder
2024-01-03 1:49 ` Alejandro Colomar
2024-01-03 3:50 ` Matthew House [this message]
2024-01-03 3:57 ` Alejandro Colomar
2024-01-29 12:29 ` Alejandro Colomar
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=20240103035053.212096-1-mattlloydhouse@gmail.com \
--to=mattlloydhouse@gmail.com \
--cc=alx@kernel.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