From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: A Representation for Native Code
Date: Wed, 05 Jan 2011 22:38:31 +0100 [thread overview]
Message-ID: <87r5crghew.fsf@gnu.org> (raw)
In-Reply-To: AANLkTineFigG+y32z1f71Fsg-AwjAZLcsO3benvWqNej@mail.gmail.com
Hi Noah,
Noah Lavine <noah.b.lavine@gmail.com> writes:
> Also, am I correct in assuming that we'd want to keep the old objcode
> around even after we jitted something, just in case something tried to
> introspect on it? I think putting it in a procedure property would
> work.
I think so, because there’s ‘objcode-meta’, used by ‘program-meta’,
which returns a thunk that itself returns procedure meta-data:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (use-modules (system vm program))
scheme@(guile-user)> ((program-meta 1+))
$3 = (() () ((3 7 1 0 #f)) (name . 1+))
--8<---------------cut here---------------end--------------->8---
Thanks,
Ludo’.
prev parent reply other threads:[~2011-01-05 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 0:20 A Representation for Native Code Noah Lavine
2011-01-05 21:38 ` Ludovic Courtès [this message]
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=87r5crghew.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.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.
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).