This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients jyasskin, neologix, pitrou, vstinner
Date 2017-06-29.20:25:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498767923.04.0.739660006116.issue30808@psf.upfronthosting.co.za>
In-reply-to
Content
Look at the PR :-) That's what we used.  But, while sig_atomic_t guarantees that accesses are atomic, it doesn't enforce a memory order.  So the CPU (depending on the architecture) is free to reorder writes.
History
Date User Action Args
2017-06-29 20:25:23pitrousetrecipients: + pitrou, vstinner, jyasskin, neologix
2017-06-29 20:25:23pitrousetmessageid: <1498767923.04.0.739660006116.issue30808@psf.upfronthosting.co.za>
2017-06-29 20:25:23pitroulinkissue30808 messages
2017-06-29 20:25:22pitroucreate