hi kyle, i've tried the -debug option. works fine, except it does not include stack usage in a ISR. at least this is what I understood.
the problem here is also there's a weird stack usage when context is a ISR and procedure also access some inteerupt related information. this is at least what I understand. I'll provide more testing programs if you want. finally, I don't know if you noticed that, but compiler gives a nasty core dump when a line in serial-hw-write is commented (see previous post). i can provide more test if you want. let me know ! cheers, seb 2009/1/5, Kyle <[email protected]>: > > Greetings, > > On Sun, 4 Jan 2009 20:13:39 +0100, Joep Suijs wrote >> >> And about stack level use analysis: as I said, it would be nice if we >> had an overview of the worst cases. > > Compile with the '-debug' flag and the assembly output includes the deepest > stacklevel detected for each instruction. > > --kyle > > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
