[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JIT compiling
From: |
Oliver Heimlich |
Subject: |
Re: JIT compiling |
Date: |
Fri, 12 Aug 2016 18:06:08 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0 |
On 12.08.2016 17:08, Sergei Steshenko wrote:
>> ________________________________
>> From: Jordi Gutiérrez Hermoso <address@hidden>
>> To: Alex Vong <address@hidden>
>> Cc: Ricardo Wurmus <address@hidden>; address@hidden; Leo Famulari
>> <address@hidden>; address@hidden; Mike Miller <address@hidden>
>> Sent: Friday, August 12, 2016 2:45 PM
>> Subject: JIT compiling
>>
>>
>> On Thu, 2016-08-11 at 23:27 +0800, Alex Vong wrote:
>>> Finally, some unrelated stuff, I hope octave would have a byte code
>>> interpreter soon. I would suggest to write it in rpython, it seems
>>> to be the easiest way to have jit these days.
>>
>> That is a faraway pipe dream. Can you help?
>>
>> - Jordi G. H.
>>
>>
>
>
> Julia ( http://julialang.org/ ) quite developed since it's been discussed
> here. They claim to have close to "C" performance and JIT.
>
There is a good language introduction available as a talk from JuliaCon:
https://youtu.be/rAxzR7lMGDM
As far as I can see, Julia compiles the code if it can predict the types
of the variables. Otherwise, it is slow. This is explained in the first
part of the talk.
Best
Oliver
- Re: octave license is incompatible with openssl, (continued)
Re: octave license is incompatible with openssl, Alex Vong, 2016/08/10
JIT compiling, Jordi Gutiérrez Hermoso, 2016/08/12
Re: JIT compiling, Sergei Steshenko, 2016/08/12
Re: JIT compiling,
Oliver Heimlich <=
Re: JIT compiling, Sergei Steshenko, 2016/08/12
Re: JIT compiling, Alex Vong, 2016/08/13
Re: JIT compiling, Alex Vong, 2016/08/13
Re: JIT compiling, Sergei Steshenko, 2016/08/14
Re: JIT compiling, Jordi Gutiérrez Hermoso, 2016/08/14
Re: JIT compiling, Francesco Potortì, 2016/08/16
Re: octave license is incompatible with openssl, Mark H Weaver, 2016/08/10