From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22676 invoked by alias); 5 Aug 2005 16:46:56 -0000 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 Received: (qmail 22626 invoked by uid 48); 5 Aug 2005 16:46:50 -0000 Date: Fri, 05 Aug 2005 16:46:00 -0000 Message-ID: <20050805164650.22625.qmail@sourceware.org> From: "dnovillo at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050724081306.23046.dank@kegel.com> References: <20050724081306.23046.dank@kegel.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/23046] [4.1 Regression] ICE in set_value_range, at tree-vrp.c:191 X-Bugzilla-Reason: CC X-SW-Source: 2005-08/txt/msg00571.txt.bz2 List-Id: ------- Additional Comments From dnovillo at gcc dot gnu dot org 2005-08-05 16:46 ------- (In reply to comment #14) > I patched fold to change if (FOO > TYPE_MAX) or if (FOO < TYPE_MIN) to if (0) > and this fixes the ice. I'll mail the patch when I get back from work tonight. That was my idea too, but it may not be as easy as it looks. See Roger's response to my message http://gcc.gnu.org/ml/gcc/2005-08/msg00169.html. The problem now is that VRP will either need to treat the range as VARYING or do some trickery to fold that conditional. For 4.1 it is probably easier to just set the range to VARYING. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |sayle at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23046