From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org
Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org
Subject: Re: windows build help
Date: Sun, 15 Oct 2017 23:49:49 -0700 [thread overview]
Message-ID: <ba0436b3-19c9-0e6e-0586-ff3508b7ff5b@cs.ucla.edu> (raw)
In-Reply-To: <E1e3uax-0005G6-Tq@fencepost.gnu.org>
> > one can write Elisp code that compiles to different .elc files
> > depending whether the compiling Emacs is built for a 32 or 64 bit machine,
>
> Just for curiosity's sake, would anyone like to tell me what circumstances
> this happens in?
For example, given this source code:
(defconst x (* 32768 32768))
On a 64-bit machine, byte-compiling generates an .elc file containing this:
(defconst x 1073741824)
On a 32-bit machine, byte-compiling the same source code generates an .elc file
containing this instead:
(defconst x 0)
due to multiplication overflow in this Emacs's integers, which use 30-bit two's
complement. Each .elc file is correct for the Emacs it is built with, but
incorrect for the other Emacs.
GNU Emacs source code should not do this sort of thing, since the .elc files
distributed in its tarballs are supposed to be portable.
next prev parent reply other threads:[~2017-10-16 6:49 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 20:02 bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems Vincent Belaïche
2017-09-27 18:36 ` Glenn Morris
2017-09-27 19:07 ` Vincent Belaïche
2017-09-27 19:10 ` Vincent Belaïche
2017-09-27 21:37 ` Glenn Morris
2017-09-28 13:10 ` Andy Moreton
2017-09-29 9:37 ` Eli Zaretskii
2017-10-12 23:06 ` Noam Postavsky
2017-10-13 6:41 ` Eli Zaretskii
2017-10-13 10:14 ` Andy Moreton
2017-10-13 12:22 ` Eli Zaretskii
2017-10-13 13:52 ` Andy Moreton
2017-10-13 14:38 ` Eli Zaretskii
2017-10-13 16:33 ` Noam Postavsky
2017-10-13 17:24 ` Eli Zaretskii
2017-10-13 17:51 ` Noam Postavsky
2017-10-13 18:35 ` Eli Zaretskii
2017-10-13 18:52 ` windows build help Phillip Lord
2017-10-13 19:36 ` Óscar Fuentes
2017-10-13 19:38 ` Stephen Leake
2017-10-14 11:07 ` Phillip Lord
2017-10-14 15:15 ` Stephen Leake
2017-10-14 15:26 ` Phillip Lord
2017-10-14 15:31 ` Eli Zaretskii
2017-10-14 23:04 ` Paul Eggert
2017-10-16 1:53 ` Richard Stallman
2017-10-16 6:49 ` Paul Eggert [this message]
2017-10-16 13:54 ` Stefan Monnier
2017-10-13 19:47 ` Noam Postavsky
2017-10-14 11:09 ` Phillip Lord
2017-10-13 14:09 ` bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems Vincent Belaïche
2017-10-13 14:16 ` Noam Postavsky
2017-10-14 1:40 ` Noam Postavsky
2017-10-16 8:59 ` Vincent Belaïche
2017-10-16 14:23 ` Noam Postavsky
2017-10-16 17:11 ` Vincent Belaïche
2017-10-16 21:42 ` Noam Postavsky
2017-10-19 8:25 ` Vincent Belaïche
2017-11-08 2:37 ` Noam Postavsky
2017-11-08 16:05 ` Eli Zaretskii
2017-11-08 17:42 ` Noam Postavsky
2017-11-08 18:13 ` Eli Zaretskii
2017-11-08 19:23 ` Noam Postavsky
2017-11-08 19:38 ` Eli Zaretskii
2017-11-16 14:40 ` Noam Postavsky
2017-11-16 16:11 ` Eli Zaretskii
2017-11-21 19:44 ` Noam Postavsky
2017-10-16 16:19 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2017-10-14 8:16 windows build help Angelo Graziosi
2017-10-14 11:16 ` Phillip Lord
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=ba0436b3-19c9-0e6e-0586-ff3508b7ff5b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stephen_leake@stephe-leake.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.