Follow-up Comment #3, bug #50270 (project avr-libc):
The bug report is fine for a clear bug. However, for
something to be discussed first, it's a poor medium: if
the author of that text (who is on the developers
mailinglist) wants to reply something, he stands no chance
to add it to the bug report. If we discuss it on the list,
you'll miss the replies.
If you've got a suggestion for a better explanation and/or
wording of the phenomenon shown there, please tell us so.
The entire purpose of the text is to make users aware that
there are potential pitfalls in optimization which at least
currently cannot be controlled by any compiler statement.
_______________________________________________________
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
