Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Sep 1998 15:17:45 CDT
From:      Kent Vander Velden <graphix@iastate.edu>
To:        Mike Smith <mike@smith.net.au>
Cc:        freebsd-hackers@FreeBSD.ORG
Subject:   Re: Unused functions 
Message-ID:  <199809142017.PAA21067@du248-16.cc.iastate.edu>
In-Reply-To: Your message of "Mon, 14 Sep 1998 11:19:48 PDT." <199809141819.LAA00296@dingo.cdrom.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

In message <199809141819.LAA00296@dingo.cdrom.com>, Mike Smith writes:
>> > It allows the programmer and the C scoping rules to 
>> > work together to determine what should be associated and what need not.
>> 
>> Instead of the compiler merely calculating hamiltonian cycles in
>> the dependency graph to do dead code elimination.
>
>And if I happen to *want* all of the items in a given object (eg. I am 
>using a scripting language that supports primitive lookup via the 
>symbol table, or any other form of lazy runtime linking)?
>
>The current rules give the best of both worlds.   Don't fix what isn't 
>really broken.

  Is there any tool that can, as a post process following linking, remove
any unused code?  Strip just removes the debug symbols correct?  Perhaps
SuperStrip!  This would seem to be a nice feature since it could be run
by a person that is aware of the problems it may cause and has done the 
work to be certain no harm will happen.

---
Kent Vander Velden
kent@iastate.edu

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809142017.PAA21067>