From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15296 invoked by alias); 16 Dec 2010 14:15:42 -0000 Received: (qmail 15288 invoked by uid 22791); 16 Dec 2010 14:15:42 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_TM X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Dec 2010 14:15:36 +0000 From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/46931] [4.6 Regression] Subversion id 167184 breaks building perlbench on power7 with debug X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: regression X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: CC Target Milestone Summary Severity Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 16 Dec 2010 14:15:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-12/txt/msg01964.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46931 Richard Guenther changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Target Milestone|--- |4.6.0 Summary|Subversion id 167184 breaks |[4.6 Regression] Subversion |building perlbench on |id 167184 breaks building |power7 with debug |perlbench on power7 with | |debug Severity|major |normal --- Comment #3 from Richard Guenther 2010-12-16 14:15:02 UTC --- (In reply to comment #2) > I think the actual problem was introduced in PR46172 commit, with the addition > of remove_dead_stmts_from_loop, as we now DCE what we have created during the > vectorization. > This function gsi_removes a stmt and then calls release_defs, which does > nothing though, because the SSA_NAME is name_registered_for_update_p, so the > release of it is deferred. But when delete_update_ssa attempts to release the > SSANAME afterwards, the bb for the stmt is already NULL and so gsi_for_stmt > fails. > > Not sure if there is something wrong on the remove_dead_stmts_from_loop side, > or if just releasing what has been created in the same pass has never been done > before and we should make insert_debug_temp_for_var_def do nothing if > gsi is NULL and def_stmt has NULL gimple_bb and the RHS isn't a constant. Hmm. We definitely shouldn't insert debug stmts for stmts that are no longer in the insn stream...