From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: Troubles with Objcode and Storing JIT Pointers
Date: Mon, 21 Jun 2010 18:23:00 -0400 [thread overview]
Message-ID: <AANLkTik-Kv8dHen0Cn4D8kTnB-zBeI6cokf-_xowAFdK@mail.gmail.com> (raw)
In-Reply-To: <m3tyow9m09.fsf@pobox.com>
Hi Andy,
That sounds excellent. If I may ask, do you already have patches or a
git branch that adds this slot? If so, what are you doing about the
embedded objcode issue? (Changing the bytecode to leave room for it,
or hiding the slot in the C code?)
If not, why don't I just write that up first and submit it as a
separate patch for Guile, and then try to add JIT stuff on top of it?
Noah
On Mon, Jun 21, 2010 at 4:19 PM, Andy Wingo <wingo@pobox.com> wrote:
> Hi Noah,
>
> On Mon 21 Jun 2010 20:19, Noah Lavine <noah.b.lavine@gmail.com> writes:
>
>> I don't know where to store the JITed code.
>
> The 2.2 branch probably will add a slot to objcode objects for native
> code. If you want to do this, that's fine. Otherwise if you want 2.0
> compat, use an object property, or equivalently, a weak-key hash table.
>
> Andy
> --
> http://wingolog.org/
>
next prev parent reply other threads:[~2010-06-21 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 18:19 Troubles with Objcode and Storing JIT Pointers Noah Lavine
2010-06-21 20:19 ` Andy Wingo
2010-06-21 22:23 ` Noah Lavine [this message]
2010-06-22 19:03 ` Andy Wingo
2010-07-03 18:28 ` Noah Lavine
2010-07-04 17:43 ` Noah Lavine
2010-07-17 11:36 ` Andy Wingo
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=AANLkTik-Kv8dHen0Cn4D8kTnB-zBeI6cokf-_xowAFdK@mail.gmail.com \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).