From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27482 invoked by alias); 13 Sep 2013 09:50:38 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 27473 invoked by uid 89); 13 Sep 2013 09:50:38 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 13 Sep 2013 09:50:38 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r8D9oY2L017266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 13 Sep 2013 05:50:34 -0400 Received: from redhat.com (ovpn-116-91.ams2.redhat.com [10.36.116.91]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r8D9oUAB008978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 13 Sep 2013 05:50:32 -0400 Date: Fri, 13 Sep 2013 10:29:00 -0000 From: Marek Polacek To: "Joseph S. Myers" Cc: GCC Patches , Jakub Jelinek , Jason Merrill Subject: Re: [PATCH][ubsan] Add VLA bound instrumentation Message-ID: <20130913095030.GS23899@redhat.com> References: <20130912122655.GN23899@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2013-09/txt/msg01019.txt.bz2 On Thu, Sep 12, 2013 at 04:05:48PM +0000, Joseph S. Myers wrote: > cause stack overflow that doesn't get detected by the kernel. So maybe > ubsan should imply -fstack-check or similar. Well, I have a patch for that, but I no longer think that ubsan should imply -fstack-check, since e.g. int main (void) { int x = -1; int b[x - 4]; /* ... */ return 0; } segfaults at runtime on int b[x - 4]; line when -fstack-check is used (even without sanitizing), so we wouldn't give proper diagnostics for stmts following that line... Marek