> This is true. I used this in my optimization from two > years ago, and moved the oparg preparation into the > opcode cases, not doing any test, but just fetching > the argument. What happened to the optimization. It is not in the current code? > I also turned this into macros which > added to the insn pointer only once. > Incredible but true: Most of the win I gathered was > by typecasting the oparg access differently into > a reference to a short int, instead of oring two > bytes. I skipped over that one because I thought that it would fail on a big-endian computer. Raymond Hettinger
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4