public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>,
	libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Patch ping^3 ([PATCH] libstdc++: Outline the overlapping case of string _M_replace into a separate function [PR105329])
Date: Mon, 12 Sep 2022 11:15:57 +0200	[thread overview]
Message-ID: <Yx74zRmKfV9xYVHt@tucnak> (raw)
In-Reply-To: <Yw8sMqFGa2VZtetv@tucnak>

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.

Thanks.

	Jakub


  reply	other threads:[~2022-09-12  9:16 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     ` Jakub Jelinek [this message]
2022-09-12  9:24       ` Patch ping^3 " 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=Yx74zRmKfV9xYVHt@tucnak \
    --to=jakub@redhat.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).