From owner-cvs-all@FreeBSD.ORG Sat Jan 22 02:08:04 2005 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3CC316A4CE; Sat, 22 Jan 2005 02:08:04 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47D9743D39; Sat, 22 Jan 2005 02:08:04 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.13.1) with ESMTP id j0M27dng035318; Fri, 21 Jan 2005 21:07:39 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.13.1/Submit) id j0M27dOW035317; Fri, 21 Jan 2005 21:07:39 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Fri, 21 Jan 2005 21:07:39 -0500 From: David Schultz To: "David E. O'Brien" Message-ID: <20050122020739.GA35293@VARK.MIT.EDU> Mail-Followup-To: "David E. O'Brien" , src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG References: <200501220058.j0M0wYDe021527@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501220058.j0M0wYDe021527@repoman.freebsd.org> cc: cvs-src@FreeBSD.ORG cc: src-committers@FreeBSD.ORG cc: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/conf kern.pre.mk X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 02:08:04 -0000 On Sat, Jan 22, 2005, David E. O'Brien wrote: > obrien 2005-01-22 00:58:34 UTC > > FreeBSD src repository > > Modified files: > sys/conf kern.pre.mk > Log: > Embellish rev 1.61. If we're not building a debug kernel, use -O2 as before. With this change, problems (e.g. pointer aliasing bugs) that occur with non-DEBUG production kernels may mysteriously go away on DEBUG kernels, making the problems harder to diagnose. If we are going to keep things like this, perhaps it would be a good idea to carefully document this feature, along with the appropriate way to work around it and go about debugging. Thoughts?