From: Tristan Colgate <tcolgate@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Extensible vm ops?
Date: Thu, 9 Aug 2012 08:07:14 +0100 [thread overview]
Message-ID: <CAPGZSGJki-ZEjnMG02MO5XXbbpHAuFx1K94vKmiqr1RjTfYHgA@mail.gmail.com> (raw)
Hi All,
Is it possible, or practical, to support addition of VM ops to the
VM dynamically?
The only use case I am really thinking of is for adding SIMD based
functions for operations on uniform numeric vectors. I realise I could
just take all the funky maths and add it in a C extension, but then
I'm calling out to C, have an extra function call and all that
entails.
Providing a bunch of hard coded SIMD based vector ops might well be
good enough, but I thought a more general solution might be sexier.
I've no idea how such a thing might look though.
--
Tristan Colgate-McFarlane
----
"You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"
next reply other threads:[~2012-08-09 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 7:07 Tristan Colgate [this message]
2012-08-10 15:13 ` Extensible vm ops? Ludovic Courtès
2012-08-26 17:21 ` Stefan Israelsson Tampe
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=CAPGZSGJki-ZEjnMG02MO5XXbbpHAuFx1K94vKmiqr1RjTfYHgA@mail.gmail.com \
--to=tcolgate@gmail.com \
--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).