Lpc2000

At 02:37 AM 2/19/04 +1100, you wrote:
>In the meantime I learnt the hard way :-)
>Yes, I have run into a problem where the GCC based part screws up
>the context, reducing optimisation fixed it.
>This threw me out for quite some time. grrrr :-(

I gave up on using C directly for interrupts long ago.  I've run into too 
many compiler failures where they either produced wrong code or were so 
pessimistic they increased the overhead by several multiples.  I'll often 
do my own prolog and epilog and then call the C myself.  If nothing else 
it's a good way to learn the ins & outs of the processor.  Just as often 
(probably more often) I'm using an interrupt for performance reasons and I 
want to minimize the context switch overhead and/or access chip features 
that are not (easily) accessible in C (particularly standard C).  In that 
case asm can sometimes be an order of magnitude faster.

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III