From: Jason Merrill <jason@redhat.com>
To: Ben Boeckel <ben.boeckel@kitware.com>, gcc-patches@gcc.gnu.org
Cc: nathan@acm.org, fortran@gcc.gnu.org, gcc@gcc.gnu.org,
brad.king@kitware.com
Subject: Re: [PATCH v6 1/4] libcpp: reject codepoints above 0x10FFFF
Date: Mon, 19 Jun 2023 17:34:22 -0400 [thread overview]
Message-ID: <8e347f55-8102-a2a0-a98d-7d3155d1ea8a@redhat.com> (raw)
In-Reply-To: <20230606205025.3164738-2-ben.boeckel@kitware.com>
On 6/6/23 16:50, Ben Boeckel wrote:
> Unicode does not support such values because they are unrepresentable in
> UTF-16.
Pushed.
> libcpp/
>
> * charset.cc: Reject encodings of codepoints above 0x10FFFF.
> UTF-16 does not support such codepoints and therefore all
> Unicode rejects such values.
>
> Signed-off-by: Ben Boeckel <ben.boeckel@kitware.com>
> ---
> libcpp/charset.cc | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/libcpp/charset.cc b/libcpp/charset.cc
> index d7f323b2cd5..3b34d804cf1 100644
> --- a/libcpp/charset.cc
> +++ b/libcpp/charset.cc
> @@ -1886,6 +1886,13 @@ cpp_valid_utf8_p (const char *buffer, size_t num_bytes)
> int err = one_utf8_to_cppchar (&iter, &bytesleft, &cp);
> if (err)
> return false;
> +
> + /* Additionally, Unicode declares that all codepoints above 0010FFFF are
> + invalid because they cannot be represented in UTF-16.
> +
> + Reject such values.*/
> + if (cp >= 0x10FFFF)
> + return false;
> }
> /* No problems encountered. */
> return true;
next prev parent reply other threads:[~2023-06-19 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 20:50 [PATCH v6 0/4] P1689R5 support Ben Boeckel
2023-06-06 20:50 ` [PATCH v6 1/4] libcpp: reject codepoints above 0x10FFFF Ben Boeckel
2023-06-19 21:34 ` Jason Merrill [this message]
2023-06-06 20:50 ` [PATCH v6 2/4] p1689r5: initial support Ben Boeckel
2023-06-06 20:50 ` [PATCH v6 3/4] c++modules: report imported CMI files as dependencies Ben Boeckel
2023-06-06 20:50 ` [PATCH v6 4/4] c++modules: report module mapper files as a dependency Ben Boeckel
2023-06-08 17:59 ` [PATCH v6 0/4] P1689R5 support Maxim Kuvyrkov
2023-06-16 19:48 ` Ben Boeckel
2023-06-16 23:15 ` Ben Boeckel
2023-06-17 3:55 ` Jason Merrill
2023-06-17 14:43 ` Ben Boeckel
2023-06-20 0:54 ` Jason Merrill
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=8e347f55-8102-a2a0-a98d-7d3155d1ea8a@redhat.com \
--to=jason@redhat.com \
--cc=ben.boeckel@kitware.com \
--cc=brad.king@kitware.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=nathan@acm.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).