[avr-libc-dev] [bug #50270] Article "Problems with reordering code" misleading

Follow-up Comment #1, bug #50270 (project avr-libc): Your criticism seems to confuse volatile memory access with volatile asm statements. Given the matter is known to be tricky, it would have been better to subscribe to the avr-libc mailing list, and discuss the wording there with the other devel

[avr-libc-dev] [bug #50270] Article "Problems with reordering code" misleading

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 top

[avr-libc-dev] [bug #50270] Article "Problems with reordering code" misleading

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 repor

[avr-libc-dev] [bug #50270] Article "Problems with reordering code" misleading

Follow-up Comment #4, bug #50270 (project avr-libc): I'm sorry if I have chosen the wrong medium. I tried to point out the problem on a mailing list already, but hardly anyone was interested to discuss it. I may have chosen the wrong mailing list, but this was the only one I found. But I still do

[avr-libc-dev] [bug #50270] Article "Problems with reordering code" misleading

Follow-up Comment #5, bug #50270 (project avr-libc): As I can see, all the discussion is automatically sent to avr-libc-dev@nongnu.org, so I guess the author of the text can see the discussion and join it. Isn't this right? ___ Reply to thi

Re: [avr-libc-dev] Support for AtMega328pb

As Pitchumani Sivanupandi wrote: > >Can Microchip at least grant us permission to back-integrate their > >header files here? I assume they still have the usual 3-clause > >BSD-like copyright statement, so it wouldn't be a legal issue to have > >them here. > I think there is no change in licensin

[avr-libc-dev] [bug #50270] Article "Problems with reordering code" misleading

Follow-up Comment #6, bug #50270 (project avr-libc): Yes, he can discuss it there, but he cannot append anything to the bug report itself. ___ Reply to this item at: _