From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
Richard Sandiford <richard.sandiford@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] Teach vectorizer to deal with bitfield reads
Date: Mon, 1 Aug 2022 11:13:45 +0100 [thread overview]
Message-ID: <186b5113-b54e-8432-ddd0-958a2de963e9@arm.com> (raw)
In-Reply-To: <YuO3FvWoUm148X8J@tucnak>
On 29/07/2022 11:31, Jakub Jelinek wrote:
> On Fri, Jul 29, 2022 at 09:57:29AM +0100, Andre Vieira (lists) via Gcc-patches wrote:
>> The 'only on the vectorized code path' remains the same though as vect_recog
>> also only happens on the vectorized code path right?
> if conversion (in some cases) duplicates a loop and guards one copy with
> an ifn which resolves to true if that particular loop is vectorized and
> false otherwise. So, then changes that shouldn't be done in case of
> vectorization failure can be done on the for vectorizer only copy of the
> loop.
>
> Jakub
I'm pretty sure vect_recog patterns have no effect on scalar codegen if
the vectorization fails too. The patterns live as new vect_stmt_info's
and no changes are actually done to the scalar loop. That was the point
I was trying to make, but it doesn't matter that much, as I said I am
happy to do this in if convert.
next prev parent reply other threads:[~2022-08-01 10:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 10:00 Andre Vieira (lists)
2022-07-27 11:37 ` Richard Biener
2022-07-29 8:57 ` Andre Vieira (lists)
2022-07-29 9:11 ` Richard Biener
2022-07-29 10:31 ` Jakub Jelinek
2022-07-29 10:52 ` Richard Biener
2022-08-01 10:21 ` Andre Vieira (lists)
2022-08-01 13:16 ` Richard Biener
2022-08-08 14:06 ` [PATCH] Teach vectorizer to deal with bitfield accesses (was: [RFC] Teach vectorizer to deal with bitfield reads) Andre Vieira (lists)
2022-08-09 14:34 ` Richard Biener
2022-08-16 10:24 ` Andre Vieira (lists)
2022-08-17 12:49 ` Richard Biener
2022-08-25 9:09 ` Andre Vieira (lists)
2022-09-08 9:07 ` Andre Vieira (lists)
2022-09-08 11:51 ` Richard Biener
2022-09-26 15:23 ` Andre Vieira (lists)
2022-09-27 12:34 ` Richard Biener
2022-09-28 9:43 ` Andre Vieira (lists)
2022-09-28 17:31 ` Andre Vieira (lists)
2022-09-29 7:54 ` Richard Biener
2022-10-07 14:20 ` Andre Vieira (lists)
2022-10-12 1:55 ` Hongtao Liu
2022-10-12 2:11 ` Hongtao Liu
2022-08-01 10:13 ` Andre Vieira (lists) [this message]
2022-10-12 9:02 ` [RFC] Teach vectorizer to deal with bitfield reads Eric Botcazou
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=186b5113-b54e-8432-ddd0-958a2de963e9@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
--cc=richard.sandiford@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).