public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/50133] [4.7 Regression] ICE: SIGSEGV in vect_finish_stmt_generation (gimple.h:4821) with -ftree-vectorize -fno-tree-loop-im Date: Sun, 21 Aug 2011 18:09:00 -0000 [thread overview] Message-ID: <bug-50133-4-xNz0Rpc4gA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50133-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50133 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-08-21 17:43:08 UTC --- Insert before gsi_end_p should be fine, you just can't copy locus from it in that case. So you could as well do something like: si = *gsi; if (gsi_end_p (si)) { gsi_prev (&si); gsi_prev_nondebug (&si); } else if (is_gimple_debug (gsi_stmt (si))) { gsi_next_nondebug (&si); gcc_assert (!gsi_end_p (si)); } where the first gsi_prev would move from the end to the newly inserted stmt and gsi_prev_nondebug to the previous stmt (skipping any debug stmts). This wouldn't work when inserting into a completely empty bb, but does the vectorizer ever do something like that?
next prev parent reply other threads:[~2011-08-21 17:43 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-19 21:58 [Bug tree-optimization/50133] New: " zsojka at seznam dot cz 2011-08-19 23:05 ` [Bug tree-optimization/50133] " rguenth at gcc dot gnu.org 2011-08-21 7:56 ` irar at il dot ibm.com 2011-08-21 9:17 ` irar at il dot ibm.com 2011-08-21 18:09 ` jakub at gcc dot gnu.org [this message] 2011-08-22 9:40 ` jakub at gcc dot gnu.org 2011-08-22 10:28 ` jakub at gcc dot gnu.org 2011-08-22 15:12 ` jakub at gcc dot gnu.org 2011-08-23 9:58 ` 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-50133-4-xNz0Rpc4gA@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).