public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH v3] Introduce -finline-stringops
Date: Mon, 20 Nov 2023 14:49:54 +0100	[thread overview]
Message-ID: <CAFiYyc2GCwYYhREUE9Tuprk8k29JuQV7wA4_GzzKkf=NS3YY3A@mail.gmail.com> (raw)
In-Reply-To: <oredgkpozm.fsf@lxoliva.fsfla.org>

On Mon, Nov 20, 2023 at 1:51 PM Alexandre Oliva <oliva@adacore.com> wrote:
>
> On Sep 23, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
>
> > On Sep 21, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
> >> On Sep 15, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
> >>> On Jun 22, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
> >>>> On Jun  2, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
> >>>>> Introduce -finline-stringops
>
> >>>> Ping?  https://gcc.gnu.org/pipermail/gcc-patches/2023-June/620472.html
>
> >>> Ping?
>
> >> Here's a refreshed and improved patch, that improves the memcmp
> >> expansion a little, dropping redundant barriers and conditional
> >> branches.
>
> > Introduce -finline-stringops
>
> > This patch introduces -finline-stringops[=fn] to request expansions to
> > start with a loop, so as to still take advantage of known alignment
> > even with long lengths, but without necessarily adding store blocks
> > for every power of two.
>
> Ping?
> https://gcc.gnu.org/pipermail/gcc-patches/2023-September/631227.html
>
> Re-regstrapped on x86_64-linux-gnu, with and without -finline-stringops.

OK.  Can you add a corresponding entry to gcc-14/changes.html?

Thanks,
Richard.

> --
> Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
>    Free Software Activist                   GNU Toolchain Engineer
> More tolerance and less prejudice are key for inclusion and diversity
> Excluding neuro-others for not behaving ""normal"" is *not* inclusive

  reply	other threads:[~2023-11-20 13:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27  4:02 [RFC] Introduce -finline-memset-loops Alexandre Oliva
2023-01-12 13:18 ` Richard Biener
2023-01-14  1:54   ` Alexandre Oliva
2023-01-14  2:12     ` Paul Koning
2023-01-14  3:21       ` Alexandre Oliva
2023-01-16  7:26     ` Richard Biener
2023-01-19 11:25       ` Alexandre Oliva
2023-01-19 11:58         ` Richard Biener
2023-06-02 10:11         ` Alexandre Oliva
2023-06-02 14:58           ` Fangrui Song
2023-06-23  2:23           ` Introduce -finline-stringops (was: Re: [RFC] Introduce -finline-memset-loops) Alexandre Oliva
2023-09-15  7:59             ` Introduce -finline-stringops Alexandre Oliva
2023-09-21  6:52               ` [PATCH v2] " Alexandre Oliva
2023-09-23  5:56                 ` [PATCH v3] " Alexandre Oliva
2023-11-20 12:51                   ` Alexandre Oliva
2023-11-20 13:49                     ` Richard Biener [this message]
2023-12-11 18:43             ` Introduce -finline-stringops (was: Re: [RFC] Introduce -finline-memset-loops) Sam James
2023-12-12  1:42               ` Introduce -finline-stringops Alexandre Oliva

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='CAFiYyc2GCwYYhREUE9Tuprk8k29JuQV7wA4_GzzKkf=NS3YY3A@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=oliva@adacore.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).