From: Paul Eggert <eggert@cs.ucla.edu>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "Mattias Engdegård" <mattiase@acm.org>, 34781@debbugs.gnu.org
Subject: bug#34781: 27.0.50; integer in pcase sometimes compared by eq
Date: Thu, 28 Mar 2019 13:33:45 -0700 [thread overview]
Message-ID: <ef1f33b9-512a-56fd-08ba-14ba3f2667f1@cs.ucla.edu> (raw)
In-Reply-To: <87y34y4w81.fsf@web.de>
On 3/28/19 12:47 PM, Michael Heerdegen wrote:
> AFAIU the patch only corrects an optimization (use `memq' instead of
> `member') that doesn't work for bignums. This can never be harmful.
Isn't it harmful if a 64-bit Emacs decides that the optimization is safe
for the fixnum 1000000000 and thus generates the faster code, but the
code is put into an .elc file and then loaded by a 32-bit emacs that
treats 1000000000 as a bignum?
(An alternative to this annoying most-positive-portable-bignum business
would be to require --with-wide-int on all platforms. :-)
next prev parent reply other threads:[~2019-03-28 20:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 15:13 bug#34781: 27.0.50; integer in pcase sometimes compared by eq Mattias Engdegård
[not found] ` <handler.34781.B.15519717565134.ack@debbugs.gnu.org>
2019-03-12 12:24 ` bug#34781: Acknowledgement (27.0.50; integer in pcase sometimes compared by eq) Mattias Engdegård
2019-03-16 19:09 ` bug#34781: 27.0.50; integer in pcase sometimes compared by eq Mattias Engdegård
2019-03-28 18:25 ` Paul Eggert
2019-03-28 19:47 ` Michael Heerdegen
2019-03-28 20:33 ` Paul Eggert [this message]
2019-03-28 21:30 ` Michael Heerdegen
2019-03-28 19:51 ` Mattias Engdegård
2019-03-28 20:30 ` Paul Eggert
2019-03-28 21:51 ` Mattias Engdegård
2019-03-28 22:10 ` Paul Eggert
2019-03-28 22:11 ` Stefan Monnier
2019-03-28 22:20 ` Mattias Engdegård
2019-03-28 22:38 ` Paul Eggert
2019-03-28 23:03 ` Mattias Engdegård
2019-03-29 8:48 ` Eli Zaretskii
2019-03-29 9:52 ` Mattias Engdegård
2019-03-29 12:33 ` Eli Zaretskii
2019-03-28 19:43 ` Michael Heerdegen
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=ef1f33b9-512a-56fd-08ba-14ba3f2667f1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=34781@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=michael_heerdegen@web.de \
/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.