summaryrefslogtreecommitdiffstats
path: root/Include/cpython
Commit message (Collapse)AuthorAgeFilesLines
* gh-142217: Deprecate the private _Py_Identifier C API (#142221)Victor Stinner2025-12-123-3/+3
| | | | | | | Deprecate functions: * _PyObject_CallMethodId() * _PyObject_GetAttrId() * _PyUnicode_FromId()
* gh-142534: Avoid TSan warnings in dictobject.c (gh-142544)Sam Gross2025-12-111-0/+11
| | | | | | There are places we use "relaxed" loads where C11 requires "consume" or stronger. Unfortunately, compilers don't really implement "consume" so fake it for our use in a way that avoids upsetting TSan.
* GH-135379: Top of stack caching for the JIT. (GH-135465)Mark Shannon2025-12-111-1/+1
| | | | Uses three registers to cache values at the top of the evaluation stack This significantly reduces memory traffic for smaller, more common uops.
* gh-141976: Protect against non-progressing specializations in tracing JIT ↵Ken Jin2025-12-101-0/+1
| | | | (GH-141989)
* gh-141732: Fix `ExceptionGroup` repr changing when original exception ↵dr-carlos2025-12-071-0/+1
| | | | sequence is mutated (#141736)
* gh-138122: Don't sample partial frame chains (#141912)Pablo Galindo Salgado2025-12-071-0/+7
|
* gh-138122: Implement frame caching in RemoteUnwinder to reduce memory reads ↵Pablo Galindo Salgado2025-12-061-0/+2
| | | | | | | | | | | (#142137) This PR implements frame caching in the RemoteUnwinder class to significantly reduce memory reads when profiling remote processes with deep call stacks. When cache_frames=True, the unwinder stores the frame chain from each sample and reuses unchanged portions in subsequent samples. Since most profiling samples capture similar call stacks (especially the parent frames), this optimization avoids repeatedly reading the same frame data from the target process. The implementation adds a last_profiled_frame field to the thread state that tracks where the previous sample stopped. On the next sample, if the current frame chain reaches this marker, the cached frames from that point onward are reused instead of being re-read from remote memory. The sampling profiler now enables frame caching by default.
* gh-130396: Remove _Py_ReachedRecursionLimitWithMargin() function (#141951)Victor Stinner2025-11-271-2/+0
| | | Move the private function to the internal C API (pycore_ceval.h).
* gh-141726: Add PyDict_SetDefaultRef() to the Stable ABI (#141727)da-woods2025-11-191-10/+0
| | | Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
* gh-141070: Add PyUnstable_Object_Dump() function (#141072)Victor Stinner2025-11-181-5/+9
| | | | | | | | | | * Promote _PyObject_Dump() as a public function. * Keep _PyObject_Dump() alias to PyUnstable_Object_Dump() for backward compatibility. * Replace _PyObject_Dump() with PyUnstable_Object_Dump(). Co-authored-by: Peter Bierma <zintensitydev@gmail.com> Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Petr Viktorin <encukou@gmail.com>
* gh-135953: Add GIL contention markers to sampling profiler Gecko format ↵Pablo Galindo Salgado2025-11-171-0/+3
| | | | | | (#139485) This commit enhances the Gecko format reporter in the sampling profiler to include markers for GIL acquisition events.
* fix memory order of `_Py_atomic_store_uint_release` (#141562)SubbaraoGarlapati2025-11-171-8/+8
|
* gh-131510: Use PyUnstable_Unicode_GET_CACHED_HASH() (GH-141520)Victor Stinner2025-11-141-1/+0
| | | | | | | | Replace code that directly accesses PyASCIIObject.hash with PyUnstable_Unicode_GET_CACHED_HASH(). Remove redundant "assert(PyUnicode_Check(op))" from PyUnstable_Unicode_GET_CACHED_HASH(), _PyASCIIObject_CAST() already implements the check.
* gh-116146: Add C-API to create module from spec and initfunc (GH-139196)Itamar Oren2025-11-141-0/+7
| | | | | Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Petr Viktorin <encukou@gmail.com> Co-authored-by: Victor Stinner <vstinner@python.org>
* gh-139109: A new tracing JIT compiler frontend for CPython (GH-140310)Ken Jin2025-11-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This PR changes the current JIT model from trace projection to trace recording. Benchmarking: better pyperformance (about 1.7% overall) geomean versus current https://raw.githubusercontent.com/facebookexperimental/free-threading-benchmarking/refs/heads/main/results/bm-20251108-3.15.0a1%2B-7e2bc1d-JIT/bm-20251108-vultr-x86_64-Fidget%252dSpinner-tracing_jit-3.15.0a1%2B-7e2bc1d-vs-base.svg, 100% faster Richards on the most improved benchmark versus the current JIT. Slowdown of about 10-15% on the worst benchmark versus the current JIT. **Note: the fastest version isn't the one merged, as it relies on fixing bugs in the specializing interpreter, which is left to another PR**. The speedup in the merged version is about 1.1%. https://raw.githubusercontent.com/facebookexperimental/free-threading-benchmarking/refs/heads/main/results/bm-20251112-3.15.0a1%2B-f8a764a-JIT/bm-20251112-vultr-x86_64-Fidget%252dSpinner-tracing_jit-3.15.0a1%2B-f8a764a-vs-base.svg Stats: 50% more uops executed, 30% more traces entered the last time we ran them. It also suggests our trace lengths for a real trace recording JIT are too short, as a lot of trace too long aborts https://github.com/facebookexperimental/free-threading-benchmarking/blob/main/results/bm-20251023-3.15.0a1%2B-eb73378-CLANG%2CJIT/bm-20251023-vultr-x86_64-Fidget%252dSpinner-tracing_jit-3.15.0a1%2B-eb73378-pystats-vs-base.md . This new JIT frontend is already able to record/execute significantly more instructions than the previous JIT frontend. In this PR, we are now able to record through custom dunders, simple object creation, generators, etc. None of these were done by the old JIT frontend. Some custom dunders uops were discovered to be broken as part of this work gh-140277 The optimizer stack space check is disabled, as it's no longer valid to deal with underflow. Pros: * Ignoring the generated tracer code as it's automatically created, this is only additional 1k lines of code. The maintenance burden is handled by the DSL and code generator. * `optimizer.c` is now significantly simpler, as we don't have to do strange things to recover the bytecode from a trace. * The new JIT frontend is able to handle a lot more control-flow than the old one. * Tracing is very low overhead. We use the tail calling interpreter/computed goto interpreter to switch between tracing mode and non-tracing mode. I call this mechanism dual dispatch, as we have two dispatch tables dispatching to each other. Specialization is still enabled while tracing. * Better handling of polymorphism. We leverage the specializing interpreter for this. Cons: * (For now) requires tail calling interpreter or computed gotos. This means no Windows JIT for now :(. Not to fret, tail calling is coming soon to Windows though https://github.com/python/cpython/pull/139962 Design: * After each instruction, the `record_previous_inst` function/label is executed. This does as the name suggests. * The tracing interpreter lowers bytecode to uops directly so that it can obtain "fresh" values at the point of lowering. * The tracing version behaves nearly identical to the normal interpreter, in fact it even has specialization! This allows it to run without much of a slowdown when tracing. The actual cost of tracing is only a function call and writes to memory. * The tracing interpreter uses the specializing interpreter's deopt to naturally form the side exit chains. This allows it to side exit chain effectively, without repeating much code. We force a re-specializing when tracing a deopt. * The tracing interpreter can even handle goto errors/exceptions, but I chose to disable them for now as it's not tested. * Because we do not share interpreter dispatch, there is should be no significant slowdown to the original specializing interpreter on tailcall and computed got with JIT disabled. With JIT enabled, there might be a slowdown in the form of the JIT trying to trace. * Things that could have dynamic instruction pointer effects are guarded on. The guard deopts to a new instruction --- `_DYNAMIC_EXIT`.
* gh-139653: Add PyUnstable_ThreadState_SetStackProtection() (#139668)Victor Stinner2025-11-131-0/+12
| | | | | | | | Add PyUnstable_ThreadState_SetStackProtection() and PyUnstable_ThreadState_ResetStackProtection() functions to set the stack base address and stack size of a Python thread state. Co-authored-by: Petr Viktorin <encukou@gmail.com>
* gh-139871: Add `bytearray.take_bytes([n])` to efficiently extract `bytes` ↵Cody Maloney2025-11-131-8/+8
| | | | | | | | | | | | | | | | | | | | | | | (GH-140128) Update `bytearray` to contain a `bytes` and provide a zero-copy path to "extract" the `bytes`. This allows making several code paths more efficient. This does not move any codepaths to make use of this new API. The documentation changes include common code patterns which can be made more efficient with this API. --- When just changing `bytearray` to contain `bytes` I ran pyperformance on a `--with-lto --enable-optimizations --with-static-libpython` build and don't see any major speedups or slowdowns with this; all seems to be in the noise of my machine (Generally changes under 5% or benchmarks that don't touch bytes/bytearray). Co-authored-by: Victor Stinner <vstinner@python.org> Co-authored-by: Maurycy Pawłowski-Wieroński <5383+maurycy@users.noreply.github.com>
* gh-111389: replace deprecated occurrences of `_PyHASH_*` macros (#141236)Bénédikt Tran2025-11-091-2/+2
|
* gh-131253: free-threaded build support for pystats (gh-137189)Neil Schemenauer2025-11-032-13/+75
| | | | | | | | Allow the --enable-pystats build option to be used with free-threading. The stats are now stored on a per-interpreter basis, rather than process global. For free-threaded builds, the stats structure is allocated per-thread and then periodically merged into the per-interpreter stats structure (on thread exit or when the reporting function is called). Most of the pystats related code has be moved into the file Python/pystats.c.
* gh-139640: Fix swallowing syntax warnings in different modules (GH-139755)Serhiy Storchaka2025-10-141-6/+0
| | | | | | Revert GH-131993. Fix swallowing some syntax warnings in different modules if they accidentally have the same message and are emitted from the same line.
* gh-112075: Remove _PyObject_SetManagedDict() function (#139737)Victor Stinner2025-10-121-1/+0
| | | Move it to the internal C API and no longer export it.
* gh-139924: Add PyFunction_PYFUNC_EVENT_MODIFY_QUALNAME event for function ↵Dino Viehland2025-10-101-1/+2
| | | | | watchers (#139925) Add PyFunction_PYFUNC_EVENT_MODIFY_QUALNAME event for function watchers
* gh-111489: Add PyTuple_FromArray() function (#139691)Victor Stinner2025-10-101-0/+4
|
* gh-70030: Remove _PyCode_ConstantKey() function (#139735)Victor Stinner2025-10-081-9/+0
| | | Move the function to the internal C API and no longer export it.
* gh-138342: Move _PyObject_VisitType() to the internal C API (#139734)Victor Stinner2025-10-081-4/+0
|
* gh-79315: Add Include/cpython/structseq.h header (#139730)Victor Stinner2025-10-071-0/+12
|
* gh-79315: Remove Include/pylock.h and Include/monitoring.h (#139731)Victor Stinner2025-10-072-4/+27
| | | Keep Include/cpython/pylock.h and Include/cpython/monitoring.h.
* gh-79315: Add Include/cpython/sliceobject.h header (#139729)Victor Stinner2025-10-071-0/+20
|
* gh-79315: Add Include/cpython/marshal.h header (#139725)Victor Stinner2025-10-071-0/+17
|
* gh-133644: remove `PyWeakref_GetObject` and `PyWeakref_GET_OBJECT` (GH-133657)Bénédikt Tran2025-09-241-17/+0
|
* gh-136003: Execute pre-finalization callbacks in a loop (GH-136004)Peter Bierma2025-09-181-0/+1
|
* GH-138355: Remove trash_delete_later from _gc_runtime_state (#138767)Sergey Miryanov2025-09-171-0/+5
| | | Remove trash_delete_later and trash_delete_nesting from _gc_runtime_state.
* gh-138794: Communicate to PyRefTracer when they are being replaced (#138797)Pablo Galindo Salgado2025-09-151-0/+1
|
* gh-129813, PEP 782: Add PyBytesWriter_Format() (#138824)Victor Stinner2025-09-121-0/+4
| | | | Modify PyBytes_FromFormatV() to use the public PyBytesWriter API rather than the _PyBytesWriter private API.
* gh-129813, PEP 782: Add PyBytesWriter C API (#138822)Victor Stinner2025-09-121-0/+39
|
* gh-137210: Add a struct, slot & function for checking an extension's ABI ↵Petr Viktorin2025-09-051-0/+12
| | | | | (GH-137212) Co-authored-by: Steve Dower <steve.dower@microsoft.com>
* gh-135755: Make Py_MAX_SCRIPT_PATH_SIZE private (#138350)Victor Stinner2025-09-011-2/+2
|
* gh-138342: Use a common utility for visiting an object's type (GH-138343)Peter Bierma2025-09-011-0/+4
| | | Add `_PyObject_VisitType` in place of `tp_traverse` functions that only visit the object's type.
* GH-136410: Faster side exits by using a cold exit stub (GH-136411)Mark Shannon2025-08-011-0/+3
|
* gh-128813: soft-deprecate _Py_c_*() functions (GH-137261)Sergey B Kirpichev2025-08-011-1/+2
|
* gh-136759: rename `lock.h` to `pylock.h` (#137041)AN Long2025-07-241-0/+0
| | | Rename `lock.h` to `pylock.h` to avoid conflicts with headers of other projects.
* gh-133296: Publicly expose critical section API that accepts PyMutex (gh-135899)Nathan Goldbaum2025-07-211-0/+20
| | | | | | | | | | | | | | | This makes the following APIs public: * `Py_BEGIN_CRITICAL_SECTION_MUTEX(mutex),` * `Py_BEGIN_CRITICAL_SECTION2_MUTEX(mutex1, mutex2)` * `void PyCriticalSection_BeginMutex(PyCriticalSection *c, PyMutex *mutex)` * `void PyCriticalSection2_BeginMutex(PyCriticalSection2 *c, PyMutex *mutex1, PyMutex *mutex2)` The macros are identical to the corresponding `Py_BEGIN_CRITICAL_SECTION` and `Py_BEGIN_CRITICAL_SECTION2` macros (e.g., they include braces), but they accept a `PyMutex` instead of an object. The new macros are still paired with the existing END macros (`Py_END_CRITICAL_SECTION`, `Py_END_CRITICAL_SECTION2`).
* GH-133711: Enable UTF-8 mode by default (PEP 686) (#133712)Adam Turner2025-07-151-7/+6
| | | Co-authored-by: Victor Stinner <vstinner@python.org>
* gh-92536: Fix comment about number of unicode string types (#136439)Arseniy Terekhin2025-07-081-1/+1
|
* gh-134009: Expose `PyMutex_IsLocked` in the public C API (gh-134365)Sam Gross2025-07-011-0/+11
| | | | | The `PyMutex_IsLocked()` function is useful in assertions for verifying that code maintains certain locking invariants.
* gh-135755: Use private names (_Py*) for header file guards new in 3.14 ↵Petr Viktorin2025-06-261-1/+1
| | | | | (GH-135921) These are private API; let's name new ones accordingly.
* gh-135755: Move `PyFunction_GET_BUILTINS` to the private API (GH-135938)Peter Bierma2025-06-261-5/+0
|
* gh-131591: Add Py_ prefix to MAX_SCRIPT_PATH_SIZE; remove unprefixed struct ↵Petr Viktorin2025-06-261-3/+3
| | | | | tag (GH-135924) Names/macros defined in public headers should have `Py`/`_Py` prefixes.
* gh-135379: Move PyLong_CheckCompact to private header and rename it (GH-135707)Ken Jin2025-06-191-6/+0
|
* gh-135379: Add back const cast to _PyLong_IsCompact (GH-135706)Ken Jin2025-06-191-2/+2
|
generated by cgit v0.12 at 2025-12-27 18:31:29 (GMT)