public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31470] inttypes.h provides incorrect macro definitions
Date: Mon, 11 Mar 2024 15:34:17 +0000	[thread overview]
Message-ID: <bug-31470-131-dWLWU6NZNa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31470-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31470

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2024-03-11
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #5 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
CD2 GB-108 is indeed on my list of accepted NB comments requiring
implementation changes - the macro definitions should be changed, with
associated tests added to the glibc testsuite. The general rule that you can
pass a value of the promoted type (or, in certain cases, a signed/unsigned
variant of that type, when the rules for va_arg allow such variations), not
necessarily arising from promotion of a value of the narrower type, was
introduced for N2562 (previously this area was unclear). CD2 GB-108 simply
makes the macros in inttypes.h follow the same rules required to be followed by
direct use of formats such as %hhd.

When %hh / %h formats are used directly, glibc has done the expected narrowing
since 2006 (bug 2509; glibc 2.5; "(process_arg): Fix reading of signed short
and byte values from parameter list."). It's just the macros that now need
fixing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-03-11 15:34 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 ` [Bug libc/31470] " fweimer at redhat dot com
2024-03-11 13:12 ` 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 [this message]
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-dWLWU6NZNa@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).