From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Bignum speedup patch causes crash at startup
Date: Wed, 05 Sep 2018 18:21:00 +0300 [thread overview]
Message-ID: <83lg8gx95v.fsf@gnu.org> (raw)
In-Reply-To: <0ef8eb60-39dc-39cf-12f9-91240f876729@cs.ucla.edu> (message from Paul Eggert on Tue, 4 Sep 2018 17:56:03 -0700)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 4 Sep 2018 17:56:03 -0700
>
> Andy Moreton wrote:
> > Dumping of bignums is not currently required by any emacs code, but it
> > should be supported unless there is some unreasonable difficulty in
> > doing so.
>
> The difficulty seems to be that memory allocation doesn't work for it, at least
> on MS-Windows. Fixing this is low priority, admittedly.
I don't think there's anything that needs to be fixed here. Dumping
pure bignums should not cause any trouble any more than dumping pure
strings. The only issue is that mp_set_memory_functions must be
called before we call any GMP functions that might allocate memory.
next prev parent reply other threads:[~2018-09-05 15:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 14:21 Bignum speedup patch causes crash at startup Andy Moreton
2018-09-04 15:10 ` Eli Zaretskii
2018-09-04 16:24 ` Eli Zaretskii
2018-09-04 18:59 ` Paul Eggert
2018-09-05 2:35 ` Eli Zaretskii
2018-09-05 7:31 ` Paul Eggert
2018-09-04 16:40 ` Paul Eggert
2018-09-04 17:30 ` Eli Zaretskii
2018-09-04 17:37 ` Andy Moreton
2018-09-04 17:50 ` Eli Zaretskii
2018-09-04 19:50 ` Andy Moreton
2018-09-04 21:11 ` Paul Eggert
2018-09-04 22:34 ` Tom Tromey
2018-09-05 0:09 ` Andy Moreton
2018-09-05 0:56 ` Paul Eggert
2018-09-05 15:21 ` Eli Zaretskii [this message]
2018-09-05 15:17 ` Eli Zaretskii
2018-09-04 19:56 ` Andy Moreton
2018-09-04 20:48 ` Paul Eggert
2018-09-05 15:15 ` Eli Zaretskii
2018-09-05 15:40 ` Paul Eggert
2018-09-05 15:50 ` Pip Cet
2018-09-05 16:06 ` 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=83lg8gx95v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.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 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.