From owner-freebsd-fs@FreeBSD.ORG Sun Apr 10 17:10:39 2005 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66E8616A4CE; Sun, 10 Apr 2005 17:10:39 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2513243D1F; Sun, 10 Apr 2005 17:10:39 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 8D52C5DA0; Sun, 10 Apr 2005 13:10:38 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85577-01; Sun, 10 Apr 2005 13:10:36 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-53-96.ny325.east.verizon.net [68.161.53.96]) by pi.codefab.com (Postfix) with ESMTP id 378895C85; Sun, 10 Apr 2005 13:10:36 -0400 (EDT) Message-ID: <42595E04.60705@mac.com> Date: Sun, 10 Apr 2005 13:10:28 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Ellard References: <200504100251.j3A2pLEH055107@sana.init-main.com> <20050410074009.N66651@bowser.eecs.harvard.edu> <1892195662.20050410140423@andric.com> <20050410082945.H66651@bowser.eecs.harvard.edu> In-Reply-To: <20050410082945.H66651@bowser.eecs.harvard.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com cc: freebsd-fs@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: smbfs bug introduced at smbfs_vnops.c:1.58 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Apr 2005 17:10:39 -0000 Daniel Ellard wrote: > On Sun, 10 Apr 2005, Dimitry Andric wrote: [ ... ] > At least the gcc folk now do detect this old chestnut: > > { > int a; > > a /= 0; > } > > which was used to provoke arguments in compiler > classes for many years. (Optimized, nothing happens. > Unoptimized, a division-by-zero error happens...) Great example. If the optimized code fails to generate a division-by-zero error here, the optimizer is buggy. (I won't quote Aho, Sethi, and Ullman again.... :-) -- -Chuck