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 jdemeyer
Recipients Rhamphoryncus, georg.brandl, gustavo, gvanrossum, jdemeyer
Date 2019-04-10.05:56:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1554875772.42.0.33719615902.issue1583@roundup.psfhosted.org>
In-reply-to
Content
> Unpacking the int would mean having one sig_atomic_t for 'invalid', using that instead of INVALID_FD, plus an array of sig_atomic_t for the fd itself.  Every time you want to change the fd you first set the 'invalid' flag, then the individual bytes, then clear 'invalid'.

I'm not sure that this is thread-safe as processors can reorder instructions, so there is no guarantee that memory is written in the expected order. That's one of the problems that C11/C++11 atomics solve.
History
Date User Action Args
2019-04-10 05:56:12jdemeyersetrecipients: + jdemeyer, gvanrossum, georg.brandl, Rhamphoryncus, gustavo
2019-04-10 05:56:12jdemeyersetmessageid: <1554875772.42.0.33719615902.issue1583@roundup.psfhosted.org>
2019-04-10 05:56:12jdemeyerlinkissue1583 messages
2019-04-10 05:56:12jdemeyercreate