summaryrefslogtreecommitdiff
path: root/c/misc_thread_common.h
Commit message (Collapse)AuthorAgeFilesLines
* oops thanks BlastRock NA for spotting thisArmin Rigo2019-01-311-1/+2
|
* Issue #362Armin Rigo2019-01-281-67/+226
| | | | | | | Add "thread canary" objects which are deallocated if the PyThreadState is explicitly deallocated by CPython. If the thread shuts down first, then instead the canary is inserted in a zombie list. In that case, we clear and delete properly the PyThreadState at the next occasion.
* msvc supportArmin Rigo2018-08-081-1/+3
|
* Issue #362Armin Rigo2018-03-151-1/+69
| | | | | | Py_Finalize() will free any threadstate around, so in that case we must not call PyThreadState_Delete() any more on them from cffi_thread_shutdown().
* Push and pull at the messArmin Rigo2017-10-051-22/+24
|
* More fun with _PyThreadState_Current becoming undefined in 3.7.Armin Rigo2017-09-271-9/+17
|
* Pull request #79 by xwangArmin Rigo2017-03-281-6/+1
| | | | | We can actually call PyThreadState_Delete(), which works without the GIL and seems to pass the same tests.
* Change get_current_ts to always use _Py_atomic_load_relaxed when available.Michael McGee2016-04-051-1/+1
|
* Remove this field if it's not usedArmin Rigo2016-01-031-1/+3
|
* Generalize the code for 'local_thread_state' and move it toArmin Rigo2016-01-031-0/+134
misc_thread_common.h.