All commit authors signed the Contributor License Agreement.

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

Hmm, while this does allow _RECORD uops to come after _SPECIALIZE uops, it also:

• Allows _RECORD uops to come after non _SPECIALIZE uops since not all tier-1 uops are specializing.
• No longer ensures both recording and specializing uops comes first

Example that violates both:

macro(LOAD_SUPER_ATTR) =
    _LOAD_SUPER_ATTR + // tier1 uop
    _RECORD_TOS_TYPE + 
    _SPECIALIZE_LOAD_SUPER_ATTR +
    _PUSH_NULL_CONDITIONAL;

BUT, you should wait for a core dev to review this as I may have misunderstood something.

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

@Sacul0457 Good catch! You are entirely correct—my previous logic conflated all tier1 uops with specializing uops, which was too permissive. I also tangled up the Git history on this branch, so I have closed this PR and opened a clean one with a much stricter positional index check that specifically guards for SPECIALIZE prefixes.

The new PR is here: #148373
Thanks for the review