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/61634] [4.8/4.9/4.10 Regression] ICE in in vect_get_vec_def_for_operand, at tree-vect-stmts.c:1423 Date: Tue, 08 Jul 2014 11:29:00 -0000 [thread overview] Message-ID: <bug-61634-4-LXV9LFaDk3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61634-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61634 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- We have patt_24 = DOT_PROD_EXPR <_12, _12, prephitmp_48>; and _12 = _11 >> 2; is not STMT_VINFO_IN_PATTERN_P but it doesn't have a vec_stmt yet even though it is there: vect__12.29_90 = vect__11.27_87 >> 2; vect__12.29_91 = vect__11.28_89 >> 2; _12 = _11 >> 2; that's because vectorizable_shift doesn't assign to *vec_stmt!? if (slp_node) continue; if (j == 0) STMT_VINFO_VEC_STMT (stmt_info) = *vec_stmt = new_stmt; else STMT_VINFO_RELATED_STMT (prev_stmt_info) = new_stmt; if it's part of an SLP node... (pure_slp). I'm not sure we can vectorize this case.
next prev parent reply other threads:[~2014-07-08 11:29 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-27 17:36 [Bug c/61634] New: [4.8.3/4.9.1] " manuel.lauss at googlemail dot com 2014-06-28 7:36 ` [Bug tree-optimization/61634] [4.8/4.9/4.10 Regression] " trippels at gcc dot gnu.org 2014-06-30 13:27 ` jakub at gcc dot gnu.org 2014-07-07 11:08 ` rguenth at gcc dot gnu.org 2014-07-08 11:29 ` rguenth at gcc dot gnu.org [this message] 2014-11-25 16:35 ` [Bug tree-optimization/61634] [4.8/4.9/5 " rguenth at gcc dot gnu.org 2014-11-27 9:34 ` rguenth at gcc dot gnu.org 2014-11-27 9:37 ` [Bug tree-optimization/61634] [4.8/4.9 " rguenth at gcc dot gnu.org 2014-12-10 13:01 ` rguenth at gcc dot gnu.org 2014-12-19 13:44 ` jakub at gcc dot gnu.org 2015-02-23 12:38 ` rguenth at gcc dot gnu.org 2015-02-26 14:18 ` [Bug tree-optimization/61634] [4.8 " rguenth at gcc dot gnu.org 2015-02-26 14:39 ` 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-61634-4-LXV9LFaDk3@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).