public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "irar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/52091] [4.7 Regression] ICE: verify_gimple failed Date: Sun, 05 Feb 2012 05:59:00 -0000 [thread overview] Message-ID: <bug-52091-4-bmyAjYF9Wz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52091-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52091 --- Comment #8 from irar at gcc dot gnu.org 2012-02-05 05:58:22 UTC --- Author: irar Date: Sun Feb 5 05:58:18 2012 New Revision: 183902 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183902 Log: PR tree-optimization/52091 * tree-vectorizer.h (vect_is_simple_use): Add an argument. (vect_is_simple_use_1): Likewise. * tree-vect-loop.c (vectorizable_reduction): Update calls to vect_is_simple_use_1 and vect_is_simple_use. (vectorizable_live_operation): Likewise. * tree-vect-patterns.c (widened_name_p, vect_recog_vector_vector_shift_pattern, check_bool_pattern): Likewise. * tree-vect-stmts.c (process_use, vect_get_vec_def_for_operand, vectorizable_call, vectorizable_conversion, vectorizable_assignment, vectorizable_shift, vectorizable_operation, vectorizable_store, vectorizable_load): Likewise. (vect_is_simple_cond): Add an argument, pass it to vect_is_simple_use_1. (vectorizable_condition): Update calls to vect_is_simple_cond, vect_is_simple_use. (vect_is_simple_use): Add an argument, the statement in which OPERAND is used. Check that if OPERAND's def stmt is a double reduction phi node, the use is a phi node too. (vect_is_simple_use_1): Add an argument, pass it to vect_is_simple_use. * tree-vect-slp.c (vect_get_and_check_slp_defs): Update a call to vect_is_simple_use. Added: trunk/gcc/testsuite/gcc.dg/vect/pr52091.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vect-loop.c trunk/gcc/tree-vect-patterns.c trunk/gcc/tree-vect-slp.c trunk/gcc/tree-vect-stmts.c trunk/gcc/tree-vectorizer.h
next prev parent reply other threads:[~2012-02-05 5:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-02 4:42 [Bug c/52091] New: " regehr at cs dot utah.edu 2012-02-02 4:47 ` [Bug tree-optimization/52091] [4.7 Regression] " pinskia at gcc dot gnu.org 2012-02-02 4:53 ` pinskia at gcc dot gnu.org 2012-02-02 8:30 ` jakub at gcc dot gnu.org 2012-02-02 9:01 ` jakub at gcc dot gnu.org 2012-02-02 12:07 ` jakub at gcc dot gnu.org 2012-02-02 13:23 ` irar at il dot ibm.com 2012-02-02 13:42 ` jakub at gcc dot gnu.org 2012-02-02 15:16 ` irar at il dot ibm.com 2012-02-05 5:59 ` irar at gcc dot gnu.org [this message] 2012-02-06 8:42 ` irar at il dot ibm.com
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-52091-4-bmyAjYF9Wz@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).