From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>,
"Paul Eggert" <eggert@cs.ucla.edu>
Cc: gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: Question about bignum usage
Date: Thu, 20 Jun 2024 13:02:54 +0300 [thread overview]
Message-ID: <868qz0nd81.fsf@gnu.org> (raw)
In-Reply-To: <227390B1-09FC-4FD5-B9E9-2729624A0D13@gmail.com> (message from Mattias Engdegård on Thu, 20 Jun 2024 11:38:48 +0200)
> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Thu, 20 Jun 2024 11:38:48 +0200
> Cc: Gerd Möllmann <gerd.moellmann@gmail.com>,
> emacs-devel@gnu.org
>
> 20 juni 2024 kl. 09.36 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > This means we check for expired times every 100 msec, so yes, we will
> > create a lot of bignums.
>
> Right, and a few hundred bignums allocated every second isn't something even the current GC should have any trouble with.
>
> But it is a bit wasteful, isn't it? We use very short-lived bignums for internal purposes even when the picosecond part is 0, in places like decode_timer where there should be need to cons anything at all.
Sure, if that can be avoided, it would be beneficial. Paul, any
suggestions?
next prev parent reply other threads:[~2024-06-20 10:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 5:59 Question about bignum usage Gerd Möllmann
2024-06-20 6:26 ` Eli Zaretskii
2024-06-20 6:34 ` Gerd Möllmann
2024-06-20 7:36 ` Eli Zaretskii
2024-06-20 8:35 ` Gerd Möllmann
2024-06-20 13:07 ` Gerd Möllmann
2024-06-20 13:43 ` Helmut Eller
2024-06-20 14:17 ` Gerd Möllmann
2024-06-20 18:32 ` Gerd Möllmann
2024-06-20 18:37 ` Gerd Möllmann
2024-06-20 18:58 ` Eli Zaretskii
2024-06-20 19:16 ` Gerd Möllmann
2024-06-20 19:25 ` Eli Zaretskii
2024-06-20 19:42 ` Gerd Möllmann
2024-06-20 9:38 ` Mattias Engdegård
2024-06-20 10:02 ` Eli Zaretskii [this message]
2024-07-11 14:10 ` Paul Eggert
2024-07-13 9:43 ` Mattias Engdegård
2024-07-14 4:34 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868qz0nd81.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=mattias.engdegard@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.