From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Collin Funk <collin.funk1@gmail.com>
Subject: Re: limits-h: Fix BOOL_MAX value
Date: Mon, 12 Feb 2024 17:25:25 +0100 [thread overview]
Message-ID: <4252097.PYKUYFuaPT@nimes> (raw)
In-Reply-To: <f558964d-b1c8-4f5b-8d8a-0ff1d1980e7f@gmail.com>
Collin Funk wrote:
> Both ISO C 23 § 5.2.4.2.1 and
> Annex E seem to say BOOL_WIDTH must be exactly 1.
I have no idea what the footnote "This value is exact." in § 5.2.4.2.1 means.
And Annex E is informational, not normative.
Therefore, I think, the grounds for claiming a clang bug are weak.
Bruno
prev parent reply other threads:[~2024-02-12 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 13:09 limits-h: Fix BOOL_MAX value Bruno Haible
2024-02-12 14:48 ` Collin Funk
2024-02-12 16:25 ` Bruno Haible [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4252097.PYKUYFuaPT@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=collin.funk1@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).