FM / cpython

/opt/imh/python3.13/include/python3.13/cpython/

/opt/imh/python3.13/include/python3.13/cpython

Name	Size	Mode	Actions
abstract.h	3399	0644	edit dl rm
bytearrayobject.h	1163	0644	edit dl rm
bytesobject.h	1180	0644	edit dl rm
cellobject.h	1076	0644	edit dl rm
ceval.h	1115	0644	edit dl rm
classobject.h	2245	0644	edit dl rm
code.h	15207	0644	edit dl rm
compile.h	2121	0644	edit dl rm
complexobject.h	909	0644	edit dl rm
context.h	1837	0644	edit dl rm
critical_section.h	5588	0644	edit dl rm
descrobject.h	1593	0644	edit dl rm
dictobject.h	3870	0644	edit dl rm
fileobject.h	652	0644	edit dl rm
fileutils.h	232	0644	edit dl rm
floatobject.h	900	0644	edit dl rm
frameobject.h	1199	0644	edit dl rm
funcobject.h	7049	0644	edit dl rm
genobject.h	2997	0644	edit dl rm
import.h	725	0644	edit dl rm
initconfig.h	8197	0644	edit dl rm
listobject.h	1801	0644	edit dl rm
lock.h	1763	0644	edit dl rm
longintrepr.h	5119	0644	edit dl rm
longobject.h	5583	0644	edit dl rm
memoryobject.h	2223	0644	edit dl rm
methodobject.h	2276	0644	edit dl rm
modsupport.h	1042	0644	edit dl rm
monitoring.h	7704	0644	edit dl rm
object.h	19074	0644	edit dl rm
objimpl.h	3820	0644	edit dl rm
odictobject.h	1311	0644	edit dl rm
picklebufobject.h	848	0644	edit dl rm
pthread_stubs.h	3926	0644	edit dl rm
pyatomic.h	16506	0644	edit dl rm
pyatomic_gcc.h	19131	0644	edit dl rm
pyatomic_msc.h	29241	0644	edit dl rm
pyatomic_std.h	24336	0644	edit dl rm
pyctype.h	1387	0644	edit dl rm
pydebug.h	1413	0644	edit dl rm
pyerrors.h	2908	0644	edit dl rm
pyfpe.h	444	0644	edit dl rm
pyframe.h	1947	0644	edit dl rm
pyhash.h	1382	0644	edit dl rm
pylifecycle.h	2817	0644	edit dl rm
pymem.h	2843	0644	edit dl rm
pystate.h	9465	0644	edit dl rm
pystats.h	5434	0644	edit dl rm
pythonrun.h	4327	0644	edit dl rm
pythread.h	1510	0644	edit dl rm
pytime.h	707	0644	edit dl rm
setobject.h	2046	0644	edit dl rm
sysmodule.h	775	0644	edit dl rm
traceback.h	282	0644	edit dl rm
tracemalloc.h	823	0644	edit dl rm
tupleobject.h	1329	0644	edit dl rm
unicodeobject.h	25074	0644	edit dl rm
warnings.h	695	0644	edit dl rm
weakrefobject.h	2249	0644	edit dl rm

Edit: /opt/imh/python3.13/include/python3.13/cpython/critical_section.h (5588B)

#ifndef Py_CPYTHON_CRITICAL_SECTION_H
#  error "this header file must not be included directly"
#endif

// Python critical sections
//
// Conceptually, critical sections are a deadlock avoidance layer on top of
// per-object locks. These helpers, in combination with those locks, replace
// our usage of the global interpreter lock to provide thread-safety for
// otherwise thread-unsafe objects, such as dict.
//
// NOTE: These APIs are no-ops in non-free-threaded builds.
//
// Straightforward per-object locking could introduce deadlocks that were not
// present when running with the GIL. Threads may hold locks for multiple
// objects simultaneously because Python operations can nest. If threads were
// to acquire the same locks in different orders, they would deadlock.
//
// One way to avoid deadlocks is to allow threads to hold only the lock (or
// locks) for a single operation at a time (typically a single lock, but some
// operations involve two locks). When a thread begins a nested operation it
// could suspend the locks for any outer operation: before beginning the nested
// operation, the locks for the outer operation are released and when the
// nested operation completes, the locks for the outer operation are
// reacquired.
//
// To improve performance, this API uses a variation of the above scheme.
// Instead of immediately suspending locks any time a nested operation begins,
// locks are only suspended if the thread would block. This reduces the number
// of lock acquisitions and releases for nested operations, while still
// avoiding deadlocks.
//
// Additionally, the locks for any active operation are suspended around
// other potentially blocking operations, such as I/O. This is because the
// interaction between locks and blocking operations can lead to deadlocks in
// the same way as the interaction between multiple locks.
//
// Each thread's critical sections and their corresponding locks are tracked in
// a stack in `PyThreadState.critical_section`. When a thread calls
// `_PyThreadState_Detach()`, such as before a blocking I/O operation or when
// waiting to acquire a lock, the thread suspends all of its active critical
// sections, temporarily releasing the associated locks. When the thread calls
// `_PyThreadState_Attach()`, it resumes the top-most (i.e., most recent)
// critical section by reacquiring the associated lock or locks.  See
// `_PyCriticalSection_Resume()`.
//
// NOTE: Only the top-most critical section is guaranteed to be active.
// Operations that need to lock two objects at once must use
// `Py_BEGIN_CRITICAL_SECTION2()`. You *CANNOT* use nested critical sections
// to lock more than one object at once, because the inner critical section
// may  suspend the outer critical sections. This API does not provide a way
// to lock more than two objects at once (though it could be added later
// if actually needed).
//
// NOTE: Critical sections implicitly behave like reentrant locks because
// attempting to acquire the same lock will suspend any outer (earlier)
// critical sections. However, they are less efficient for this use case than
// purposefully designed reentrant locks.
//
// Example usage:
//  Py_BEGIN_CRITICAL_SECTION(op);
//  ...
//  Py_END_CRITICAL_SECTION();
//
// To lock two objects at once:
//  Py_BEGIN_CRITICAL_SECTION2(op1, op2);
//  ...
//  Py_END_CRITICAL_SECTION2();

typedef struct PyCriticalSection PyCriticalSection;
typedef struct PyCriticalSection2 PyCriticalSection2;

PyAPI_FUNC(void)
PyCriticalSection_Begin(PyCriticalSection *c, PyObject *op);

PyAPI_FUNC(void)
PyCriticalSection_End(PyCriticalSection *c);

PyAPI_FUNC(void)
PyCriticalSection2_Begin(PyCriticalSection2 *c, PyObject *a, PyObject *b);

PyAPI_FUNC(void)
PyCriticalSection2_End(PyCriticalSection2 *c);

#ifndef Py_GIL_DISABLED
# define Py_BEGIN_CRITICAL_SECTION(op)      \
    {
# define Py_END_CRITICAL_SECTION()          \
    }
# define Py_BEGIN_CRITICAL_SECTION2(a, b)   \
    {
# define Py_END_CRITICAL_SECTION2()         \
    }
#else /* !Py_GIL_DISABLED */

// NOTE: the contents of this struct are private and may change betweeen
// Python releases without a deprecation period.
struct PyCriticalSection {
    // Tagged pointer to an outer active critical section (or 0).
    uintptr_t _cs_prev;

// Mutex used to protect critical section
    PyMutex *_cs_mutex;
};

// A critical section protected by two mutexes. Use
// Py_BEGIN_CRITICAL_SECTION2 and Py_END_CRITICAL_SECTION2.
// NOTE: the contents of this struct are private and may change betweeen
// Python releases without a deprecation period.
struct PyCriticalSection2 {
    PyCriticalSection _cs_base;

PyMutex *_cs_mutex2;
};

# define Py_BEGIN_CRITICAL_SECTION(op)                                  \
    {                                                                   \
        PyCriticalSection _py_cs;                                       \
        PyCriticalSection_Begin(&_py_cs, _PyObject_CAST(op))

# define Py_END_CRITICAL_SECTION()                                      \
        PyCriticalSection_End(&_py_cs);                                 \
    }

# define Py_BEGIN_CRITICAL_SECTION2(a, b)                               \
    {                                                                   \
        PyCriticalSection2 _py_cs2;                                     \
        PyCriticalSection2_Begin(&_py_cs2, _PyObject_CAST(a), _PyObject_CAST(b))

# define Py_END_CRITICAL_SECTION2()                                     \
        PyCriticalSection2_End(&_py_cs2);                               \
    }

#endif

cmd: