From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Allocating Executable Memory
Date: Sun, 06 Jun 2010 21:54:49 +0200 [thread overview]
Message-ID: <m339x0ueba.fsf@pobox.com> (raw)
In-Reply-To: <AANLkTinikNOVGSCVoawhK7YSpuqJ5IqD1kEcqtitVcWu@mail.gmail.com> (Noah Lavine's message of "Sat, 5 Jun 2010 14:28:44 -0400")
On Sat 05 Jun 2010 20:28, Noah Lavine <noah.b.lavine@gmail.com> writes:
> It seems like the right solution is to give the GC system the ability
> to manage executable memory at the user's request, but that will
> require some modifications.
>
> So, people who are familiar with the GC system, where should those
> modifications be made, and how would you do it?
The best thing would be to modify libgc to provide hooks to manage
executable memory. Otherwise you would have to implement an executable
memory manager on top of mmap et al, and make GC-managed objects that
are associated with that executable memory, with finalizers or
guardians.
A
--
http://wingolog.org/
prev parent reply other threads:[~2010-06-06 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 18:28 Allocating Executable Memory Noah Lavine
2010-06-06 14:15 ` Ludovic Courtès
2010-06-06 19:54 ` Andy Wingo [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=m339x0ueba.fsf@pobox.com \
--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).