From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22652 invoked by alias); 2 Nov 2010 13:28:21 -0000 Received: (qmail 22634 invoked by uid 22791); 2 Nov 2010 13:28:20 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,MISSING_MID 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; Tue, 02 Nov 2010 13:28:16 +0000 From: "irar at il dot ibm.com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46172] [4.3/4.4/4.5/4.6 Regression] ICE: in expand_widen_pattern_expr, at optabs.c:522 with -ftree-vectorize -fno-tree-dce X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: irar at il dot ibm.com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.3.6 X-Bugzilla-Changed-Fields: 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: Tue, 02 Nov 2010 13:28: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-11/txt/msg00114.txt.bz2 Message-ID: <20101102132800.XgJB52zkFWY--NrA2zF675Onnf611mmvMuO-BFl0I6c@z> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46172 --- Comment #5 from Ira Rosen 2010-11-02 13:28:14 UTC --- (In reply to comment #4) > Ah, if this is in dead code created by vectorizer that really shouldn't be ever > expanded, Yes, in this case it's dead code created by the vectorizer that shouldn't be expanded. But there is also always scalar code that we do not remove except for stores. > then either we need to arrange for DCE to be performed after > vectorizer even if flag_tree_vectorize && !flag_tree_dce (e.g. by using a > different pass structure e.g. instead of pass_dce_loop and use a different gate > for it right after vectorizer), Yes, this is what I meant. > or vectorizer shouldn't create garbage. > > -fno-tree-dce is sometimes useful for compiler testing to write testcases e.g. > for expansion and RTL passes bugs, so making it unconditional is not a good > idea.