From: Nala Ginrut <nalaginrut@gmail.com>
To: Chaos Eternal <eternalchaos@shlug.org>
Cc: Guile User <guile-user@gnu.org>,
Atsuro Hoshino <hoshinoatsuro@gmail.com>,
guile-devel <guile-devel@gnu.org>
Subject: Re: The status of JIT compiler of Guile (was: Guile benchmark)
Date: Tue, 14 Mar 2017 10:35:52 +0800 [thread overview]
Message-ID: <CAPjoZoeKtATCjDaO7KNwfAiKfG_Pz4F3qsA2Y9DqE3t5+=GXrg@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZocq92fHWiFkMapVndKHuHJ7OWzGv=bhmq8Vo8CU2qw+VA@mail.gmail.com>
Rebased to the latest, folks may download the tarball directly
https://github.com/NalaGinrut/guile-tjit/releases/tag/tjit-2.1.8.975-1f6fc-rebase
On Mon, Mar 6, 2017 at 7:19 PM, Nala Ginrut <nalaginrut@gmail.com> wrote:
> I've rebased the latest master (2.1.7.1040-0f7db-dirty) and fixed to work.
> The result become more interesting with the naive case mentioned in my
> earlier mail:
> Chez: 15s
> Guile-JIT: 12s
>
> Alright, we still need to face some problems.
>
> In Atsuro's original design, there're two files should be included
> with Scheme's "include" function in the compiling time. IMO this is
> not a good way, since it'll assume the building path is the same with
> source path. Then it complains jit-code-t.scm and
> compat-x86_64-linux.scm are missing. I've fixed this issue in Makefile
> to make a soft link. In the long term I think it's better to change
> its design to use modules.
>
> And we don't have to generate jit-code-t.scm every time we compile.
> This file is generated by gen-code-t.scm according to GNU-lightning
> header file. Next step, I will move it to script directory and we may
> generate it with guild. It's a standalone script actually.
>
> To be continued.
next prev parent reply other threads:[~2017-03-14 2:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 7:49 The status of JIT compiler of Guile (was: Guile benchmark) Nala Ginrut
2017-03-02 8:31 ` The status of JIT compiler of Guile Andy Wingo
2017-03-07 13:23 ` Ludovic Courtès
2017-03-09 6:59 ` Nala Ginrut
2017-03-09 14:27 ` Andy Wingo
2017-03-10 6:19 ` Nala Ginrut
2017-03-10 8:14 ` Andy Wingo
2017-03-02 9:10 ` The status of JIT compiler of Guile (was: Guile benchmark) Chaos Eternal
2017-03-06 11:19 ` Nala Ginrut
2017-03-14 2:35 ` Nala Ginrut [this message]
2017-03-14 2:37 ` Nala Ginrut
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='CAPjoZoeKtATCjDaO7KNwfAiKfG_Pz4F3qsA2Y9DqE3t5+=GXrg@mail.gmail.com' \
--to=nalaginrut@gmail.com \
--cc=eternalchaos@shlug.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=hoshinoatsuro@gmail.com \
/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).