From: kefu chai <tchaikov@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH v2 0/1] Set _M_string_length before calling _M_dispose()
Date: Wed, 3 May 2023 20:30:49 +0800 [thread overview]
Message-ID: <CAJE9aOM8PeHu3z72VrWj6YCwmrYZ2RkVTOpJMx2u8D=rMj=GwA@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4k5isDU-5Rn6YyBqNUZygjJzD65s_rx8BzT3LJMg6UY9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
Le mer. 3 mai 2023 à 20:22, Jonathan Wakely <jwakely@redhat.com> a écrit :
>
>
> On Wed, 3 May 2023 at 03:17, Kefu Chai via Libstdc++ <
> libstdc++@gcc.gnu.org> wrote:
>
>> Hi Jonathan,
>>
>> Thank you for your review and suggestion. The change looks great!
>> Assigning a value with an immediate zero is indeed much faster.
>>
>> in v2:
>>
>> * revised the commit message a little bit, I found it a little bit
>> difficult to parse when re-reading it.
>> * associated the commit with PR/libstdc++/109703. as I just filed
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109706, which turns out
>> to be a dup of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109703
>>
>> The rest of the v2 patch is identical to the one attached in your reply.
>>
>> Would you please taking another look?
>>
>
> Thanks. I've pushed it to trunk as
> cbf6c7a1d16490a1e63e9a5ce00e9a5c44c4c2f2 and will backport it too.
>
> I altered the commit msg again, because "input_iterator" is a C++20
> concept, and here we're just talking about types meeting the old
> C[[17InputIterator requirements, not types modelling the concept. I also
> added references to the commit and PR that added the
> __builtin_unreachable().
>
Awesome! The commit message is much better now. Thank you very much for
your help!
>
>
>> Kefu Chai (1):
>> libstdc++: Set _M_string_length before calling _M_dispose() [PR109703]
>>
>> libstdc++-v3/include/bits/basic_string.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> --
>> 2.40.1
>>
>> --
Regards
Kefu Chai
prev parent reply other threads:[~2023-05-03 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230501070622.847749-2-tchaikov@gmail.com>
2023-05-03 2:17 ` Kefu Chai
2023-05-03 2:17 ` [PATCH v2 1/1] libstdc++: Set _M_string_length before calling _M_dispose() [PR109703] Kefu Chai
2023-05-03 12:22 ` [PATCH v2 0/1] Set _M_string_length before calling _M_dispose() Jonathan Wakely
2023-05-03 12:30 ` kefu chai [this message]
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='CAJE9aOM8PeHu3z72VrWj6YCwmrYZ2RkVTOpJMx2u8D=rMj=GwA@mail.gmail.com' \
--to=tchaikov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--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).