4827e0cd5c
Memory accesses are posted in program order by virtue of the uncacheable memory attribute. Since GCC, by default, adds acquire and release semantics to volatile memory loads and stores, we need to use inline assembly to guarantee it. With inline assembly, we don't need volatile pointers anymore. Itanium does not support semaphore instructions to uncacheable memory. |
||
---|---|---|
.. | ||
acpica | ||
compile | ||
conf | ||
disasm | ||
ia32 | ||
ia64 | ||
include | ||
isa | ||
pci |