[riot-notifications] [RIOT-OS/RIOT] core: fix c11 atomic definitions (fix gcc9 compilation) (#11514)
notifications at github.com
Wed May 15 13:18:35 CEST 2019
> whether casting off the pointer's volatile has any effect within an irq_disable()/irq_restore() pair
Oh, I missed that. Citing from https://en.cppreference.com/w/c/language/volatile:
> Any attempt to read or write to an object whose type is volatile-qualified through a non-volatile lvalue results in undefined behavior
Even though our current compilers seem to not interpret this as an "optimization opportunity" (yet), we might better change this. (Btw: We should check the use of `volatile` in the scheduler/threading part of RIOT as well in this context.)
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications