Re: [Bug 126] Add support for attribute to mark data as volatile.

2014-06-02 Thread via D.gnu
On Monday, 2 June 2014 at 17:27:52 UTC, Johannes Pfau wrote: And of course without a type qualifier there can't be transitivity. The programmer always has to be careful to access struct members, array members, and other types 'connected' via indirection with peek/poke. I too think that a) vol

Re: [Bug 126] Add support for attribute to mark data as volatile.

2014-06-02 Thread Johannes Pfau via D.gnu
Am Sun, 01 Jun 2014 15:37:04 + schrieb "Timo Sintonen" : > I did not yet read the dip but here are some of my thoughts: > Thanks for joining this discussion, your input is very appreciated. > At the old days peripherals were simple. An uart might have a > control register, a status registe

[Bug 126] Add support for attribute to mark data as volatile.

2014-06-02 Thread via D.gnu
http://bugzilla.gdcproject.org/show_bug.cgi?id=126 --- Comment #12 from Johannes Pfau --- > I've created a "design discussion" around this debate on the D wiki: > http://wiki.dlang.org/Language_design_discussions#volatile Thanks, that's very useful. I did not even remember that we already had

[Bug 126] Add support for attribute to mark data as volatile.

2014-06-02 Thread via D.gnu
http://bugzilla.gdcproject.org/show_bug.cgi?id=126 --- Comment #11 from Mike --- Ok, clearly I have not fully understood shared semantics. > In future, the compiler would memoize the loop and go straight for the > assignment. > > mov$12, _D4test4globi(%rip) That would be very bad for my m