public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107920] [13 Regression] ICE in execute_todo, at passes.cc:2140
Date: Wed, 30 Nov 2022 11:48:14 +0000 [thread overview]
Message-ID: <bug-107920-4-nTMuy31LFX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107920-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > It is specifically svld1rq_s8 folding into:
> > # VUSE <.MEM>
> > _5 = MEM <vector(16) signed char> [(signed char * {ref-all})x_3(D)];
> >
> >
> > Which is done by svld1rq_impl::fold (aarch64-sve-builtins-base.cc:1214).
>
> Which was added by r13-1055-g494bec025002df .
>
> The question becomes is gimple folding allowed to add MEM references here or
> not?
Yes, but the folding needs to properly handle virtual operands. Instead it
does
- # VUSE <.MEM_2(D)>
- _4 = svld1rq_s8 (_1, x_3(D));
+ # VUSE <.MEM>
+ _5 = MEM <vector(16) signed char> [(signed char * {ref-all})x_3(D)];
+ _4 = VEC_PERM_EXPR <_5, _5, { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
14, 15, ... }>;
see how gimple-fold.cc handles them.
next prev parent reply other threads:[~2022-11-30 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 16:53 [Bug tree-optimization/107920] New: " asolokha at gmx dot com
2022-11-29 18:42 ` [Bug tree-optimization/107920] " pinskia at gcc dot gnu.org
2022-11-29 18:46 ` pinskia at gcc dot gnu.org
2022-11-29 18:50 ` pinskia at gcc dot gnu.org
2022-11-29 18:51 ` pinskia at gcc dot gnu.org
2022-11-29 19:18 ` pinskia at gcc dot gnu.org
2022-11-29 19:54 ` pinskia at gcc dot gnu.org
2022-11-29 19:59 ` [Bug target/107920] " pinskia at gcc dot gnu.org
2022-11-29 20:12 ` pinskia at gcc dot gnu.org
2022-11-29 20:36 ` pinskia at gcc dot gnu.org
2022-11-30 11:48 ` rguenth at gcc dot gnu.org [this message]
2022-11-30 11:51 ` rguenth at gcc dot gnu.org
2022-11-30 16:56 ` prathamesh3492 at gcc dot gnu.org
2022-12-01 12:22 ` jakub at gcc dot gnu.org
2022-12-01 18:06 ` prathamesh3492 at gcc dot gnu.org
2022-12-02 9:13 ` prathamesh3492 at gcc dot gnu.org
2022-12-07 8:06 ` cvs-commit at gcc dot gnu.org
2022-12-08 15:55 ` jakub at gcc dot gnu.org
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-107920-4-nTMuy31LFX@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).