[riot-notifications] [RIOT-OS/RIOT] sys: Added simple memory barrier API (#11438)

Marian Buschsieweke notifications at github.com
Wed Sep 4 14:38:09 CEST 2019


OK, I indeed cannot come up with an example that is not falling into the following cases:

1. A high level synchronization primitive can be used
2. The low level code should be wrapped into `irq_disable()` and `irq_restore()` anyway
3. Inline assembly is used, so adding appropriate [clobbers](https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html#Clobbers-and-Scratch-Registers) and (on out of order CPUs only) synchronization instructions would be equally fine.

Unless a practical example not falling in these categories pops up, this PR can be closed IMHO

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11438#issuecomment-527881772
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190904/9f9859fd/attachment.htm>


More information about the notifications mailing list