> Does anyone know of any tool that can help identify fallow routines?
It's not a complete solution, but it is one tool that will contribute
to your effort: Andrew Tridgell has written a script called
`findstatic.pl' (Google for it) that will tell you which functions can
be made static because the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, May 05, 2006 at 06:20:19AM -0500, John Love-Jensen wrote:
> One of my project's general on-going tasks is to eliminate dead code.
> Sort of following the Extreme Programming principle.
If you're doing XP then you also have a test suite that co
Any suggestions, pointers or recommendations for tools, tips and/or
techniques would be appreciated.
A couple of different ways come to mind:
a) there's the binutils -ffunction-sections -Wl,-gc-sections approach
where every function is put into it's own section and the total is
then garbag
