public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31470] inttypes.h provides incorrect macro definitions
Date: Mon, 11 Mar 2024 12:43:55 +0000 [thread overview]
Message-ID: <bug-31470-131-AgnmihNRN7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31470-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31470
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com,
| |jsm28 at gcc dot gnu.org
--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
Interesting.
Joseph, should we change most of the <inttypes.h> macro definitions
accordingly? I don't have access to C23, but the wording in C11 suggest to me
that the example violates the precondition set in 7.8.1p1. It's hard to
interpret though due to default argument promotions, though.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-11 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 1:05 [Bug libc/31470] New: " luigighiron at gmail dot com
2024-03-11 12:43 ` fweimer at redhat dot com [this message]
2024-03-11 13:12 ` [Bug libc/31470] " schwab@linux-m68k.org
2024-03-11 14:44 ` luigighiron at gmail dot com
2024-03-11 15:25 ` schwab@linux-m68k.org
2024-03-11 15:34 ` jsm28 at gcc dot gnu.org
2024-03-11 15:36 ` jsm28 at gcc dot gnu.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-31470-131-AgnmihNRN7@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: 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).