Memory barrier instructions:
http://infocenter.arm.com/help/topic/com.arm.doc.faqs/ka1404...
GCC example:
http://stackoverflow.com/questions/6751605/data-memory-barri...
As far as I understand, volatile doesn't give you the needed "barrier" semantics (what is not allowed to happen before or after, on the deep hardware level) if the code with "volatile" works, it can be just an accident.