From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31410 invoked by alias); 22 Aug 2005 12:38:29 -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 31390 invoked by uid 48); 22 Aug 2005 12:38:25 -0000 Date: Mon, 22 Aug 2005 12:47:00 -0000 Message-ID: <20050822123825.31389.qmail@sourceware.org> From: "sebastian dot pop at cri dot ensmp dot fr" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20021017142600.8268.d.binderman@virgin.net> References: <20021017142600.8268.d.binderman@virgin.net> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c/8268] no compile time array index checking X-Bugzilla-Reason: CC X-SW-Source: 2005-08/txt/msg02527.txt.bz2 List-Id: ------- Additional Comments From sebastian dot pop at cri dot ensmp dot fr 2005-08-22 12:38 ------- (In reply to comment #14) > (In reply to comment #9) > > > If we really wanted to tackle this better a compile-time, we'd run a > > pass to look at all the ARRAY_REFs for those which have an out-of-range > > index. It wouldn't be terribly hard to stick one in just before we > > leave SSA form. > > I'll give this a try. > Have a look at tree-data-ref.c:analyze_array_indexes The warning can be implemented in this function. seb -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8268