> Does this allow AOT compiling of Racket code to native ARM?
Yes, there's an example of this in the section "Cross-compile Racket modules for iOS".
> Assuming that JIT is still not possible on iOS.
JIT on iOS is not possible for non-side-loaded apps, like you mentioned downthread. That's part of the caveats[1] I mention at the top of the article and the more complex part of the change: when compiling new code (eg. via `eval`), we flip the protection bits between W and X for the minimum set of memory segments necessary based on certain heuristics.
Yes, there's an example of this in the section "Cross-compile Racket modules for iOS".
> Assuming that JIT is still not possible on iOS.
JIT on iOS is not possible for non-side-loaded apps, like you mentioned downthread. That's part of the caveats[1] I mention at the top of the article and the more complex part of the change: when compiling new code (eg. via `eval`), we flip the protection bits between W and X for the minimum set of memory segments necessary based on certain heuristics.
[1]: https://github.com/racket/racket/blob/351c0047d6371e36cf422b...