public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "irar at il dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51606] [4.7 Regression] FAIL: gcc.dg/vect/pr51015.c (internal compiler error) on ppc*-*-*
Date: Sun, 18 Dec 2011 12:02:00 -0000 [thread overview]
Message-ID: <bug-51606-4-vb4fovGarG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51606-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51606
Ira Rosen <irar at il dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011-12-18
CC| |irar at il dot ibm.com
Ever Confirmed|0 |1
--- Comment #1 from Ira Rosen <irar at il dot ibm.com> 2011-12-18 11:41:41 UTC ---
Caused by
r182388 | jakub | 2011-12-15 22:47:29 +0200 (Thu, 15 Dec 2011) | 27 lines
* tree-vectorizer.h (struct _stmt_vec_info): Remove pattern_def_stmt
field, add pattern_def_seq.
(STMT_VINFO_PATTERN_DEF_STMT): Remove.
(STMT_VINFO_PATTERN_DEF_SEQ): Define.
(NUM_PATTERNS): Bump to 10.
* tree-vect-loop.c (vect_determine_vectorization_factor,
vect_transform_loop): Adjust for pattern def changing from a single
gimple stmt to gimple_seq.
* tree-vect-stmts.c (vect_analyze_stmt, new_stmt_vec_info,
free_stmt_vec_info): Likewise.
* tree-vect-patterns.c (vect_recog_over_widening_pattern,
vect_recog_vector_vector_shift_pattern,
vect_recog_mixed_size_cond_pattern, adjust_bool_pattern_cast,
adjust_bool_pattern, vect_mark_pattern_stmts): Likewise.
(vect_recog_sdivmod_pow2_pattern): New function.
(vect_vect_recog_func_ptrs): Add it.
...
And probably PR 51580 is the same problem.
Looking at pr51015.c, vect_recog_vector_vector_shift_pattern is detected and a
new def stmt is created during the detection:
patt.23_33 = (long long unsigned int) D.2004_3;
The pattern detection fails later (on the vector type checks probably), but
this stmt remains a use stmt of D.2004_3 = i_25 + -2;. Therefore, we check
whether it's inside the loop, but get segfault while trying to check its not
existing BB.
Before the use of gimple_seq, this didn't happen, i.e., patt.23_33 = (long long
unsigned int) D.2004_3; wasn't a use of D.2004_3 = i_25 + -2;.
next prev parent reply other threads:[~2011-12-18 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 23:49 [Bug tree-optimization/51606] New: " dominiq at lps dot ens.fr
2011-12-18 12:02 ` irar at il dot ibm.com [this message]
2011-12-19 9:18 ` [Bug tree-optimization/51606] " jakub at gcc dot gnu.org
2011-12-19 9:24 ` jakub at gcc dot gnu.org
2011-12-19 14:23 ` jakub 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-51606-4-vb4fovGarG@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).