public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/115304] gcc.dg/vect/slp-gap-1.c FAILs
Date: Thu, 20 Jun 2024 06:45:27 +0000 [thread overview]
Message-ID: <bug-115304-4-rljCzMnYfA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115304-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115304
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 20 Jun 2024, pinskia at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115304
>
> Andrew Pinski <pinskia at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |pinskia at gcc dot gnu.org
>
> --- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> Note when I am adding V4QI support to the aarch64 backend (emulating it via
> V8QI), I am getting a failure in slp-gap-1.c but it is different from the
> others.
>
> Without V4QI, the pattern matched `\{_\[0-9\]\+, 0` was able to match 6 times.
>
> we got in the IR:
> ```
> unsigned int _50;
> vector(2) unsigned int _49;
> ...
> _50 = MEM <unsigned int> [(uint8_t *)vectp_pix1.5_58];
> _49 = {_50, 0};
> ```
>
>
> But afterwards we now get:
> ```
> vector(4) unsigned char _50;
> vector(8) unsigned char vect__34.9;
> ...
> _50 = MEM <vector(4) unsigned char> [(uint8_t *)vectp_pix1.5_58];
> vect__34.9_49 = {_50, { 0, 0, 0, 0 }};
> ```
>
> Which produces the exact same code. I am trying to figure out the best way to
> change the testcase pattern to make sure we don't match:
> vect__37.23_6 = VEC_PERM_EXPR <vect__37.15_30, vect__37.19_13, { 0, 1, 2, 3,
> 8, 9, 10, 11 }>;
>
> too.
>
> `\{_\[0-9\]\+, { 0, 0` I think that will work but should I just do an
> alternative for the scan-tree-dump-times or should I put it as a seperate one
> with some target selection here?
Maybe match \{_\[0-9\]\+, (0\|{ 0(, 0)+ })? (with proper quoting)
prev parent reply other threads:[~2024-06-20 6:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 8:45 [Bug tree-optimization/115304] New: " ro at gcc dot gnu.org
2024-05-31 8:46 ` [Bug tree-optimization/115304] " ro at gcc dot gnu.org
2024-05-31 8:46 ` ro at gcc dot gnu.org
2024-05-31 12:26 ` rguenth at gcc dot gnu.org
2024-06-03 9:18 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-06-03 10:10 ` tschwinge at gcc dot gnu.org
2024-06-03 10:10 ` tschwinge at gcc dot gnu.org
2024-06-03 10:13 ` tschwinge at gcc dot gnu.org
2024-06-03 12:43 ` rguenth at gcc dot gnu.org
2024-06-03 12:46 ` cvs-commit at gcc dot gnu.org
2024-06-03 12:47 ` rguenth at gcc dot gnu.org
2024-06-03 13:33 ` ams at gcc dot gnu.org
2024-06-03 13:51 ` rguenther at suse dot de
2024-06-03 14:11 ` ams at gcc dot gnu.org
2024-06-20 5:15 ` pinskia at gcc dot gnu.org
2024-06-20 6:45 ` rguenther at suse dot de [this message]
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=bug-115304-4-rljCzMnYfA@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).