From owner-freebsd-current Mon Feb 5 18:39:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA19219 for current-outgoing; Mon, 5 Feb 1996 18:39:49 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA19207 for ; Mon, 5 Feb 1996 18:39:25 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id NAA15216; Tue, 6 Feb 1996 13:31:23 +1100 Date: Tue, 6 Feb 1996 13:31:23 +1100 From: Bruce Evans Message-Id: <199602060231.NAA15216@godzilla.zeta.org.au> To: davidg@Root.COM, leisner@sdsp.mc.xerox.com Subject: Re: make world with -fomit-frame-pointer Cc: freebsd-current@FreeBSD.ORG, jdli@linux.csie.nctu.edu.tw Sender: owner-current@FreeBSD.ORG Precedence: bulk >>I didn't read the message fully before I replied... >> >>-fomit-frame-pointer is something I've only seen in Linux. >> >>With -fomit-frame-pointer, you can't debug code...core dumps are >>meaningless...Please don't do it!! >> >>The only place where it may be useful is in the kernel. No, the debugging considerations are the same for the kernel, and the improvement from -fomit-frame-pointer is less than for average programs because the kernel does a lot of copying and waiting for cache misses, and has lots of assembler routines that don't use the frame pointer anyway. > We strip the symbol table from system utilities before installing them >(making debugging impossible), so why do you think -fomit-frame-pointer will >make things any worse in this respect? The utilities are easy to reconstruct (perhaps even with full debugging symbols) by recompiling the sources (provided the sources and the compiler, etc., haven't been changed since the binaries were installed). Same for the kernel. Bruce