Pito, > In my newest float libs (1/2011) I am handling T this way - pushing > an poping it into r14.7. It worked with 4.0 and 4.2. Is it possible > you set the T in 4.0/4.2 within the inner interpreter only (it means > before entering a word) and now you set the T anytime when interrupt > fires- it means maybe during e.g. __SUBF12??
The redesign of the interrupt handling did not change _that_ part. It was always as it is now. The T-flag could be set anytime, and the inner intepreter checks it whenever it is entered. The timing has not changed here. What has changed is, that the controller itself is kept significantly longer in interrupt mode than in previous versions, since the reti instruction has been delayd. I cannot see anything here that could do harm to your code however. Even long running assembly snippets did work as before in my tests (they of course did not touch the T flag). Currently I'd that it was pure luck, that the error did not came up earlier.. strange enough.. Matthias ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Amforth-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amforth-devel
