[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JIT compiling
From: |
Alex Vong |
Subject: |
Re: JIT compiling |
Date: |
Sat, 13 Aug 2016 20:12:29 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Jordi Gutiérrez Hermoso <address@hidden> writes:
> 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?
>
I think I will be too un-experienced to help, but I am interested in
it. I've always dreamt octave having good anoymous and nested function
support. I think the first step is to prase octave correctly. Is there a
reference on it other than the libinterp code itself?
> - Jordi G. H.
Cheers,
Alex
- 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, 2016/08/12
- Re: JIT compiling, Sergei Steshenko, 2016/08/12
- Re: JIT compiling, Alex Vong, 2016/08/13
- Re: JIT compiling,
Alex Vong <=
- 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