On Sat, Dec 13, 2003 at 09:34:25AM -0600, Bill Knight wrote:
> Yes, that is one failing of the tasker. It has no concept of an idle task
> making it difficult to easily implement LPM when there is nothing to do.
>
> Well what can you expect? It was originally written to provide threading
> on a PC running DOS well over 10 years ago. Since then, it has been ported
> to close to a dozen different architectures and compilers.
I like it. It's quite simple. But another question, is it enough to push
just R4 to R11? The mspgcc users manual says that R12 to R15 are "clobbered"
registers. Can I use R12 to R15 for my own special purpose?
How do you determine the stack space needed for each task? Can gcc list a
function call tree (show what function is calling what function), and the
stack space that is needed by each function? With no recursive calls
this should be possible at compile time. Add the space needed for the
interrupts and you have the worst case stack size.
Matthias
