I been looking for it and can’t find it on there.
So it’s not on it at the Moment or am I missing it?
You’re not missing it, it’s not there.
Between here and reddit, there have been several dozens of topics explaining that apple forbids jits/dynarecs on ios, it’s kind of miracle that you missed that information.
Yeah, but there are tricks to get it working on side loaded builds, that’s how flycast and play! work. The dynarec in ppsspp works if you side load as well, though it’s completely unnecessary. It’s also completely unnecessary for the PS1 cores.
For N64 the cpu dynarec also isn’t available at all, but the parallel-rsp plugin does use a dynarec. If it’s not available and you try to select it, it will silently fall back to a plugin that doesn’t require it.
I knew they Banned JI for being used but did not get that it was the same with Dynarecs
The two terms, JIT and dynarec, have become mostly synonymous, at least in the context of emulators on iOS. They are not actually the same thing but most emulators that have an dynarec implement just in time dynamic recompilation.
1 Like
This was brought out in some of those topics, most (all ?) dynarecs are also affected.
In the first place, it’s kind of wrong to say that “apple ban jits”, what is banned is a “method of execution”. More specifically i think what’s forbidden is marking pages (memory blocks) as executables ? Maybe @warmenhoven would be able to confirm ?
JITs, which are just a subcategory of dynarec in the context of emulation, just happen to use that method, but it never meant other subcategories of dynarecs didn’t.
1 Like
I actually don’t know specifically which call is failing; when you run in a debugger it’s allowed, since the debugger needs to dynamically generate and execute instructions. (This is how side load builds enable dynarecs, is they ape the installation Xcode performs and then convince the OS that the app is being debugged.) I assume mprotect crashes when trying to mark pages as executable, yes.