RE: [Sdcc-user] ISR problems with sdcc 2.4

[Gabriel M. <gab...@gm...>]

I've solved de puzzle, it was a misuse of the "critical" statement.
The external interrupt was been enabled inside a function with the critical 
statement, daah, so at the end of the function the compiler was restoring 
the interrupt enable to the previous state (off).
The statement was there to prevent a serial interrupt from breaking a 
function that should be atomic.

But that raises a question, why it was working on sdcc 2.30?

At 03:58 PM 1/12/2005, you wrote:

>I wouldn't be surprised if these delays are being optimised away. Declaring
>ciclos as volatile should put a stop to this.
>
>John.
>
>-----Original Message-----
>
>        ciclos = 40;
>        while (ciclos--);
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>Sdcc-user mailing list
>Sdc...@li...
>https://lists.sourceforge.net/lists/listinfo/sdcc-user