Repository navigation
[DRAFT] gh-105059: In C++, Py_INCREF() uses a function call - #105764
vstinner wants to merge 1 commit into
Conversation
Sorry, something went wrong.
In C++, Py_INCREF() and Py_DECREF() are now implemented as function calls. Moreover, in C++, PyObject.ob_refcnt type is just Py_ssize_t: don't use an anonymous union to avoid compiler warnings (anonymous unions were added to C11).
|
In the issue #105387, I modified Py_INCREF() and Py_DECREF() to implement them as opaque function calls in the limited C API version 3.12 and newer (and when Python is built in debug mode): commit b542972 We can consider to do something similar in C++ and/or in C without anonymous union (ex: ISO C89). This PR implements this idea for C++: in C++, PyObject.ob_refcnt type is again the simple Py_ssize_t, and Py_INCREF() and Py_DECREF() are implemented as function calls. Well, I wrote this PR to show that we now have this technical solution, but it has a cost on performance. I don't know if it's acceptable for Python 3.12. Alternatives are discussed in issue #105059 and PR #105275. |
Sorry, something went wrong.
C compiler configured for C99 in pedantic mode also emits a compiler warning (which may be treated as error) in Include/object.h because of the PyObject.ob_refcnt anonymous union: #105059 (comment) |
Sorry, something went wrong.
|
Abandoned in favor of PR #105767. C++ is unaffected by the issue: #105059 (comment) |
Sorry, something went wrong.
In C++, Py_INCREF() and Py_DECREF() are now implemented as function calls. Moreover, in C++, PyObject.ob_refcnt type is just Py_ssize_t: don't use an anonymous union to avoid compiler warnings (anonymous unions were added to C11).