Yes, there does not appear to be any problem with direct calls, so T2 should be off the hook as long as people stay away from function pointers.
The bug seems to have something to do with pointer arithmetic confusing gcc. I don't imagine that the TinyOS 1.x scheduler ever triggers this or people would have noticed. The bug is there in gcc 4.1.0, I filed a bug report with the gcc people, maybe they'll fix it. John > I'll demonstrate my lack of knowledge of avr codegen and ask a clueless > question: Does this ever happen in standard calls, or is it only when you load > an address from memory? That is, if you follow the TinyOS guideline of not > using function pointers, will you ever encounter this? I assume that 1.x can > tickle the bug due to the task queue, but 2.x uses static binding, so would be > safe, right? > > Phil > _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
