From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26441 invoked by alias); 26 Sep 2006 17:42:57 -0000 Received: (qmail 26404 invoked by uid 48); 26 Sep 2006 17:42:47 -0000 Date: Tue, 26 Sep 2006 17:42:00 -0000 Message-ID: <20060926174247.26403.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/29185] inconsistent warning: deleting array In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gcc dot gnu dot org" 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 X-SW-Source: 2006-09/txt/msg02475.txt.bz2 List-Id: ------- Comment #4 from pinskia at gcc dot gnu dot org 2006-09-26 17:42 ------- (In reply to comment #3) > FWIW, I think it should be ill-formed with diagnostic required since the > behavior of the expression is always undefined. There are cases where this can show up in templates, someway or another. And then undefined behavior at runtime cannot be rejected because someone it does not need to be run as someone could do: if (0) delete a; -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29185