From owner-freebsd-stable  Mon Oct 21  9:19: 9 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F419D37B401
	for <stable@FreeBSD.ORG>; Mon, 21 Oct 2002 09:19:08 -0700 (PDT)
Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6374F43E4A
	for <stable@FreeBSD.ORG>; Mon, 21 Oct 2002 09:19:03 -0700 (PDT)
	(envelope-from dschultz@uclink.Berkeley.EDU)
Received: from HAL9000.homeunix.com (localhost [127.0.0.1])
	by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9LGJ24D000540;
	Mon, 21 Oct 2002 09:19:02 -0700 (PDT)
	(envelope-from dschultz@uclink.Berkeley.EDU)
Received: (from das@localhost)
	by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9LGJ2re000539;
	Mon, 21 Oct 2002 09:19:02 -0700 (PDT)
	(envelope-from dschultz@uclink.Berkeley.EDU)
Date: Mon, 21 Oct 2002 09:19:02 -0700
From: David Schultz <dschultz@uclink.Berkeley.EDU>
To: Charles Swiger <cswiger@mac.com>
Cc: stable@FreeBSD.ORG
Subject: Re: 4.7-RELEASE crash [file system]
Message-ID: <20021021161902.GA396@HAL9000.homeunix.com>
Mail-Followup-To: Charles Swiger <cswiger@mac.com>,
	stable@FreeBSD.ORG
References: <20021019130404.A25131-100000@edge.foundation.invalid> <001901c27798$d033df70$0301a8c0@prime> <3DB2399F.3060900@zbzoom.net> <003a01c27849$6367d4d0$0301a8c0@prime>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <003a01c27849$6367d4d0$0301a8c0@prime>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

Thus spake Charles Swiger <cswiger@mac.com>:
> PS: Arguably, people should be building with "-g -O" all of the time, even
> in production.  GCC tends to generate the most reliable code for that
> combination of options, as those are exercised the most frequently.

GCC specifically does *not* generate code that is any more or less
reliable when you use -g.  The GCC folks are fairly picky about
that rule.  As for optimization, I've never been bitten by any
bugs in either -O0 or -O, but in theory -O0 would save you from
any bugs in the optimizer.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message