From: Sjoerd van Leent <svanleent@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Attempt to create an inline assembler for Guile
Date: Wed, 24 Jun 2015 21:41:25 +0200 [thread overview]
Message-ID: <CACqzbVi-9OU84PvCGP7En7J+ivu1NXm=Ls_NQ16Co16y4QV8UQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Hi All,
In line with my will to create an assembler, I started first by being able
to execute something in memory, using the memory-mapper strategy. I am
aware not all platforms use the same mechanism, but this is a starting
point.
At a later point, an inline assembler can be used by a (more abstract) JIT
engine
I put my repository here:
https://github.com/santidhammo/guile-assembler
Met vriendelijke groet,
Sjoerd
[-- Attachment #2: Type: text/html, Size: 676 bytes --]
next reply other threads:[~2015-06-24 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 19:41 Sjoerd van Leent [this message]
2015-06-25 3:27 ` Attempt to create an inline assembler for Guile Nala Ginrut
2015-06-25 16:10 ` Sjoerd van Leent
2015-07-16 19:17 ` 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='CACqzbVi-9OU84PvCGP7En7J+ivu1NXm=Ls_NQ16Co16y4QV8UQ@mail.gmail.com' \
--to=svanleent@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).