unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: rtl metadata musings
Date: Mon, 20 May 2013 16:23:25 +0200	[thread overview]
Message-ID: <877gitd92a.fsf@pobox.com> (raw)
In-Reply-To: <87bo86y6vx.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 19 May 2013 23:52:34 +0200")

Hi,

On Sun 19 May 2013 23:52, ludo@gnu.org (Ludovic Courtès) writes:

> I guess literal strings would go out as per ‘SCM_IMMUTABLE_STRING’
> (which needs relocation), right?

Yep.  Right now the stringbuf goes into read-only memory, but the string
itself goes in writable memory as it needs its link to the stringbuf
fixed up (relocated) at runtime.

> Perhaps the .guile.docstr section could eventually be used to contain
> stexi, but that seems to already fit into the plan anyway.

That can happen already, but I think if we do texinfo we should
serialize the string as texinfo -- that way no relocs are needed if
docstrings aren't used, because if we use the .docstr string table, it's
just an offset into the image of a NUL-terminated UTF-8 byte sequence.
(I suppose we should be careful about embedded NUL characters; perhaps
we should use some other format for the string tables.)

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2013-05-20 14:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10  5:07 rtl metadata musings Andy Wingo
2013-05-11  4:48 ` Mark H Weaver
2013-05-12 21:20   ` Andy Wingo
2013-05-16 21:42 ` Andy Wingo
2013-05-19 21:52 ` Ludovic Courtès
2013-05-20 14:23   ` Andy Wingo [this message]
2013-05-20 16:37     ` Ludovic Courtès
2013-05-20 16:48       ` Mike Gran
2013-05-20 18:29       ` Andy Wingo
2013-05-20 19:28         ` Ludovic Courtès
2013-05-20 20:24           ` 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=877gitd92a.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).