AVR C Runtime Library - Bugs: bug #50270, Article "Problems with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #50270: Article "Problems with reordering code" misleading
Submitter: | None | ||
Submitted: | Thu 09 Feb 2017 10:07:34 PM UTC | ||
Category: | Documentation | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | Documentation |
Status: | None | Percent Complete: | 0% |
Assigned to: | None | Originator Email: | -email is unavailable- |
Open/Closed: | Open | Release: | 2.0.0 |
Fixed Release: | None |
( Jump to the original submission )
Sat 05 Sep 2020 01:26:03 PM UTC, comment #11: |
Marcin Godlewski <mrn_> |
Mon 16 Dec 2019 08:18:02 PM UTC, comment #10: Well, as already proposed 3 years ago, the below sentences:
|
Marcin Godlewski <mrn_> |
Sun 15 Dec 2019 01:59:06 PM UTC, comment #9: Just propose (best on the list where it can be discussed better) a new wording of that entry.
|
Joerg Wunsch <joerg_wunsch>![]() |
Sun 15 Dec 2019 11:46:05 AM UTC, comment #8: I've been involved in a couple of discussions about this page in the manual. I must admit that it annoys me a little that nothing has been done to update the page. It means people have been getting the same limited and slightly inaccurate information for years, when there are a number of solutions to the problem discussed.
|
David Brown <davidmbrown> |
Sun 15 Dec 2019 09:39:22 AM UTC, comment #7: Why this thread is dead? Is the auuthor of the article reachable so that he can share his opinion? |
Anonymous |
Fri 10 Feb 2017 02:46:46 PM UTC, comment #6: Yes, he can discuss it there, but he cannot append anything
|
Joerg Wunsch <joerg_wunsch>![]() |
Fri 10 Feb 2017 02:36:56 PM UTC, comment #5: 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? |
Marcin Godlewski <mrn_> |
Fri 10 Feb 2017 02:32:18 PM UTC, comment #4: 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.
|
Marcin Godlewski <mrn_> |
Fri 10 Feb 2017 02:06:14 PM UTC, comment #3: The bug report is fine for a clear bug. However, for
|
Joerg Wunsch <joerg_wunsch>![]() |
Fri 10 Feb 2017 11:06:23 AM UTC, comment #2: 1. I don't think I confuse volatile memory access with volatile asm statements.What is your point here?
|
Marcin Godlewski <mrn_> |
Fri 10 Feb 2017 09:03:53 AM UTC, comment #1: Your criticism seems to confuse volatile memory access with
|
Joerg Wunsch <joerg_wunsch>![]() |
Thu 09 Feb 2017 10:07:34 PM UTC, original submission:
The article available here:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
So there is a new wording proposal for 9 months now and not a single response. Looks like nobody is interested in updating the manual and fixing the issues.