From: Andy Wingo <wingo@pobox.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: redoing SCM representation in 2.2
Date: Mon, 16 May 2011 11:40:23 +0200 [thread overview]
Message-ID: <m3mxinasqg.fsf@unquote.localdomain> (raw)
In-Reply-To: <72BFF702-0847-45A6-A433-4BAC00F5950B@raeburn.org> (Ken Raeburn's message of "Sun, 15 May 2011 16:43:26 -0400")
Hi Ken,
On Sun 15 May 2011 22:43, Ken Raeburn <raeburn@raeburn.org> writes:
>> FWIW I plan on moving objcode to be ELF in 2.2, which will mean we
> write
>> our own loader for ELF, so we would have similar concerns about
> mapping
>> the file in the right address range.
>
> Ooh, also very interesting. Though, I would think the win of using ELF
> would be the ability to treat it as a native object file and use native
> support, which only works on ELF systems.
Actually that's only part of it. The point I'm mainly interested in is
its extensibility. The fact that it can interoperate with native tools
on GNU systems is a plus, but I want to use ELF even for bytecode.
> If you have to write your own loader anyways, we could pick up some
> lessons from ELF, and maybe use something modeled on it, but I'm not
> sure ELF itself is best; it's probably got a lot of stuff we don't need.
True, true; definitely something to figure out as we go.
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-16 9:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 10:17 redoing SCM representation in 2.2 Andy Wingo
2011-05-12 11:12 ` nalaginrut
2011-05-12 12:50 ` Stefan Israelsson Tampe
2011-05-13 22:08 ` Mark H Weaver
2011-05-14 9:47 ` Andy Wingo
2011-05-15 9:02 ` Ken Raeburn
2011-05-15 15:35 ` Andy Wingo
2011-05-15 9:00 ` Ken Raeburn
2011-05-15 15:47 ` Andy Wingo
2011-05-15 20:43 ` Ken Raeburn
2011-05-16 9:40 ` Andy Wingo [this message]
2011-05-17 18:59 ` Mark H Weaver
2011-05-19 7:58 ` Ken Raeburn
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=m3mxinasqg.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.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).