From owner-freebsd-questions@FreeBSD.ORG Thu Sep 9 12:01:25 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D40A816A4CE for ; Thu, 9 Sep 2004 12:01:25 +0000 (GMT) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 606F843D5E for ; Thu, 9 Sep 2004 12:01:25 +0000 (GMT) (envelope-from cpghost@cordula.ws) Received: from bsdevil.farid-hajji.net (bsdevil [192.168.254.5]) by fw.farid-hajji.net (Postfix) with ESMTP id 6F8434AC85; Thu, 9 Sep 2004 13:57:51 +0200 (CEST) Date: Thu, 9 Sep 2004 14:02:21 +0200 From: cpghost@cordula.ws To: Geert Hendrickx Message-ID: <20040909120221.GA3115@bsdevil.farid-hajji.net> References: <20040909105232.GA51740@lori.mine.nu> <20040909114033.GA2039@bsdevil.farid-hajji.net> <20040909115122.GA52787@lori.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040909115122.GA52787@lori.mine.nu> User-Agent: Mutt/1.5.6i cc: freebsd-questions@freebsd.org Subject: Re: what is -DNOPROFILE ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2004 12:01:26 -0000 On Thu, Sep 09, 2004 at 01:51:22PM +0200, Geert Hendrickx wrote: > On Thu, Sep 09, 2004 at 01:40:33PM +0200, cpghost@cordula.ws wrote: > > On Thu, Sep 09, 2004 at 12:52:32PM +0200, Geert Hendrickx wrote: > > > Hi, > > > > > > I was wondering what this make.conf-flag is for: > > > > > > NOPROFILE= true # Avoid compiling profiled libraries > > > > > > What are "profiled" libraries? > > > > /usr/lib/lib*_p.{a,so} > > > > See gprof(1) > > So, if I understand it correctly from gprof(1), profiled libraries are > for measuring how much CPU time is spent in each suboutine? And, as a > regular user (not a developer or benchmarker), I don't need this and can > use -DNOPROFILE for not building profiled libraries? Yes, that's the whole point of NOPROFILE. Unless you are a developer yourself and want to optimize some code, there's little reason to keep those profiling libs around (or spend time building them). > I also understand these libraries are seperate from my "regular" > libraries? So, is there a drawback (other than increased compile time > for a make world) in building them? Or does it not matter? The libraries contain the same code as the regular (non-profiling) libraries, with a small addition within every function, to count the number of times a function is called and to measure the time. Linking normal apps against profiled libraries naturally slows them down (at run time), because the measuring code must be executed every time a library function is called. Therefore, normal applications are not linked against profiling libraries, and you can safely remove those libs from your system. It doesn't harm though to build them anyway, just in case you change your mind. Even on slow systems, building profiled libraries doesn't take that much longer. At the end of the day, it's your call. > GH Cheers, cpghost. -- Cordula's Web. http://www.cordula.ws/