Repository navigation
Allow recording uops after specializing uops #148285
Description
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.
Activity
adityakrmishra commentedon Apr 11, 2026
Hi @markshannon I'd like to take this on.
I see that the validation logic in Tools/cases_generator/analyzer.py currently rejects a recording uop following a specializing uop Since specializing is restricted to Tier 1 and recording to Tier 2, there shouldn't be a conflict. I can update the analyzer's parsing/validation rules to permit this sequence
Could you assign this to me? I'll spin up a PR with the fix shortly
kumaraditya303 commentedon Apr 11, 2026
We do not assign issues to non-core devs, if you have a fix feel free to propose a PR.
adityakrmishra commentedon Apr 11, 2026
Thanks for the heads-up! I've started working on the analyzer.py fix locally and will open a PR with the proposed changes shortly.
pythongh-148285: Allow recording uops after specializing uops in case…
pythongh-148285: Allow recording uops after specializing uops in case…
pythongh-148285: Allow recording uops after specializing uops
pythongh-148285: Allow recording uops after specializing uops
NekoAsakura commentedon Apr 12, 2026
I'm on it.
pythongh-148285: Allow recording uops after specializing uops
gh-148285: Allow recording uops after specializing uops (GH-148482)
Fidget-Spinner commentedon Apr 13, 2026
Done.
pythongh-148285: Allow recording uops after specializing uops (python…