From: Jeff Law <law@redhat.com>
To: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>,
Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] ldist: Recognize rawmemchr loop patterns
Date: Thu, 25 Feb 2021 16:49:53 -0700 [thread overview]
Message-ID: <842e391b-4234-f048-0e31-0082ef052735@redhat.com> (raw)
In-Reply-To: <YDfX7V4iLtHjs1um@localhost.localdomain>
On 2/25/21 10:01 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
> Ping
Given this is not a regression it needs to wait for gcc-12.
jeff
next prev parent reply other threads:[~2021-02-25 23:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 12:47 Stefan Schulze Frielinghaus
2021-02-09 8:57 ` Richard Biener
2021-02-14 10:27 ` Stefan Schulze Frielinghaus
2021-02-25 17:01 ` Stefan Schulze Frielinghaus
2021-02-25 23:49 ` Jeff Law [this message]
2021-03-02 12:29 ` Richard Biener
2021-03-03 17:17 ` Stefan Schulze Frielinghaus
2021-03-16 17:13 ` Stefan Schulze Frielinghaus
2021-04-08 8:23 ` Stefan Schulze Frielinghaus
2021-05-04 17:25 ` Stefan Schulze Frielinghaus
2021-05-05 9:36 ` Richard Biener
2021-05-05 10:03 ` Richard Biener
2021-05-07 12:32 ` Stefan Schulze Frielinghaus
2021-05-20 9:24 ` Richard Biener
2021-05-20 18:37 ` Stefan Schulze Frielinghaus
2021-06-14 17:26 ` Stefan Schulze Frielinghaus
2021-06-16 14:22 ` Richard Biener
2021-06-25 10:23 ` Stefan Schulze Frielinghaus
2021-08-06 14:02 ` Stefan Schulze Frielinghaus
2021-08-20 10:35 ` Richard Biener
2021-09-03 8:00 ` Stefan Schulze Frielinghaus
2021-09-06 9:56 ` Richard Biener
2021-09-13 14:53 ` Stefan Schulze Frielinghaus
2021-09-17 8:08 ` Richard Biener
2021-10-11 16:02 ` Stefan Schulze Frielinghaus
2022-01-31 13:16 ` Tom de Vries
2022-01-31 15:00 ` Richard Biener
2022-01-31 16:26 ` [PATCH][ldist] Don't add lib calls with -fno-tree-loop-distribute-patterns Tom de Vries
2022-02-01 7:04 ` Richard Biener
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=842e391b-4234-f048-0e31-0082ef052735@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=stefansf@linux.ibm.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).