> 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 they are not reference outside of their own object file. Once you do this, GCC will sometimes warn that they are defined but never used -- these can generally be removed.
One difficulty with these methods is that condtional compilation will suggest that code is not used, when it may indeed still be used. In the end, you still need to use grep and read the code carefully. Cheers, Ben
