From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29249 invoked by alias); 10 Apr 2006 10:24:46 -0000 Received: (qmail 29212 invoked by alias); 10 Apr 2006 10:24:41 -0000 Date: Mon, 10 Apr 2006 10:24:00 -0000 Message-ID: <20060410102441.29211.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/23855] loop header should also be pulled out of the inner loop too In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rakdver at atrey dot karlin dot mff dot cuni dot cz" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-04/txt/msg00767.txt.bz2 List-Id: ------- Comment #18 from rakdver at atrey dot karlin dot mff dot cuni dot cz 2006-04-10 10:24 ------- Subject: Re: loop header should also be pulled out of the inner loop too > > > actually, thinking about it again, it should suffice to teach > > > invariant_without_guard_p about invariant memory loads, and this should just > > > work. > > > > It basically does, the only other problem is that we are not able to determine > > that the outer loop is not infinite. > > It that because we don't recognize the condition of the loop header? the problem is that we use # of iterations analysis, and it tries to fully instantiate the scalar evolutions, which is impossible for *je. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23855