From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: data-crunching in guile
Date: Thu, 25 Jun 2009 10:04:42 +0200 [thread overview]
Message-ID: <86r5x891t1.fsf@gnu.org> (raw)
In-Reply-To: m3ljnhon41.fsf@pobox.com
Hi,
Andy Wingo <wingo@pobox.com> writes:
> What I'm getting at is that I think we should have VM ops for working on
> vectors -- both generic vectors, and specific ops for bytevectors, and
> probably an op for string-ref as well, and possibly string-set!. Then a
> native code backend could be effectively implemented to operate on the
> GLIL or assembly level, relying on the Tree-IL compiler's previous
> resolution of high-level operations (i.e., vector-set!) to low-level
> instructions. I think we have the space in the VM, and if we group all
> of the vector instructions at the end, we shouldn't affect the
> instruction cache too much.
Why not, but...
It looks to me like a failure to optimize the general case, which we
work around by specializing the instruction set.
Maybe we could have a more generic approach to the problem. For
instance, there could be a way to annotate primitive procedures with
information useful to the compiler, such as "returns-single-value",
"return-value-unspecified", etc., which would allow the generated code
to take shortcuts. But maybe this is just unrealistic. What do you
think?
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-06-25 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 12:03 data-crunching in guile Andy Wingo
2009-06-25 7:26 ` Neil Jerram
2009-06-25 8:04 ` Ludovic Courtès [this message]
2009-06-25 21:08 ` Andy Wingo
2009-06-25 22:47 ` Neil Jerram
2009-06-26 14:37 ` Andy Wingo
2009-06-26 21:25 ` Neil Jerram
2009-06-26 12:09 ` 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=86r5x891t1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).