public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2]middle-end: Support early break/return auto-vectorization.
Date: Wed, 16 Nov 2022 11:52:13 -0700	[thread overview]
Message-ID: <8d25ff4f-025e-5534-6148-64359375ada3@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2211161216230.3995@jbgna.fhfr.qr>


On 11/16/22 05:17, Richard Biener via Gcc-patches wrote:
> On Tue, 15 Nov 2022, Tamar Christina wrote:
>
>> Ping, anyone alive in here? ?
> You have to queue behind all the others waiting, sorry.  But it's on
> my list of things to look at - but it's also a complex thing and thus
> requires a larger chunk of time.

Yea, it was quite an end-of-stage1 this cycle.  I'm slogging through as 
much as I can day-to-day.


jeff



  reply	other threads:[~2022-11-16 18:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 14:45 Tamar Christina
2022-11-02 14:46 ` [PATCH 2/2]AArch64 Add implementation for vector cbranch Tamar Christina
2022-11-02 21:50 ` [PATCH 1/2]middle-end: Support early break/return auto-vectorization Bernhard Reutner-Fischer
2022-11-02 22:32   ` Jeff Law
2022-11-03  8:51     ` Tamar Christina
2022-11-08 17:36 ` Tamar Christina
2022-11-15 11:11   ` Tamar Christina
2022-11-16 12:17     ` Richard Biener
2022-11-16 18:52       ` Jeff Law [this message]
2022-11-18 15:04 ` Richard Biener
2022-11-18 18:23   ` Tamar Christina
2022-11-19 10:49     ` Tamar Christina
2022-11-24  9:02     ` Richard Biener
2022-11-24 11:56       ` Tamar Christina
2022-11-25  9:33         ` Richard Biener
2022-11-25 10:32           ` Tamar Christina
2022-12-13 15:01             ` Tamar Christina
2022-12-14  9:41               ` 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=8d25ff4f-025e-5534-6148-64359375ada3@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@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).