[Pharo-dev] VM for Athens Graphics

Stéphane Ducasse stephane.ducasse at inria.fr
Fri Oct 25 03:22:27 EDT 2013


> 
> Ok I was not aware you were thinking about that. So this is good to have this path in my radar.
> 
> Yes, this is actually what we discussed recently with Esteban about possible alternatives and
> low-hanging fruits :)

I like these ones :)

>  
>> Concerning ARM:
>>  - Damien Pollet works on ARM assembler for ASMJit.
>> as soon as it working, we can try doing something with it.
>> 
>> But in addition, what i would like to do is to move more towards platform-neutral FFI implementation,
>> using low-level assembler DSL which is platform neutral. There's a work started on it
>> as part of Mate project, but it is yet far from finished.
> 
> I would love that.
> Now I guess that I'm correct to say that even with it the fact that it would generate assembly on the fly
> would make it a no go for iPad and friends.
> 
> I thought that esteban and you thought about generating the "assembly once for all for Ipda and putting it in file"
> so that we do not have the "assembly generation" problem?
> 
> that's a big question, whether such idea fits into apple technicians/politicans heads or not.
> Do you think we have enough time/resources to waste on implementing such mechanism
> only to discover later that Apple says 'over my dead body'?
> The point is that generating code, saving it to file, and then loading that file as DLL,
> is largely a hack.
> You either allowed to run your own generated code or not.. because from security perspective,
> the fact that you first stored it into file and then load it back doesn't changes a tiny bit.
> From design perspective, it is crutch, which don't really buys anything (why on earth, anyone would want to deal with files
> and OS, if he could just run code which already in memory?).
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131025/eb1e87e3/attachment-0002.html>


More information about the Pharo-dev mailing list