How about hiring an "optimizing programmer". Better algorythms always beat
optimizing compilers/assemblers.

Bill :-)

At 11:00 AM 16/01/98 +0000, you wrote:
>TONY NIXON 54964 wrote about crunching code into limited ROM.
>
>Congratulations.
>
>I wish there were decent design tools for assembly programming.
>
>I don't mean just an assembler, but something that would
>- point out where registers can do double duty
>- point out potential stack overflows
>- manage code and data paging
>- etc.
>so that I can concentrate on the application and not the
>intricacies of the chip.
>
>Compilers do a lot of automated code generation and checking.
>It would be nice to have the same sophistication for assembly.
>
>For me, limited resources are just one challenge.
>I want to know if the code I write is flawed or not.
>Recalling product with duff code is more expensive than
>paying for slightly bigger PICs!
>