> > > The stack use thing has to do with compiler optimisation. When an isr > is simple, it does not save all possible registers. But when the isr > is more complex, it does: call l__pic_stkpush
And doing this, it eats one precious stack level. Maybe there's an option to tell it to kind of "pragma inline" this l__pic_stkpush. > > Iirc correct, the compiler also makes procedures and functions > re-entrant when they are called both from level0 and isr-level. I can remember this, but I don't know "making func/prox re-entrant" means... Could you give some more words on this ? > > And about stack level use analysis: as I said, it would be nice if we > had an overview of the worst cases. The assembler file should be a > good base to do this and I thought about it quite a few times too (to > build in perl, that is). But I did not come to it yet. I'll give it > some thought (it is in my head now), but I have quite a lot of > projects going and my holiday ends tomorrow :( Not holidays for me :( Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
