From: Alexandre Oliva <oliva@adacore.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Introduce -finline-stringops
Date: Fri, 15 Sep 2023 04:59:31 -0300 [thread overview]
Message-ID: <orbke3uasc.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orsfaiq5m6.fsf_-_@lxoliva.fsfla.org> (Alexandre Oliva's message of "Thu, 22 Jun 2023 23:23:13 -0300")
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?
--
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
next prev parent reply other threads:[~2023-09-15 7:59 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 ` Alexandre Oliva [this message]
2023-09-21 6:52 ` [PATCH v2] Re: Introduce -finline-stringops 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
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=orbke3uasc.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@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).