From: Rocky Bernstein <rb@dustyfeet.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Should wide-int be registered in features?
Date: Thu, 5 Apr 2018 18:12:03 -0400 [thread overview]
Message-ID: <CANCp2gYeDVTmv6Dr6WXQMgrLY22tf2=2vYToz9Oz2oZ74tOSVw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
.. or in system-configuration. And/or shown in emacs-version?
Recently I was reading the thread "Floating-point constant folding in Emacs
byte compiler", and it looks like, as of now, most (or all) of the issues
raised have been resolved in the byte-code optimizer.
Although I'm happy that things are fixed now, there a part of me that asks:
what might have help detection and prevention of such a problem?
I think there should be a simple program to do some sanity checking of
bytecode *before* it gets run to warn of potential problems or worse does
partial execution work and then crashes.
I've mentioned this in the past, but I now realize that I can write such a
lint checker in Elisp Lisp as a side package.
But there are a couple additional features that might be helpful, both in
such a bytecode lint program and independent of that: whether emacs was
built with --with-wide-int.
My understanding of the floating-point-constant bug is that the behavior is
different between optimizaition on builds that differ using this option.
Other things like x-toolkit, gtk, multi-tty, are listed in features. Should
wide-int be something like this?
[-- Attachment #2: Type: text/html, Size: 2501 bytes --]
next reply other threads:[~2018-04-05 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 22:12 Rocky Bernstein [this message]
2018-04-05 22:21 ` Should wide-int be registered in features? Stefan Monnier
2018-04-05 22:34 ` rocky
2018-04-05 22:41 ` Noam Postavsky
2018-04-05 22:46 ` rocky
2018-04-06 0:56 ` Stefan Monnier
2018-04-06 6:28 ` Andreas Schwab
2018-04-06 6:30 ` Ulrich Mueller
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='CANCp2gYeDVTmv6Dr6WXQMgrLY22tf2=2vYToz9Oz2oZ74tOSVw@mail.gmail.com' \
--to=rb@dustyfeet.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).