public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103911] std::from_chars shouldn't call isdigit
Date: Thu, 06 Jan 2022 14:57:13 +0000	[thread overview]
Message-ID: <bug-103911-4-5HeJVqKWKK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103911-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103911

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:c83ecfbe74a5cf107642b9c5e1680b548ff1a0e1

commit r12-6281-gc83ecfbe74a5cf107642b9c5e1680b548ff1a0e1
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Jan 5 16:25:47 2022 +0000

    libstdc++: Do not use std::isdigit in <charconv> [PR103911]

    This avoids a potential race condition if std::setlocale is used
    concurrently with std::from_chars.

    libstdc++-v3/ChangeLog:

            PR libstdc++/103911
            * include/std/charconv (__from_chars_alpha_to_num): Return
            char instead of unsigned char. Change invalid return value to
            127 instead of using numeric trait.
            (__from_chars_alnum): Fix comment. Do not use std::isdigit.
            Change type of variable to char.

  parent reply	other threads:[~2022-01-06 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 23:49 [Bug libstdc++/103911] New: " blubban at gmail dot com
2022-01-05  0:05 ` [Bug libstdc++/103911] " redi at gcc dot gnu.org
2022-01-06 14:57 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-07 15:19 ` redi at gcc dot gnu.org
2022-04-21 12:33 ` cvs-commit at gcc dot gnu.org
2022-04-26 13:11 ` cvs-commit at gcc dot gnu.org
2022-04-26 13:16 ` redi at gcc dot gnu.org
2022-05-02 11:03 ` cvs-commit at gcc dot gnu.org
2022-05-06 13:13 ` cvs-commit at gcc dot gnu.org
2022-05-11 15:15 ` cvs-commit 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-103911-4-5HeJVqKWKK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).