_PyExecutorObject is exposed to the abidiff tool due to indirect use in PyCodeObject

Bug report

Bug description:

The problem is that PyCodeObject is thought of as part of the stable ABI in abidiff. _PyExecutorArray and thus _PyExecutorObject is not an opaque struct, so its fields and offsets are exposed as part of the stable ABI seen by the tool. Theoretically, this should be fine and not lead to crashes long as no one accesses the _PyExecutorObject, but still this is pretty annoying to have if we are to backport changes to the JIT that require changing the executor, as this will trigger a warning on abidiff tools.

There are two possible fixes, turn the executor object in the public header to be an opaque struct, or use a void pointer. I think both are fine, I'm inclined to link to the first one for type-safety reasons).

We can only fix this on main, as any prior version would break the ABIdiff/dump tools.

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• gh-153614

Commencez par examiner comment PyCodeObject expose indirectement _PyExecutorArray et _PyExecutorObject à abidiff. Comparez les deux approches proposées —une structure publique opaque ou un void pointer— et examinez la PR liée gh-153614 pour voir l’état actuel du travail. C’est terminé lorsque les champs et offsets de l’executor ne sont plus exposés dans les comparaisons de la stable-ABI sans casser les ABI dumps précédents.