I have contributed some code to JIT, mainly related to uop coverage. Currently, the plan for JIT is outlined in an overall direction at JIT Planning for 3.15 and 3.16 · Issue #139038 · python/cpython · GitHub . Since JIT is still in a rapid development stage, I think it is feasible to formulate specific short term plans and long term goals. However, for 3.15, the “must have” Free-threading support has not been completed. Currently, JIT is intentionally designed to be an easy-to-maintain mode, using many generators, but this also leads to the situation where only a few lines of changes ultimately result in thousands of lines of generated modifications, such as gh-148211: decompose `_SHUFFLE_3_LOAD_CONST_INLINE_BORROW` in JIT (GH… · python/cpython@2b6a137 · GitHub . Personally, I do not want this advantage to become a burden of fork merge conflicts. Perhaps during this period, there are clear and minor optimizations (that do not bring obvious visible performance improvements), such as Better uop coverage in the JIT optimizer · Issue #131798 · python/cpython · GitHub , which are acceptable? This is also the part that is easiest to implement and attract new volunteers, and it can maintain the level of activity.
1 Like