>to the same RAM location based on their usage.  For example, sub1 uses a
>byte variable called Byte1, and sub2 uses a byte var called Byte2.  The
>compiler analyzes the subroutine call structure, and if sub1 never calls
>sub2 (even indirectly) and sub2 never calls sub1, then Byte1 and Byte2 will
>use the same physical RAM location.

That's great, as long as they're both auto variables.  If one is static,
you've got trouble.


I hacked together a simple dead code finder today.  It seems to work, as
long as you don't use computed gotos, pclath, or more than 2k of program.
I'm kinda stuck on the pclath--I couldn't think of any easy way to
determine it's value without simulating most of the program.

I certainly wouldn't just let it loose on a hex file, but it's kinda cool
to look through the list files and see what it picks out as unreachable.


newell