Currently, this is illegal in bytecodes.c:

macro(TO_BOOL) = 
    _SPECIALIZE_TO_BOOL +
    _RECORD_TOS_TYPE +
    unused/2 +
   _TO_BOOL;

because both specializing and recording uops must be first. Since specializing uops are only present in tier 1, and recording uops are only present in tier 2, there should be no conflict.

We should fix Tools/cases_generator/analyzer.py to allow a recording uop to follow a specializing uop.

Linked PRs

• gh-148285: Allow recording uops after specializing uops #148367
• gh-148285: Allow recording uops after specializing uops #148373
• gh-148285: Allow recording uops after specializing uops #148482