From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19373 invoked by alias); 28 Mar 2008 22:59:19 -0000 Received: (qmail 18892 invoked by uid 48); 28 Mar 2008 22:58:35 -0000 Date: Fri, 28 Mar 2008 22:59:00 -0000 Message-ID: <20080328225835.18891.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/30911] VRP fails to eliminate range checks in Ada code In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rguenth at gcc dot gnu dot org" 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: 2008-03/txt/msg02332.txt.bz2 ------- Comment #52 from rguenth at gcc dot gnu dot org 2008-03-28 22:58 ------- I'm now testing a variant of the patch that fixes fold_sign_changed_comparison and just initializes incoming parameter value-ranges based on their types. This seems to do the same range-check removals and looks like an overall sane change. I assume when inlining we will see the range check that assures the function parameters are in-range, right? So even for that case we should be able to do the same simplifications. Can you cook up a testcase that shows this case? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30911