From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH]middle-end: don't lower past veclower [PR106063]
Date: Wed, 6 Jul 2022 07:14:06 -0600 [thread overview]
Message-ID: <0982e946-e953-45e2-ab1b-1d73537addf2@gmail.com> (raw)
In-Reply-To: <patch-15911-tamar@arm.com>
On 7/5/2022 9:00 AM, Tamar Christina via Gcc-patches wrote:
> Hi All,
>
> My previous patch can cause a problem if the pattern matches after veclower
> as it may replace the construct with a vector sequence which the target may not
> directly support.
>
> As such don't perform the rewriting if after veclower.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu, x86_64-pc-linux-gnu
> and no issues.
>
> Ok for master? and backport to GCC 12?
>
> Thanks,
> Tamar
>
>
> gcc/ChangeLog:
>
> PR tree-optimization/106063
> * match.pd: Do not apply pattern after veclower.
>
> gcc/testsuite/ChangeLog:
>
> PR tree-optimization/106063
> * gcc.dg/pr106063.c: New test.
OK for both the trunk and gcc-12.
jeff
next prev parent reply other threads:[~2022-07-06 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 15:00 Tamar Christina
2022-07-06 13:14 ` Jeff Law [this message]
2022-07-07 7:18 ` Richard Biener
2022-07-07 7:41 ` Tamar Christina
2022-07-07 7:47 ` Richard Biener
2022-07-08 6:26 ` Tamar Christina
2022-07-08 7:16 ` 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=0982e946-e953-45e2-ab1b-1d73537addf2@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).