@cdimauro thanks for raising those points.
First, there’s no clear statement about the memory consumption when using the JIT (compared to non-JIT, of course).
Good point, I realised the partial counterpart, PEP 779, mentions memory consumption on FT. I’ll take it up with the other authors on having an upper limit for additional memory use.
why continue spending time on a 32-bit platform/architecture?
This is an artefact of PEP 11, where 32-bit WIndows is still a tier 1 platform. See discussion here Consider downgrading Windows 32-bit from Tier-1 to Tier-2 or Tier-3? (in Python 3.13?) - #58 by AraHaan .
might suggest a change on the CPython parser as well, introducing
X = Y BINOP ZandX = UNOP Ybytecodes to help the JIT and gain some speed also on ceval (like I did time ago on WPython).
Actually, I think that point was communicated badly on our part. We’re not suggesting to change the IR or current JIT much. We’re just saying that the current JIT already has most of these properties, so they naturally fall out! I’ve since raised a PR to clarify this PEP 836: Clarify that only the frontend is changing by Fidget-Spinner · Pull Request #5023 · python/peps · GitHub