public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54346] combine permutations
Date: Tue, 25 Oct 2022 05:53:24 +0000 [thread overview]
Message-ID: <bug-54346-4-Xpnl2sBhfh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54346-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54346
--- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #7)
> (In reply to Marc Glisse from comment #6)
> > The log says that this breaks tree-ssa/forwprop-19.c, but I don't see any
> > xfail or anything. Does it only fail because gimple-simplify leaves some
> > dead code around, so you could update the test to scan the next DCE pass
> > dump instead of forwprop1? Or are we missing a transformation that just
> > detects a VEC_PERM_EXPR with an identity permutation?
>
> Uoops, I didn't notice this, will add an incremental patch to handle the
> indentical index (forwporp-19.c) scenario, sorry.
It's fixed.
prev parent reply other threads:[~2022-10-25 5:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 14:02 [Bug tree-optimization/54346] New: " glisse at gcc dot gnu.org
2021-08-25 7:26 ` [Bug tree-optimization/54346] " pinskia at gcc dot gnu.org
2021-08-25 9:02 ` pinskia at gcc dot gnu.org
2022-06-07 9:10 ` crazylht at gmail dot com
2022-10-11 6:12 ` cvs-commit at gcc dot gnu.org
2022-10-11 6:21 ` glisse at gcc dot gnu.org
2022-10-11 6:36 ` crazylht at gmail dot com
2022-10-21 7:17 ` cvs-commit at gcc dot gnu.org
2022-10-25 5:53 ` crazylht at gmail dot com [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-54346-4-Xpnl2sBhfh@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).