From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergei Steshenko Subject: Re: JIT compiling Date: Sun, 14 Aug 2016 08:07:44 +0000 (UTC) Message-ID: <1610542567.1951337.1471162064614@mail.yahoo.com> References: <87h9b0ij9x.fsf@gmail.com> <87wpjvhfpg.fsf@elephly.net> <87eg62d5p4.fsf@gmail.com> <20160808200018.GA20179@jasmine> <871t1yvsn8.fsf@gmail.com> <20160809172728.b6wijrzccd5wdv37@galago.mtmxr.com> <87k2fpktsi.fsf@gmail.com> <20160811062627.mbaiqhssaejwh4hw@galago.mtmxr.com> <87fuqbl40a.fsf@gmail.com> <1471002346.7915.4.camel@octave.org> <87mvkgvpea.fsf@gmail.com> Reply-To: Sergei Steshenko Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44989) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYqWX-0007UD-62 for guix-devel@gnu.org; Sun, 14 Aug 2016 04:12:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bYqWS-00086B-Tg for guix-devel@gnu.org; Sun, 14 Aug 2016 04:12:00 -0400 Received: from nm38-vm5.bullet.mail.gq1.yahoo.com ([98.136.217.76]:53524) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bYqWS-000863-K8 for guix-devel@gnu.org; Sun, 14 Aug 2016 04:11:56 -0400 In-Reply-To: <87mvkgvpea.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Alex Vong , =?UTF-8?Q?Jordi_Guti=C3=A9rrez_Hermoso?= Cc: "guix-devel@gnu.org" , Mike Miller , "help-octave@gnu.org" ----- Original Message ----- > From: Alex Vong > To: Jordi Guti=C3=A9rrez Hermoso > Cc: Ricardo Wurmus ; guix-devel@gnu.org; Leo Famulari= ; help-octave@gnu.org; Mike Miller > Sent: Saturday, August 13, 2016 3:12 PM > Subject: Re: JIT compiling >=20 > Jordi Guti=C3=A9rrez Hermoso writes: >=20 >> 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. >>=20 >> That is a faraway pipe dream. Can you help? >>=20 > 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? >=20 >> - Jordi G. H. >=20 > Cheers, >=20 > Alex >=20 > _______________________________________________ > Help-octave mailing list > Help-octave@gnu.org > https://lists.gnu.org/mailman/listinfo/help-octave >=20 "I've always dreamt octave having good anoymous and nested function support" - then switch to Perl -> PDL (http://pdl.perl.org/) or OCaml (if y= ou want type strictness and near "C" performance). ... When Julia language was first discussed here, I suggested to write an Octav= e -> Julia translator, but I think it will NEVER be done for ideological (f= anatic support of false/fake GPL freedom) reasons. The rationale was to get the best of the two worlds - speed of Julia and pa= ckages available for Octave - in addition to what already exists for Julia. --Sergei.