From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: subbytevectors
Date: Mon, 11 Jun 2012 16:01:51 +0200 [thread overview]
Message-ID: <87mx4ac5gw.fsf@pobox.com> (raw)
In-Reply-To: <87y5nuukon.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 11 Jun 2012 13:55:52 +0200")
On Mon 11 Jun 2012 13:55, ludo@gnu.org (Ludovic Courtès) writes:
> What about using copying (or rather, copy-on-write) sub-bytevectors to
> start with? That would avoid the aliasing issue; OTOH COW would make
> the implementation more complex.
Not a bad idea. The FFI can still introduce aliasing, though I don't
know if that matters. Alignment is still a problem though. Plus it's a
bit more complexity, though an optimizer should be able to do something
about that.
I'll see how much work an implementation would be.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-06-11 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 11:07 subbytevectors Andy Wingo
2012-06-09 15:16 ` subbytevectors Thien-Thi Nguyen
2012-06-09 17:07 ` subbytevectors Andy Wingo
2012-06-11 11:55 ` subbytevectors Ludovic Courtès
2012-06-11 14:01 ` Andy Wingo [this message]
2012-06-11 15:35 ` subbytevectors Ludovic Courtès
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=87mx4ac5gw.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).