[issue31119] Signal tripped flags need memory barriers

Armin Rigo report at bugs.python.org
Fri Aug 4 16:30:33 EDT 2017


Armin Rigo added the comment:

For reference, no, it can't happen on x86 or x86-64.  I've found that this simplified model actually works for reasoning about ordering at the hardware level: think about each core as a cache-less machine that always *reads* from the central RAM, but that has a delay for writes---i.e. writes issued by a core are queued internally, and actually sent to the central RAM at some unspecified later time, but in order.

(Of course that model fails on other machines like ARM.)

----------
nosy: +arigo

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue31119>
_______________________________________


More information about the Python-bugs-list mailing list