From: Kefu Chai <kefu.chai@scylladb.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Kefu Chai <tchaikov@gmail.com>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: increment *this instead of this
Date: Sat, 18 May 2024 15:42:20 +0800 [thread overview]
Message-ID: <CAKb5Zx=aUteKzU1d1K1j4Echyk_wbU5K-1fT9R_+usikkdD7aw@mail.gmail.com> (raw)
In-Reply-To: <ZkhX3PJmXEc62Rsx@tucnak>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
On Sat, May 18, 2024 at 3:25 PM Jakub Jelinek <jakub@redhat.com> wrote:
> On Sat, May 18, 2024 at 02:53:20PM +0800, Kefu Chai wrote:
> > libstdc++-v3/ChangeLog:
> >
> > * include/bits/unicode.h (enable_borrowed_range): Call ++(*this)
> > instead of ++this
>
> This should be already fixed, see https://gcc.gnu.org/PR115119
Thanks Jakub. Indeed. The mirror of the gcc source repo I am using has some
latencies.
>
> Jakub
>
>
prev parent reply other threads:[~2024-05-18 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 6:53 Kefu Chai
2024-05-18 7:25 ` Jakub Jelinek
2024-05-18 7:42 ` 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='CAKb5Zx=aUteKzU1d1K1j4Echyk_wbU5K-1fT9R_+usikkdD7aw@mail.gmail.com' \
--to=kefu.chai@scylladb.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=tchaikov@gmail.com \
/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).