On Wed, 4 Jul 2001, Olin Lathrop wrote:

> I guess I'm really having a problem being clear today.  The four MOVLW lines
> above are *INDIVIDUAL* examples of a source line that could have produced
> the *SINGLE* MOVLW instruction I was using as an example.  Of course the
> same reasoning applies to ADDLW, IORLW, etc, etc, etc.

got it...

It'd really be hard for hex optimizer to distinguish whether or not one of the
MOVLW pertains to an address or not. I use this trick and all of the others
mentioned earlier in http://www.dattalo.com/technical/software/pic/pwm256.txt
. I'd be curious to see what a hex optimizer would do to it! (Actually, I'd
think an assembly level optimizer would have a time with it. [Really actually,
it gives me a headache everytime I look  at it!])

Conclusion: a general purpose hex optimizer is impossible. A general purpose
assembly optimizer would be extremely difficult (impossible) without special
assembler directives describing the programmer's intent. An assembly optimizer
that works off the output of a high-level compiler is possible, but tedious.

Scott

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body