From: Andy Moreton <andrewjmoreton@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Bignum speedup patch causes crash at startup
Date: Wed, 05 Sep 2018 01:09:52 +0100 [thread overview]
Message-ID: <8636uo954f.fsf@gmail.com> (raw)
In-Reply-To: 87ftyorixx.fsf@tromey.com
On Tue 04 Sep 2018, Tom Tromey wrote:
>>>>>> "Paul" == Paul Eggert <eggert@cs.ucla.edu> writes:
>
> Paul> Andy Moreton wrote:
>>> Tom added support in commit fb26c9fd69 ("Make purecopy work for
>>> bignums"), so if that causes problems then it may need to be revisited.
>
> Paul> That code is never used and it wouldn't hurt to remove it as per the
> Paul> attached. I'll CC: Tom to see if he has an opinion.
>
> I added it because someone (Andy I think but this illness is affecting
> my memory somewhat) asked for it. It seemed not impossible for
> something to try to dump a bignum. But, if it isn't needed, then IMO
> that's fine.
I mentioned that support for dumping bignums would seems to be a useful
feature, in the sense of not having arbitrary restrictions. Tom added
code to support that (the commit mentioned above).
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.
AndyM
next prev parent reply other threads:[~2018-09-05 0:09 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 [this message]
2018-09-05 0:56 ` Paul Eggert
2018-09-05 15:21 ` Eli Zaretskii
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
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=8636uo954f.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--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 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).