[Vm-dev] iOS partial relaxation on executing downloaded code

John McIntosh johnmci at smalltalkconsulting.com
Wed Jun 14 00:38:19 UTC 2017


I do have a 64 bit cog(spur) stack VM working on the iPhone. Maybe later
this summer will merge. Early adopters who can compile/run/explore can
email me if they want early access.

The issue of JIT is completely different. You cannot get a page of
Executable Read/Write memory to work with. Apps with the Safari attribute
can, which they need for the JavaScript JIT, so it can grab some executable
memory. But my understanding is that request is granted once at startup
time (by the JIT engine) and application code doesn't have the ability to
grab a page because it is too late in the process for the request. So no
proper page(s) of memory, no JIT for you.


On Tue, Jun 13, 2017 at 10:22 AM, Ben Coman <btc at openinworld.com> wrote:

>
> This might be good news for some. I'm not sure whether it helps JITing.
>
> Apple made several changes to the App Store Review Guidelines during WWDC
> this week, including an easing of the prohibition against downloading and
> executing code on an iOS device. The ban on executable code remains intact,
> but rule 2.5.2 [1] now also provides that: Apps designed to teach, develop,
> or test executable code may, in limited circumstances, download code
> provided that such code is not used for other purposes. Such apps must make
> the source code provided by the Application completely viewable and
> editable by the user.
>
> cheers -ben
>
> [1] https://developer.apple.com/app-store/review/guidelines/#
> software-requirements
>
>


-- 
===========================================================================
John M. McIntosh. Corporate Smalltalk Consulting Ltd
https://www.linkedin.com/in/smalltalk
===========================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20170613/a7c27898/attachment-0001.html>


More information about the Vm-dev mailing list