mirror of
https://github.com/python/cpython.git
synced 2025-10-15 03:10:29 +00:00
gh-115999: Add free-threaded specialization for STORE_SUBSCR
(#127169)
The specialization only depends on the type, so no special thread-safety considerations there. STORE_SUBSCR_LIST_INT needs to lock the list before modifying it. `_PyDict_SetItem_Take2` already internally locks the dictionary using a critical section.
This commit is contained in:
parent
f0d3f10c43
commit
71ede1142d
5 changed files with 109 additions and 70 deletions
|
@ -284,6 +284,29 @@ GETITEM(PyObject *v, Py_ssize_t i) {
|
|||
}
|
||||
|
||||
|
||||
// Try to lock an object in the free threading build, if it's not already
|
||||
// locked. Use with a DEOPT_IF() to deopt if the object is already locked.
|
||||
// These are no-ops in the default GIL build. The general pattern is:
|
||||
//
|
||||
// DEOPT_IF(!LOCK_OBJECT(op));
|
||||
// if (/* condition fails */) {
|
||||
// UNLOCK_OBJECT(op);
|
||||
// DEOPT_IF(true);
|
||||
// }
|
||||
// ...
|
||||
// UNLOCK_OBJECT(op);
|
||||
//
|
||||
// NOTE: The object must be unlocked on every exit code path and you should
|
||||
// avoid any potentially escaping calls (like PyStackRef_CLOSE) while the
|
||||
// object is locked.
|
||||
#ifdef Py_GIL_DISABLED
|
||||
# define LOCK_OBJECT(op) PyMutex_LockFast(&(_PyObject_CAST(op))->ob_mutex._bits)
|
||||
# define UNLOCK_OBJECT(op) PyMutex_Unlock(&(_PyObject_CAST(op))->ob_mutex)
|
||||
#else
|
||||
# define LOCK_OBJECT(op) (1)
|
||||
# define UNLOCK_OBJECT(op) ((void)0)
|
||||
#endif
|
||||
|
||||
#define GLOBALS() frame->f_globals
|
||||
#define BUILTINS() frame->f_builtins
|
||||
#define LOCALS() frame->f_locals
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue