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 tree-optimization/62075] [4.8/4.9/4.10 Regression] Vectorizer ICE on dolphin
Date: Mon, 11 Aug 2014 09:55:00 -0000 [thread overview]
Message-ID: <bug-62075-4-CQa6tKpaDN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62075-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62075
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue here is that we have a load group with one stmt feeding a condition.
For some reason we think that we can support vectorizing
_7 = _4 != 0
with _4 being defined by a pure-SLP def. Which looks odd - the this is clearly
not a pure SLP node!
Fix:
Index: tree-vect-slp.c
===================================================================
--- tree-vect-slp.c (revision 213809)
+++ tree-vect-slp.c (working copy)
@@ -1793,7 +1793,8 @@ vect_detect_hybrid_slp_stmts (slp_tree n
&& (stmt_vinfo = vinfo_for_stmt (use_stmt))
&& !STMT_SLP_TYPE (stmt_vinfo)
&& (STMT_VINFO_RELEVANT (stmt_vinfo)
- || VECTORIZABLE_CYCLE_DEF (STMT_VINFO_DEF_TYPE (stmt_vinfo)))
+ || VECTORIZABLE_CYCLE_DEF (STMT_VINFO_DEF_TYPE (stmt_vinfo))
+ || STMT_VINFO_IN_PATTERN_P (stmt_vinfo))
&& !(gimple_code (use_stmt) == GIMPLE_PHI
&& STMT_VINFO_DEF_TYPE (stmt_vinfo)
== vect_reduction_def))
next prev parent reply other threads:[~2014-08-11 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 19:30 [Bug tree-optimization/62075] New: " jakub at gcc dot gnu.org
2014-08-09 19:36 ` [Bug tree-optimization/62075] " trippels at gcc dot gnu.org
2014-08-11 9:24 ` rguenth at gcc dot gnu.org
2014-08-11 9:55 ` rguenth at gcc dot gnu.org [this message]
2014-08-11 14:49 ` rguenth at gcc dot gnu.org
2014-08-13 14:18 ` [Bug tree-optimization/62075] [4.8/4.9 " rguenth at gcc dot gnu.org
2014-08-26 19:21 ` trippels at gcc dot gnu.org
2014-09-09 11:43 ` rguenth at gcc dot gnu.org
2014-09-09 13:18 ` [Bug tree-optimization/62075] [4.8 " rguenth at gcc dot gnu.org
2014-09-09 13:19 ` 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-62075-4-CQa6tKpaDN@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).