From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14882 invoked by alias); 30 Sep 2005 13:24:46 -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 14806 invoked by uid 48); 30 Sep 2005 13:24:32 -0000 Date: Fri, 30 Sep 2005 13:24:00 -0000 Message-ID: <20050930132432.14805.qmail@sourceware.org> From: "jakub at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20050828194312.23604.pinskia@gcc.gnu.org> References: <20050828194312.23604.pinskia@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/23604] [4.1 Regression] wrong code due to VRP X-Bugzilla-Reason: CC X-SW-Source: 2005-09/txt/msg03773.txt.bz2 List-Id: ------- Additional Comments From jakub at gcc dot gnu dot org 2005-09-30 13:24 ------- Jim's patch certainly worked for me. But the question is if we can do more. If not anti-range and limit_vr->min == limit_vr->max, then we at least can create anti-range from TYPE_MIN_VALUE to TYPE_MAX_VALUE. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23604