From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Patch ping^3 ([PATCH] libstdc++: Outline the overlapping case of string _M_replace into a separate function [PR105329])
Date: Mon, 12 Sep 2022 10:24:50 +0100 [thread overview]
Message-ID: <CACb0b4nODcAgEiQj=oyiLqT4b7kB++b=e62Bm2DZ3KQB3kunzA@mail.gmail.com> (raw)
In-Reply-To: <Yx74zRmKfV9xYVHt@tucnak>
On Mon, 12 Sept 2022 at 10:16, Jakub Jelinek <jakub@redhat.com> wrote:
>
> On Wed, Aug 31, 2022 at 11:38:58AM +0200, Jakub Jelinek via Gcc-patches wrote:
> > On Wed, Aug 10, 2022 at 01:27:51PM +0200, Jakub Jelinek via Gcc-patches wrote:
> > > On Wed, Jul 27, 2022 at 11:33:29AM +0200, Jakub Jelinek via Gcc-patches wrote:
> > > > The following patch is partially a workaround for bogus warnings
> > > > when the compiler isn't able to fold _M_disjunct call into constant
> > > > false, but also an optimization attempt - assuming _M_disjunct (__s)
> > > > is rare, the patch should shrink code size for the common case and
> > > > use library or for non-standard instantiations an out of line
> > > > function to handle the rare case.
> > >
> > > I'd like to ping this patch.
> >
> > I'd like to ping this patch again.
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598896.html
>
> Ping again.
OK for trunk, sorry for the slow review.
prev parent reply other threads:[~2022-09-12 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 9:33 [PATCH] libstdc++: Outline the overlapping case of string _M_replace into a separate function [PR105329] Jakub Jelinek
2022-08-10 11:27 ` Jakub Jelinek
2022-08-31 9:38 ` Patch ping ([PATCH] libstdc++: Outline the overlapping case of string _M_replace into a separate function [PR105329]) Jakub Jelinek
2022-09-12 9:15 ` Patch ping^3 " Jakub Jelinek
2022-09-12 9:24 ` Jonathan Wakely [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='CACb0b4nODcAgEiQj=oyiLqT4b7kB++b=e62Bm2DZ3KQB3kunzA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).