From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22976 invoked by alias); 9 Mar 2007 14:29:35 -0000 Received: (qmail 22937 invoked by alias); 9 Mar 2007 14:29:24 -0000 Date: Fri, 09 Mar 2007 14:29:00 -0000 Message-ID: <20070309142924.22936.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug ada/26797] [4.3 regression] ACATS cxh1001 fails In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "kenner at vlsi1 dot ultra dot nyu dot edu" 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: 2007-03/txt/msg00737.txt.bz2 ------- Comment #36 from kenner at vlsi1 dot ultra dot nyu dot edu 2007-03-09 14:29 ------- Subject: Re: [4.3 regression] ACATS cxh1001 fails > I don't think this is a very serious problem. My understanding is > that the checks can be divided into two classes: normal checks and > validity checks. A normal check, such as when you do a type > conversion, does not use a V_C_E, it just does: > > if (y < new_type_lb || y > new_type_ub) > abort; > new_var = (new_type) y; Not clear. Consider the range check for a subscript on the LHS, for example. These issues are *very* subtle ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26797