From owner-cvs-src@FreeBSD.ORG Wed Jun 13 08:48:01 2007 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F2BCC16A46B; Wed, 13 Jun 2007 08:48:00 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail19.syd.optusnet.com.au (mail19.syd.optusnet.com.au [211.29.132.200]) by mx1.freebsd.org (Postfix) with ESMTP id 6F5C613C48C; Wed, 13 Jun 2007 08:48:00 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from c220-239-235-248.carlnfd3.nsw.optusnet.com.au (c220-239-235-248.carlnfd3.nsw.optusnet.com.au [220.239.235.248]) by mail19.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l5D8lt6W022096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Jun 2007 18:47:57 +1000 Date: Wed, 13 Jun 2007 18:47:58 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Kip Macy In-Reply-To: Message-ID: <20070613184656.N25269@delplex.bde.org> References: <200706130617.l5D6HncF038605@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Bruce Evans , cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/libkern mcount.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2007 08:48:01 -0000 On Tue, 12 Jun 2007, Kip Macy wrote: > On 6/12/07, Bruce Evans wrote: >> bde 2007-06-13 06:17:48 UTC >> >> FreeBSD src repository >> >> Modified files: >> sys/libkern mcount.c >> Log: >> Unbreak high resolution profiling a little: use dummy asms to prevent >> timing loops being optimized away. >> >> Once apon a time, gcc promised not to optimize away timing loops, but >> gcc started optimizing away the call to a null function in the timing >> loop here some time between gcc-3.3.3 and gcc-3.4.6, and it started >> optimizing away the timing loop itself some time between gcc-3.4.6 >> and gcc-4.2. > > Will this fix the hang on boot that I saw earlier today? No. It's unlikely that you even configure profiling. Bruce