From: Daniel Hartwig <mandyke@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 14599@debbugs.gnu.org, Jan Schukat <shookie@email.de>
Subject: bug#14599: An option to make vector allocation aligned
Date: Fri, 14 Jun 2013 09:33:37 +0800 [thread overview]
Message-ID: <CAN3veRddPmNy=JJ-J85cbhnycXD2X5h8ftjmJu5J9fKTxAfVTg@mail.gmail.com> (raw)
In-Reply-To: <874nd2gmsq.fsf@gnu.org>
On 13 June 2013 21:31, Ludovic Courtès <ludo@gnu.org> wrote:
> Jan Schukat <shookie@email.de> skribis:
>> The other question is the read syntax (one of the primary reasons I'm
>> doing all this). If alignment is something that should be preserved in
>> the permanent representation, you also need to store it in the flags,
>> since the content pointer can be aligned by coincidence. I haven't
>> looked at the compiling of bytevectors yet, to see if alignment can be
>> handled easily there.
>
> I agree that we’d need some sort of annotation to specify the alignment
> of literals, but adding read syntax for that scares me somewhat. What
> do people think?
I agree. The read syntax for vector-ish types in guile is already
large enough. If alignment is important then use a procedural
constructor and query.
Alignment information not need to be printed with the default
representation (read syntax), we dont also print the storage address,
etc..
Regards
next prev parent reply other threads:[~2013-06-14 1:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 13:37 bug#14599: An option to make vector allocation aligned Jan Schukat
2013-06-12 14:59 ` Ludovic Courtès
2013-06-12 15:32 ` Jan Schukat
2013-06-12 21:14 ` Jan Schukat
2013-06-13 13:31 ` Ludovic Courtès
2013-06-14 1:33 ` Daniel Hartwig [this message]
2013-06-14 8:32 ` Jan Schukat
2013-06-14 12:21 ` Ludovic Courtès
2013-06-17 10:04 ` Jan Schukat
2013-06-12 20:37 ` Andy Wingo
2013-06-13 7:07 ` Jan Schukat
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='CAN3veRddPmNy=JJ-J85cbhnycXD2X5h8ftjmJu5J9fKTxAfVTg@mail.gmail.com' \
--to=mandyke@gmail.com \
--cc=14599@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=shookie@email.de \
/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).