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, dmalcolm@redhat.com, mliska@suse.cz,
anlauf@gmx.de
Subject: Re: [PATCH v2 1/3] libcpp: reject codepoints above 0x10FFFF
Date: Mon, 7 Nov 2022 13:04:35 -1000 [thread overview]
Message-ID: <3c8ab0d6-d17e-1933-8d35-b0c0209d06a8@redhat.com> (raw)
In-Reply-To: <20221027231645.67623-2-ben.boeckel@kitware.com>
On 10/27/22 13:16, Ben Boeckel wrote:
> Unicode does not support such values because they are unrepresentable in
> UTF-16.
>
> Signed-off-by: Ben Boeckel <ben.boeckel@kitware.com>
> ---
> libcpp/ChangeLog | 6 ++++++
> libcpp/charset.cc | 4 ++--
> 2 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/libcpp/ChangeLog b/libcpp/ChangeLog
> index 18d5bcceaf0..4d707277531 100644
> --- a/libcpp/ChangeLog
> +++ b/libcpp/ChangeLog
> @@ -1,3 +1,9 @@
> +2022-10-27 Ben Boeckel <ben.boeckel@kitware.com>
> +
> + * include/charset.cc: Reject encodings of codepoints above 0x10FFFF.
> + UTF-16 does not support such codepoints and therefore all Unicode
> + rejects such values.
> +
> 2022-10-19 Lewis Hyatt <lhyatt@gmail.com>
>
> * include/cpplib.h (struct cpp_string): Use new "string_length" GTY.
> diff --git a/libcpp/charset.cc b/libcpp/charset.cc
> index 12a398e7527..e9da6674b5f 100644
> --- a/libcpp/charset.cc
> +++ b/libcpp/charset.cc
> @@ -216,7 +216,7 @@ one_utf8_to_cppchar (const uchar **inbufp, size_t *inbytesleftp,
> if (c <= 0x3FFFFFF && nbytes > 5) return EILSEQ;
>
> /* Make sure the character is valid. */
> - if (c > 0x7FFFFFFF || (c >= 0xD800 && c <= 0xDFFF)) return EILSEQ;
> + if (c > 0x10FFFF || (c >= 0xD800 && c <= 0xDFFF)) return EILSEQ;
Please also adjust the comment before the function that talks about the
0x7FFFFFFF maximum.
>
> *cp = c;
> *inbufp = inbuf;
> @@ -320,7 +320,7 @@ one_utf32_to_utf8 (iconv_t bigend, const uchar **inbufp, size_t *inbytesleftp,
> s += inbuf[bigend ? 2 : 1] << 8;
> s += inbuf[bigend ? 3 : 0];
>
> - if (s >= 0x7FFFFFFF || (s >= 0xD800 && s <= 0xDFFF))
> + if (s > 0x10FFFF || (s >= 0xD800 && s <= 0xDFFF))
> return EILSEQ;
>
> rval = one_cppchar_to_utf8 (s, outbufp, outbytesleftp);
next prev parent reply other threads:[~2022-11-07 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 23:16 [PATCH v2 0/1] RFC: P1689R5 support Ben Boeckel
2022-10-27 23:16 ` [PATCH v2 1/3] libcpp: reject codepoints above 0x10FFFF Ben Boeckel
2022-10-28 12:54 ` David Malcolm
2022-11-07 23:04 ` Jason Merrill [this message]
2022-10-27 23:16 ` [PATCH v2 2/3] libcpp: add a function to determine UTF-8 validity of a C string Ben Boeckel
2022-10-28 12:59 ` David Malcolm
2022-10-28 17:14 ` Ben Boeckel
2022-11-07 23:47 ` Jason Merrill
2022-10-27 23:16 ` [PATCH v2 3/3] p1689r5: initial support Ben Boeckel
2022-10-28 17:15 ` Ben Boeckel
2022-11-01 14:57 ` Tom Tromey
2022-11-01 16:22 ` Ben Boeckel
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=3c8ab0d6-d17e-1933-8d35-b0c0209d06a8@redhat.com \
--to=jason@redhat.com \
--cc=anlauf@gmx.de \
--cc=ben.boeckel@kitware.com \
--cc=brad.king@kitware.com \
--cc=dmalcolm@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mliska@suse.cz \
--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).