_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

首先檢查 PyCodeObject 如何間接向 abidiff 公開 _PyExecutorArray 和 _PyExecutorObject。比較兩種提議的方法——opaque public struct 或 void pointer——並檢查連結的 PR gh-153614 以了解目前的工作。完成的標準是：在不破壞先前的 ABI dumps 的情況下，executor 的欄位和偏移量不再出現在 stable-ABI 比較中。