From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-346111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30211 invoked by alias); 3 Feb 2011 22:25:09 -0000
Received: (qmail 30176 invoked by uid 22791); 3 Feb 2011 22:25:09 -0000
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
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, 03 Feb 2011 22:25:05 +0000
From: "asharif at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47447] [4.3/4.4 Regression] "Unable to coalesce ssa_names <x> and <y>" ICE in tree-ssa-coalesce.c when -O3 is used
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: asharif at gcc dot gnu.org
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:
Message-ID: <bug-47447-4-JMBMwYwl1U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47447-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47447-4@http.gcc.gnu.org/bugzilla/>
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, 03 Feb 2011 22:25:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-02/txt/msg00577.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47447

--- Comment #6 from asharif at gcc dot gnu.org 2011-02-03 22:25:01 UTC ---
What happens is tree vectorization introduces code in the preheader to check
for the loop iterations at runtime. The expression holding the number of
iterations may contain ssa names that are abnormal. This may extend their live
range (that is what happens in this testcase) and make them conflict with other
abnormal names.

That leads to an ICE.

I wonder what the other passes do that hoist such code effectively extending
the live ranges of abnormal ssa names.