>Ahh, so. "Deterministic timing" is whatever the compiler **gives** you,
>whether it gives 10 cycles to code a loop, or 25 - whether a C instruction
>gets coded into 1 cycle or 8. Slowly it's coming across.


Maybe the definition of "determinism" is the problem.  It simply means that I
know ahead of time how long something takes, whether 5 or 50 cycles (or 6/51 in
certain cases).

It means nothing about the identical timing of some routine(s).

If I need to make something ALWAYS take the same amount of time, I adjust the
generated code so it does.  That is a special case of determinism.

Deterministic behavior means it will always come to a (correct) answer.  It can
also have time limitations added to it if you like.

Andy

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu