gh-106290: Fix edge cases around uops

[gvanrossum]

A bit of an omnibus PR, alas (let me know if you want it split up). This does roughly the following (though not in that order):

• Tweak uops debugging output
• Fix the bug from Line numbers for errors off in traces #106290
• Rename SET_IP to SAVE_IP (per Creation of superblocks faster-cpython/ideas#558)
• Add a SAVE_IP uop at the start of the trace (ditto)
• Allow unbound_local_error; this gives us uops for LOAD_FAST_CHECK, LOAD_CLOSURE, and DELETE_FAST
• Longer traces
• Support STORE_FAST_LOAD_FAST, STORE_FAST_STORE_FAST
• Add deps on pycore_uops.h to Makefile(.pre.in)

[gvanrossum]

While we're cleaning up uops, maybe we should change "trace" to "superblock"? There are already several other things using the name "trace", e.g. sys.settrace(), tracemalloc, lltrace.

[gvanrossum]

This (with uops on by default) benchmarks 2% slower than main (with uops off by default).

I will now revert the final (temporary) commit that turns on uops by default and mark it as ready for review.

[gvanrossum]

(Also, the tests that fail with uops on by default are largely expected. There's one refleak -- maybe I should ask Kumar to review it again. :-)

[gvanrossum]

Maybe the leak is the optimizer created and installed initially.

[brandtbucher]

The code itself looks good, haven't tried running it myself or anything. Just one note:

[brandtbucher]

I don't see where this is defined...

[gvanrossum]

Turd from the last cleanup. I'll get rid of it, then land it.

[bedevere-bot]

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot ARM64 macOS 3.x has failed when building commit 2028a4f.

What do you need to do:

1. Don't panic.
2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/725/builds/4943) and take a look at the build logs.
4. Check if the failure is related to this commit (2028a4f) or if it is a false positive.
5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/725/builds/4943

Failed tests:

• test_unittest

Failed subtests:

• test_wait_until_any_call_positional - test.test_unittest.testmock.testthreadingmock.TestThreadingMock.test_wait_until_any_call_positional

Summary of the results of the build (if available):

== Tests result: FAILURE then FAILURE ==

420 tests OK.

10 slowest tests:

• test_signal: 4 min 13 sec
• test_concurrent_futures: 2 min 49 sec
• test_multiprocessing_spawn: 2 min 19 sec
• test_multiprocessing_forkserver: 1 min 41 sec
• test_math: 1 min 38 sec
• test_logging: 1 min 3 sec
• test_capi: 54.7 sec
• test_unparse: 49.4 sec
• test_tokenize: 45.2 sec
• test_ssl: 43.1 sec

1 test failed:
test_unittest

22 tests skipped:
test.test_asyncio.test_windows_events
test.test_asyncio.test_windows_utils test_devpoll test_epoll
test_gdb test_idle test_ioctl test_launcher
test_multiprocessing_fork test_perf_profiler test_perfmaps
test_startfile test_tcl test_tkinter test_ttk test_ttk_textonly
test_turtle test_winconsoleio test_winreg test_winsound test_wmi
test_zipfile64

1 re-run test:
test_unittest

Total duration: 10 min 6 sec

Click to see traceback logs

Traceback (most recent call last):
  File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/test/test_unittest/testmock/testthreadingmock.py", line 173, in test_wait_until_any_call_positional
    self.assertNotIn(call(2), something.method_1.mock_calls)
AssertionError: call(2) unexpectedly found in [call(2), call(1)]


Traceback (most recent call last):
  File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/test/test_unittest/testmock/testthreadingmock.py", line 172, in test_wait_until_any_call_positional
    something.method_1.assert_called_with(1)
  File "/Users/buildbot/buildarea/3.x.pablogsal-macos-m1.macos-with-brew/build/Lib/unittest/mock.py", line 979, in assert_called_with
    raise AssertionError(_error_message()) from cause
AssertionError: expected call not found.
Expected: method_1(1)
Actual: method_1(2)