Man, have I walked a mile in your shoes.  I packed a 14000 to the
rafters, and when I needed that little bit more (and more, and more) I
hand packed in any way I could.  Alas, I am no use to you as I did not
look for any cool tools.  But I can add a cool feature that fits in with
your idea like a glove.  A dead RAM register finder.  I regularly jam
the RAM full, and hunt for unused RAM, to find out later that there were
a few two or three that I wasn't using and didn't see.  Shaa.  The
problem with my idea is that many RAM variables are simply equates, and
not oficially allocated until used in a piece of code, and only then
after first being loaded as a movlw.  (sometimes, IE FSR operations).
So the use of the RAM can be hidden down in the code a few steps.

Long story short, keep looking, and if you find or write something,
shout it out.

Chris Eddy, PE
Pioneer Microsystems, Inc.

Dave Reinagel wrote:

> Greetings,
>         Well, I have managed to completely fill a PIC14000 and
> am now looking through the listings trying to find dead code
> segments -- like floating point subroutines that are never
> called and can be commented out of the code to reclaim more
> space.
>         I can't believe I'm the only one who has hit this
> limit, and am wondering if someone has a utility that can
> scan either a PIC listing or the source code and identify
> any code segment that is never executed?  If not, perhaps
> I should try to write one.
>
> Dave Reiangel
> Auspex Systems, Inc
> daver@corp.auspex.com