Crash report

This code snippet crashes when the JIT is enabled:

for _ in range(4096):
    2 ** 65

I believe this is caused by GH-132733. Specifically, the abstract interpreter generator "thinks" that the operation itself can escape, and spills res to the stack before it has been defined:

It also never writes the actual result to the stack once it has been computed, leaving the garbage value in its place.

The fix is probably to teach the code generator that nothing using this "pure" constant evaluation mechanism can escape.

Linked PRs

• gh-136183: Deal with escapes in JIT optimizer's constant evaluator #136184