This branch includes the NONE/NOT_NONE commits, so look at the last commit to see the TRUE/FALSE part.

Looks good to me. Want to run the buildbots on it before merging?

There are more bit hacks we could do to streamline the jump computation and evalbreaker checks, but that's for another PR.
faster-cpython/ideas#352

🤖 New build scheduled with the buildbot fleet by @iritkatriel for commit 4e29993 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

As we predicted, this change eliminates 90% of the jumps with extended args:

Static stats

Before:

Total: 81 errors
15,128 files
333,926 code objects
5,336,282 lines
44,626,367 opcodes
2,169,508 total size of co_consts
270,630 number of co_consts
378,034 number of absolute jumps
206,404 number of relative jumps
105,676 number of absolute jumps with extended args
8,898 number of relative jumps with extended args
5,121 number of absolute jumps backwards
433 number of absolute jumps backwards with extended args
375,233 number of absolute jumps with delta < 256

After:

Total: 81 errors
15,128 files
333,926 code objects
5,336,282 lines
44,524,476 opcodes
2,169,508 total size of co_consts
270,630 number of co_consts
7,844 number of absolute jumps
576,594 number of relative jumps
1,257 number of absolute jumps with extended args
11,426 number of relative jumps with extended args
7,834 number of absolute jumps with delta < 256

🤖 New build scheduled with the buildbot fleet by @iritkatriel for commit 09ba3bc 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

🤖 New build scheduled with the buildbot fleet by @iritkatriel for commit ec4dcf2 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

The buildbots are happy.