public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eblake at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/30371] C2x strtol binary constant handling is incomplete
Date: Tue, 18 Apr 2023 21:13:35 +0000 [thread overview]
Message-ID: <bug-30371-131-o72w8SGsMZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30371-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30371
--- Comment #2 from Eric Blake <eblake at redhat dot com> ---
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3108.doc merely says:
FR-228
7.24.1, 7.31.4.1, K.3.5.3 and K.3.9.1
te
There are semantic changes and inconsistencies for strtol, scanf and similar
functions
see accompanying document
Rejected (no consensus to make this change) with comment: several vendor
solutions were discussed.
so as recently as Feb 2023, the C working group still hasn't made up their
mind.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-18 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 17:44 [Bug libc/30371] New: " bruno at clisp dot org
2023-04-18 19:42 ` [Bug libc/30371] " kdudka at redhat dot com
2023-04-18 21:08 ` eblake at redhat dot com
2023-04-18 21:13 ` eblake at redhat dot com [this message]
2023-04-18 21:42 ` bruno at clisp dot org
2023-04-19 2:46 ` sam at gentoo dot org
2023-04-20 14:58 ` mliska at suse dot cz
2023-05-22 16:42 ` eggert at cs dot ucla.edu
2023-07-03 20:14 ` bruno at clisp dot 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-30371-131-o72w8SGsMZ@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).