public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106063] [12 Regression] ICE: in gimple_expand_vec_cond_expr, at gimple-isel.cc:281 with -O2 -fno-tree-forwprop --param=evrp-mode=legacy-first Date: Wed, 27 Jul 2022 09:24:15 +0000 [thread overview] Message-ID: <bug-106063-4-AjUfx13KeR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106063-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106063 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:13d23c313374e15186f33fa6d57a0c9fd5d8b486 commit r12-8625-g13d23c313374e15186f33fa6d57a0c9fd5d8b486 Author: Tamar Christina <tamar.christina@arm.com> Date: Fri Jul 8 08:30:22 2022 +0100 middle-end: don't lower past veclower [PR106063] 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 unless the target supports the operation. If before veclower do the rewriting as well if the target didn't support the original operation either. gcc/ChangeLog: PR tree-optimization/106063 * match.pd: Do not apply pattern after veclower is not supported. gcc/testsuite/ChangeLog: PR tree-optimization/106063 * gcc.dg/pr106063.c: New test. (cherry picked from commit f7854e2faf7640230062dec3596e71773ca500ed)
next prev parent reply other threads:[~2022-07-27 9:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-23 6:46 [Bug tree-optimization/106063] New: [13 " zsojka at seznam dot cz 2022-06-23 14:22 ` [Bug tree-optimization/106063] " amacleod at redhat dot com 2022-06-24 10:29 ` rguenth at gcc dot gnu.org 2022-06-24 10:29 ` [Bug tree-optimization/106063] [12/13 " rguenth at gcc dot gnu.org 2022-06-24 11:33 ` tnfchris at gcc dot gnu.org 2022-06-26 22:10 ` tnfchris at gcc dot gnu.org 2022-07-08 7:31 ` cvs-commit at gcc dot gnu.org 2022-07-10 8:41 ` [Bug tree-optimization/106063] [12 " cvs-commit at gcc dot gnu.org 2022-07-27 9:24 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-27 9:24 ` cvs-commit at gcc dot gnu.org 2022-07-27 9:25 ` rguenth 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-106063-4-AjUfx13KeR@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: linkBe 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).