From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Storing JIT Code
Date: Wed, 18 Aug 2010 22:58:54 -0700 [thread overview]
Message-ID: <m3lj83ta75.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTim1XXhgA6gCJEA_wMmCqtj1ztcqmWgldDEyZyP7@mail.gmail.com> (Noah Lavine's message of "Sun, 18 Jul 2010 22:01:36 -0400")
Hi Noah,
On Sun 18 Jul 2010 19:01, Noah Lavine <noah.b.lavine@gmail.com> writes:
> Attached are some patches I made for storing JIT code associated with
> objcode objects. These are based on some threads a few weeks ago in
> which we discussed how to handle JIT code, with the eventual goal of
> adding a JIT compiler to Guile (I'm working on it).
Very interesting patches. They are a good start. Have you gone further
with them?
We should be able to coalesce the "fd" field of objcode with "parent",
as they are mutually exclusive, so perhaps we can have a fourth word in
objcode for jitted code.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-08-19 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 2:01 Storing JIT Code Noah Lavine
2010-08-19 5:58 ` Andy Wingo [this message]
2010-08-19 12:40 ` Noah Lavine
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3lj83ta75.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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.
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).