From: Eli Zaretskii <eliz@gnu.org>
To: Robert Boyer <robertstephenboyer@gmail.com>
Cc: 69480@debbugs.gnu.org
Subject: bug#69480: Emacs Lisp needs, for its great 'native-compile', 'declare' and 'the' for fixnums and arrays.
Date: Fri, 01 Mar 2024 08:45:37 +0200 [thread overview]
Message-ID: <86a5nisb5a.fsf@gnu.org> (raw)
In-Reply-To: <CAP9n0TMu641Kya3Hvg72RnhBOHbv+SokVRzGY=5iQNVC+qD8Lw@mail.gmail.com> (message from Robert Boyer on Thu, 29 Feb 2024 14:54:46 -0600)
> From: Robert Boyer <robertstephenboyer@gmail.com>
> Date: Thu, 29 Feb 2024 14:54:46 -0600
> Cc: 69480@debbugs.gnu.org
>
> > You use benchmark incorrectly.
>
> Huh? Here is the documentation.
>
> benchmark is an interactive native-compiled Lisp function in ‘benchmark.el’.
>
> (benchmark REPETITIONS FORM)
>
> Print the time taken for REPETITIONS executions of FORM.
> Interactively, REPETITIONS is taken from the prefix arg, and
> the command prompts for the form to benchmark.
> For non-interactive use see also ‘benchmark-run’ and
> ‘benchmark-run-compiled’.
> FORM can also be a function in which case we measure the time it takes
> to call it without any argument.
Yes, and in your recipe you reversed the order of the arguments:
(benchmark (build-sieve (expt 10 8)) 1)
> > It takes 16.7 sec on my system.
>
> All of my times come from using a $100 Lenovo Chromebook. How much did your machine
> cost?
I gave my timing as another data point. I have no way of measuring
the timing on your machine, obviously.
next prev parent reply other threads:[~2024-03-01 6:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 19:40 bug#69480: Emacs Lisp needs, for its great 'native-compile', 'declare' and 'the' for fixnums and arrays Robert Boyer
2024-02-29 20:10 ` Eli Zaretskii
2024-02-29 20:54 ` Robert Boyer
2024-02-29 22:10 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 6:45 ` Eli Zaretskii [this message]
2024-02-29 21:04 ` Robert Boyer
2024-03-01 11:28 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:18 ` Andrea Corallo
2024-03-01 12:33 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:45 ` Eli Zaretskii
2024-03-01 13:07 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 13:41 ` Eli Zaretskii
2024-03-01 13:53 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 14:07 ` Andrea Corallo
2024-03-01 14:35 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 16:10 ` Andrea Corallo
2024-03-01 19:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 16:34 ` Eli Zaretskii
2024-03-01 19:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:40 ` Eli Zaretskii
2024-03-01 12:34 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a5nisb5a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69480@debbugs.gnu.org \
--cc=robertstephenboyer@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).