answering myself: Harald Kipp wrote: > In fact I couldn't find a single memory clobber in avr-libc 1.6.2. > > Did I overlook soemthing? Any comments are most welcome.
Meanwhile I found an old thread dated back in Dec 2005. As it turns out, the variables, that need to be protected from interrupt access, must be declared volatile anyway, which in turn would stop the compiler from re-arranging the assignment. I still have the feeling that compiler optimization may interfere with inlined asm statements, but not in this specific case. Sorry for the noise, Harald _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
