From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Tamar Christina <tamar.christina@arm.com>
Cc: nd@arm.com, rguenther@suse.de, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2]middle-end: Support early break/return auto-vectorization.
Date: Wed, 02 Nov 2022 22:50:42 +0100 [thread overview]
Message-ID: <9D26FE2F-11D7-4245-A0A9-94246542DFF9@gmail.com> (raw)
In-Reply-To: <patch-16498-tamar@arm.com>
On 2 November 2022 15:45:39 CET, Tamar Christina via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>Hi All,
>
>This patch adds initial support for early break vectorization in GCC.
>The support is added for any target that implements a vector cbranch optab.
>
>Concretely the kind of loops supported are of the forms:
>
> for (int i = 0; i < N; i++)
> {
> <statements1>
> if (<condition>)
> <action>;
> <statements2>
> }
>
>where <action> can be:
> - break
> - return
Just curious, but don't we have graphite for splitting loops on control flow, respectively reflow loops to help vectorization like in this case? Did you compare, and if so, what's missing?
thanks and cheers,
next prev parent reply other threads:[~2022-11-02 21:50 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 ` Bernhard Reutner-Fischer [this message]
2022-11-02 22:32 ` [PATCH 1/2]middle-end: Support early break/return auto-vectorization 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
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=9D26FE2F-11D7-4245-A0A9-94246542DFF9@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=rguenther@suse.de \
--cc=tamar.christina@arm.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).