Follow-up Comment #2, bug #50270 (project avr-libc):
1. I don't think I confuse volatile memory access with volatile asm
statements.What is your point here?
2. I've already discussed the problem in the list avr-gcc-l...@nongnu.org and
I got feedback to submit a bug report. Please search for a topic
Avr-libc-user-manual: "Problems with reordering code".
3. I don't say the article is written without a reason. But it simply seems to
give inaccurate conclusions.
4. I also don't understand your last point. What blunt statement did I give? I
simply explained why I think the conclusions in article are wrong. I
understand that something may "look much more reasonable" to you, but such
comments doesn't bring any value in the discussion. I hope to have a
content-related discussion.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?50270>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
