Skip to content

[mypyc] Fix allow_interpreted_subclasses not seeing subclass attrs#21013

Open
VaggelisD wants to merge 3 commits intopython:masterfrom
VaggelisD:fix-interpreted-subclass-attr
Open

[mypyc] Fix allow_interpreted_subclasses not seeing subclass attrs#21013
VaggelisD wants to merge 3 commits intopython:masterfrom
VaggelisD:fix-interpreted-subclass-attr

Conversation

@VaggelisD
Copy link
Contributor

@VaggelisD VaggelisD commented Mar 12, 2026

When a compiled class with allow_interpreted_subclasses=True has methods that access self.ATTR via direct C struct slots, interpreted subclasses that override ATTR in their class __dict__ are ignored; the compiled method always reads the base class default from the slot.

The fix: In visit_get_attr for non-property attribute access, check if the instance is a mypyc-compiled type (via a new CPy_TPFLAGS_MYPYC_COMPILED tp_flags bit). If not, fall back to PyObject_GenericGetAttr which respects the MRO and finds the subclass override.

Using tp_flags rather than an exact type check ensures compiled subclasses retain fast direct struct access, while only interpreted subclasses hit the GenericGetAttr slow path.

For unboxed types (bool, int), the PyObject* result is unboxed to the expected C type.

EDIT:

Benchmark: get_x() on compiled vs interpreted subclasses (50M iters)

Base CompiledChild InterpretedChild
master (buggy) 1.543s (1.00x) 1.848s (1.20x) 1.852s (1.20x)
PR (fixed) 1.598s (1.00x) 1.867s (1.17x) 2.560s (1.60x)

  • On master, both compiled and interpreted children use direct struct access (buggy behavior)

  • For this PR, compiled children retain their cost while interpreted children correctly fall back to GenericGetAttr which is slower, but now correct since they can see overridden attributes.

…e overrides

When a compiled class with allow_interpreted_subclasses=True has methods that
access self.ATTR via direct C struct slots, interpreted subclasses that override
ATTR in their class __dict__ are ignored — the compiled method always reads the
base class default from the slot.

Fix: in visit_get_attr for non-property attribute access, check if the instance
is a mypyc-compiled type (via a new CPy_TPFLAGS_MYPYC_COMPILED tp_flags bit).
If not, fall back to PyObject_GenericGetAttr which respects the MRO and finds
the subclass override.

Using tp_flags rather than an exact type check ensures compiled subclasses
retain fast direct struct access, while only interpreted subclasses hit the
GenericGetAttr slow path.

For unboxed types (bool, int), the PyObject* result is unboxed to the expected
C type.
…omment

- Change CPy_TPFLAGS_MYPYC_COMPILED from bit 20 (Py_TPFLAGS_IS_ABSTRACT) to
  bit 21, which is unused across all CPython versions (3.8-3.14)
- Reword test comment to not claim direct struct access, since a runtime test
  cannot prove which code path was taken
@VaggelisD VaggelisD force-pushed the fix-interpreted-subclass-attr branch from 6ac30b0 to 96e99aa Compare March 20, 2026 16:09
// Flag bit set on all mypyc-compiled types. Used to distinguish compiled
// subclasses (safe for direct struct access) from interpreted subclasses
// (need PyObject_GenericGetAttr fallback) in allow_interpreted_subclasses mode.
#define CPy_TPFLAGS_MYPYC_COMPILED (1UL << 21)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of using TPFLAGS, could we add a flags field to the mypyc vtable for this purpose? This way we wouldn't need to touch CPython internal flags.

Copy link
Contributor Author

@VaggelisD VaggelisD Mar 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have additional pointers on how that'd look? Would we make the first vtable slot carry the flags?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants