From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dimitrij Mijoski <dmjpp@hotmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH v2] libstdc++: Fix Unicode codecvt and add tests [PR86419]
Date: Tue, 10 Jan 2023 13:28:02 +0000 [thread overview]
Message-ID: <CAH6eHdSsfPj7aLn+jKqZpO9Nbw+qzBHs98yc+wjn4AkMvjpo4g@mail.gmail.com> (raw)
In-Reply-To: <AM0PR04MB541256BD6B9838E4BE055B85ACFF9@AM0PR04MB5412.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Tue, 10 Jan 2023, 13:00 Dimitrij Mijoski wrote:
> Fixes the conversion from UTF-8 to UTF-16 to properly return partial
> instead ok.
> Fixes the conversion from UTF-16 to UTF-8 to properly return partial
> instead ok.
> Fixes the conversion from UTF-8 to UCS-2 to properly return partial
> instead error.
> Fixes the conversion from UTF-8 to UCS-2 to treat 4-byte UTF-8 sequences
> as error just by seeing the leading byte.
> Fixes UTF-8 decoding for all codecvts so they detect error at the end of
> the input range when the last code point is also incomplete.
>
Thanks for the patch. Do you have a copyright assignment for gcc filed with
the FSF? If not, we require that, or a DCO sign-off. See
https://gcc.gnu.org/contribute.html#legal
and
https://gcc.gnu.org/dco.html
for more details.
next prev parent reply other threads:[~2023-01-10 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 12:58 Dimitrij Mijoski
2023-01-10 13:28 ` Jonathan Wakely [this message]
2023-01-10 13:43 ` Dimitrij Mijoski
2023-01-10 14:03 ` Jonathan Wakely
2023-01-13 1:08 ` Jonathan Wakely
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=CAH6eHdSsfPj7aLn+jKqZpO9Nbw+qzBHs98yc+wjn4AkMvjpo4g@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=dmjpp@hotmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).