public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "newbie-02 at gmx dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/31518] New: documentation: FLT_MAX_10_EXP questionable text, evtl. wrong, Date: Wed, 20 Mar 2024 22:47:40 +0000 [thread overview] Message-ID: <bug-31518-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31518 Bug ID: 31518 Summary: documentation: FLT_MAX_10_EXP questionable text, evtl. wrong, Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: manual Assignee: unassigned at sourceware dot org Reporter: newbie-02 at gmx dot de CC: mtk.manpages at gmail dot com Target Milestone: --- 'FLT_MAX_10_EXP This is the maximum positive integer such that 10 raised to **this power minus 1** can be represented as a normalized floating point number of type float. This is supposed to be at least 37.' in https://www.gnu.org/software/libc/manual/html_node/Floating-Point-Parameters.html . A.) should that read as '10^( FLT_MAX_10_EXP ) - 1' or as '10^( FLT_MAX_10_EXP - 1 )? B.) for DBL_MAX_EXP my system returns 1024, while only 2^1023 fits into a binary64, for DBL_MAX_10_EXP it returns 308, where 1E308 is! possible. C.) for XXX_MAX_10_EXP I see similar definition, but different behavior / relation between description and value returned. I see some consistency problems, confusions between the two, the manual and the values returned. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-20 22:47 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-20 22:47 newbie-02 at gmx dot de [this message] 2024-05-21 8:27 ` [Bug manual/31518] " schwab@linux-m68k.org
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=bug-31518-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).