From: Ihor Radchenko <yantar92@posteo.net>
To: Emanuel Berg <incal@dataswamp.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Re: Bignum performance (was: Shrinking the C core)
Date: Tue, 15 Aug 2023 15:01:23 +0000 [thread overview]
Message-ID: <87zg2spcxo.fsf@localhost> (raw)
In-Reply-To: <875y5gh075.fsf@dataswamp.org>
Emanuel Berg <incal@dataswamp.org> writes:
>> ;; (declare (type (unsigned-byte 53) reps num z))
>> ...
>> Still ~3x faster compared to Elisp, but not orders
>> of magnitude.
>
> A pretty good optimization! :O
>
> But what kind of optimization is it?
The commented "optimization" is: "Hey, SBCL, do not use bignums. If ints
overflow, so be it".
> Also, what happens if you remove the OPTIMIZE declaration
> as well?
No difference.
> Still, isn't the rule of the "beat the benchmark" game to beat
> it as fast as possible?
Yes, but when CBCL is orders of magnitude faster, it indicates something
conceptually wrong in the algo. 3x is a matter of variation in the
internal details (like extra type checking in Elisp that Po Lu outlined).
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-08-15 15:01 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 6:28 [PATCH] Re: Bignum performance (was: Shrinking the C core) Gerd Möllmann
2023-08-14 6:56 ` Gerd Möllmann
2023-08-14 7:04 ` Ihor Radchenko
2023-08-14 7:35 ` Gerd Möllmann
2023-08-14 8:09 ` Ihor Radchenko
2023-08-14 9:28 ` Gerd Möllmann
2023-08-14 9:42 ` Ihor Radchenko
2023-08-15 14:03 ` Emanuel Berg
2023-08-15 15:01 ` Ihor Radchenko [this message]
2023-08-15 22:21 ` Emanuel Berg
2023-08-15 22:33 ` Emanuel Berg
2023-08-16 4:36 ` tomas
2023-08-16 5:23 ` Emanuel Berg
2023-08-14 16:51 ` Emanuel Berg
2023-08-15 4:58 ` Gerd Möllmann
2023-08-15 14:20 ` Emanuel Berg
2023-08-15 6:26 ` [PATCH] Re: Bignum performance Po Lu
2023-08-15 14:33 ` Emanuel Berg
2023-08-15 17:07 ` tomas
2023-08-15 22:46 ` Emanuel Berg
2023-08-16 1:31 ` Po Lu
2023-08-16 1:37 ` Emanuel Berg
2023-08-16 3:17 ` Po Lu
2023-08-16 4:44 ` tomas
2023-08-16 5:18 ` Gerd Möllmann
2023-08-16 5:35 ` Emanuel Berg
2023-08-18 7:14 ` Simon Leinen
2023-08-19 13:10 ` Emanuel Berg
2023-08-20 5:07 ` Ihor Radchenko
2023-08-20 6:20 ` Emanuel Berg
2023-08-28 5:32 ` Emanuel Berg
2023-09-03 0:48 ` Emanuel Berg
2023-09-03 8:50 ` Ihor Radchenko
2023-09-03 9:05 ` Emanuel Berg
2023-09-03 10:30 ` Elisp native-comp vs. SBCL for inclist-type-hints benchmark (was: [PATCH] Re: Bignum performance) Ihor Radchenko
2023-09-04 1:03 ` Emanuel Berg
2023-09-03 1:57 ` [PATCH] Re: Bignum performance Emanuel Berg
2023-09-04 4:13 ` Emanuel Berg
2023-08-16 5:41 ` Gerd Möllmann
2023-08-16 6:42 ` Po Lu
2023-08-16 8:05 ` Gerd Möllmann
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 9:46 Shrinking the C core Eric S. Raymond
2023-08-09 12:34 ` Po Lu
2023-08-09 15:51 ` Eric S. Raymond
2023-08-09 23:56 ` Po Lu
2023-08-10 1:19 ` Eric S. Raymond
2023-08-10 7:44 ` Eli Zaretskii
2023-08-10 21:54 ` Emanuel Berg
2023-08-11 10:27 ` Bignum performance (was: Shrinking the C core) Ihor Radchenko
2023-08-11 12:10 ` Emanuel Berg
2023-08-11 12:32 ` Ihor Radchenko
2023-08-11 12:38 ` Emanuel Berg
2023-08-11 14:07 ` [PATCH] " Ihor Radchenko
2023-08-11 18:06 ` Emanuel Berg
2023-08-11 19:41 ` Ihor Radchenko
2023-08-11 19:50 ` Emanuel Berg
2023-08-12 8:24 ` Ihor Radchenko
2023-08-12 16:03 ` Emanuel Berg
2023-08-13 9:09 ` Ihor Radchenko
2023-08-13 9:49 ` Emanuel Berg
2023-08-13 10:21 ` Ihor Radchenko
2023-08-14 2:20 ` Emanuel Berg
2023-08-14 7:20 ` Ihor Radchenko
2023-08-11 22:46 ` Emanuel Berg
2023-08-12 8:30 ` Ihor Radchenko
2023-08-12 16:22 ` Emanuel Berg
2023-08-13 9:12 ` Ihor Radchenko
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=87zg2spcxo.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=incal@dataswamp.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.
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).