From: "Jordi Gutiérrez Hermoso" <jordigh@octave.org>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org, help-octave@gnu.org,
Mike Miller <mtmiller@octave.org>
Subject: JIT compiling
Date: Fri, 12 Aug 2016 07:45:46 -0400 [thread overview]
Message-ID: <1471002346.7915.4.camel@octave.org> (raw)
In-Reply-To: <87fuqbl40a.fsf@gmail.com>
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.
next prev parent reply other threads:[~2016-08-12 14:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 16:35 octave license is incompatible with openssl Alex Vong
2016-08-04 17:10 ` John Darrington
2016-08-04 17:20 ` ng0
2016-08-05 9:08 ` Alex Vong
2016-08-05 9:03 ` Alex Vong
2016-08-05 11:43 ` Mathieu Lirzin
2016-08-05 6:50 ` Ricardo Wurmus
2016-08-06 1:52 ` Alex Vong
2016-08-08 20:00 ` Leo Famulari
2016-08-09 16:00 ` Alex Vong
2016-08-09 17:27 ` Mike Miller
2016-08-09 18:30 ` Ricardo Wurmus
2016-08-09 21:33 ` kei
2016-08-10 4:28 ` Mark H Weaver
2016-08-11 5:56 ` Mike Miller
2016-08-11 9:58 ` Mark H Weaver
2016-08-10 4:23 ` Mark H Weaver
2016-08-10 6:43 ` Alex Vong
2016-08-11 6:26 ` Mike Miller
2016-08-11 15:27 ` Alex Vong
2016-08-11 17:04 ` Kei Kebreau
2016-08-13 12:37 ` Alex Vong
2016-08-12 11:45 ` Jordi Gutiérrez Hermoso [this message]
2016-08-12 15:08 ` JIT compiling Sergei Steshenko
2016-08-12 16:06 ` Oliver Heimlich
2016-08-13 1:03 ` Sergei Steshenko
2016-08-13 11:48 ` Alex Vong
2016-08-13 12:12 ` Alex Vong
2016-08-14 8:07 ` Sergei Steshenko
2016-08-14 10:21 ` Francesco Potortì
2016-08-14 20:20 ` Jordi Gutiérrez Hermoso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1471002346.7915.4.camel@octave.org \
--to=jordigh@octave.org \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=help-octave@gnu.org \
--cc=mtmiller@octave.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).