From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Python-on-guile
Date: Sat, 24 Apr 2021 14:59:42 +0200 [thread overview]
Message-ID: <CAGua6m2+1su5Nxw=wZexvkkgFkKXnN1aK_6ZaVF1W22OK6JXnQ@mail.gmail.com> (raw)
In-Reply-To: <CAGua6m0=SK8YTOCWurVHm7BzWtYcKCME1eLdp4Wm0MTN7YpvNw@mail.gmail.com>
Actually changing in (language python compile),
(define (letec f)
(let/ec x (f x))))
To
(define-syntax-rule (letec f)
(let/ec x (f x))))
Actually lead to similar speeds as python3.
On Sat, Apr 24, 2021 at 1:26 PM Stefan Israelsson Tampe <
stefan.itampe@gmail.com> wrote:
> Pro tip, when running this on guile the scheme code that it compilse to is
> located in log.txt.
> If you ,opt the resulting code in a guile session you might be able to
> pinpoint issues that
> delays the code execution.
>
> On Sat, Apr 24, 2021 at 12:04 PM Mikael Djurfeldt <mikael@djurfeldt.com>
> wrote:
>
>> (I should perhaps add that my script doesn't benchmark the object system
>> but rather loops, conditionals and integer arithmetic.)
>>
>> Den fre 23 apr. 2021 17:00Mikael Djurfeldt <mikael@djurfeldt.com> skrev:
>>
>>> Hi,
>>>
>>> Yesterday, Andy committed new code to the compiler, some of which
>>> concerned skipping some arity checking.
>>>
>>> Also, Stefan meanwhile committed something called "reworked object
>>> system" to his python-on-guile.
>>>
>>> Sorry for coming with unspecific information (don't have time to track
>>> down the details) but I noticed that my benchmark script written in Python,
>>> and which computes the 20:th Ramanujan number, now runs 60% faster than
>>> before these changes.
>>>
>>> This means that python-on-guile running on guile3 master executes python
>>> code only 2.6 times slower than the CPython python3 interpreter itself. :-)
>>>
>>> Have a nice weekend all,
>>> Mikael
>>>
>>>
next prev parent reply other threads:[~2021-04-24 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 15:00 Python-on-guile Mikael Djurfeldt
2021-04-23 20:41 ` Python-on-guile Linus Björnstam
2021-04-24 10:04 ` Python-on-guile Mikael Djurfeldt
2021-04-24 11:26 ` Python-on-guile Stefan Israelsson Tampe
2021-04-24 12:59 ` Stefan Israelsson Tampe [this message]
2021-04-24 14:41 ` Python-on-guile Stefan Israelsson Tampe
2021-04-24 15:19 ` Python-on-guile Stefan Israelsson Tampe
2021-04-25 8:20 ` Python-on-guile Mikael Djurfeldt
2021-04-25 10:21 ` Python-on-guile Stefan Israelsson Tampe
2021-04-25 8:46 ` Python-on-guile Stefan Israelsson Tampe
2021-04-25 10:54 ` Python-on-guile Dr. Arne Babenhauserheide
2021-04-25 11:54 ` Python-on-guile Vivien Kraus via General Guile related discussions
2021-04-25 10:18 ` Python-on-guile Stefan Israelsson Tampe
2021-04-27 12:29 ` Python-on-guile Nala Ginrut
-- strict thread matches above, loose matches on Subject: below --
2022-02-19 19:36 python-on-guile Stefan Israelsson Tampe
2019-06-14 18:06 python-on-guile Stefan Israelsson Tampe
2019-06-22 21:07 ` python-on-guile Arne Babenhauserheide
2019-06-26 18:45 ` python-on-guile 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='CAGua6m2+1su5Nxw=wZexvkkgFkKXnN1aK_6ZaVF1W22OK6JXnQ@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mikael@djurfeldt.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).