public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-2053] libcpp: allow UCS_LIMIT codepoints in UTF-8 strings Date: Fri, 23 Jun 2023 20:04:40 +0000 (GMT) [thread overview] Message-ID: <20230623200440.0AC913858421@sourceware.org> (raw) https://gcc.gnu.org/g:b7fc0a3be52f78100a270b63e7555fde078fd2e3 commit r14-2053-gb7fc0a3be52f78100a270b63e7555fde078fd2e3 Author: Ben Boeckel <me@benboeckel.net> Date: Wed Jun 21 14:58:20 2023 -0400 libcpp: allow UCS_LIMIT codepoints in UTF-8 strings Fixes r14-1954 (libcpp: reject codepoints above 0x10FFFF, 2023-06-06) libcpp/ * charset.cc: Allow `UCS_LIMIT` in UTF-8 strings. Reported-by: Damien Guibouret <damien.guibouret@partition-saving.com> Signed-off-by: Ben Boeckel <ben.boeckel@kitware.com> Diff: --- libcpp/charset.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libcpp/charset.cc b/libcpp/charset.cc index d492f66adbc..7b625c9956a 100644 --- a/libcpp/charset.cc +++ b/libcpp/charset.cc @@ -1891,7 +1891,7 @@ cpp_valid_utf8_p (const char *buffer, size_t num_bytes) invalid because they cannot be represented in UTF-16. Reject such values.*/ - if (cp >= UCS_LIMIT) + if (cp > UCS_LIMIT) return false; } /* No problems encountered. */
reply other threads:[~2023-06-23 20:04 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230623200440.0AC913858421@sourceware.org \ --to=jason@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).