all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: rocky <rocky@gnu.org>
To: Emacs-devel@gnu.org
Subject: Re: Should wide-int be registered in features?
Date: Thu, 5 Apr 2018 17:34:27 -0500 (CDT)	[thread overview]
Message-ID: <1522967667743-0.post@n8.nabble.com> (raw)
In-Reply-To: <jwvzi2hi9bg.fsf-monnier+gmane.emacs.devel@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Stefan Monnier wrote
>> 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.I don't see why that would be relevant:
>> --with-wide-int should givepretty much the same result as building on a
>> 64bit system.        Stefan

"should" is not the same thing as "does". If I have this correct knowing
this and knowing how the bytecode was created would have been helpful. Are
there more bugs of this nature where setting the option has a differening
behavior? Also, I believe there are performance differences and differences
in capabilities. e.g --with-wide-int adds: 
>  buffer and string size up to 2GB on 32-bit hosts, at the cost of 10% to
> 30% slowdown of Lisp

and how inside of Emacs is one supposed to know if this is in effect? 



--
Sent from: http://emacs.1067599.n8.nabble.com/Emacs-Dev-f108916.html

[-- Attachment #2: Type: text/html, Size: 1494 bytes --]

  reply	other threads:[~2018-04-05 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 22:12 Should wide-int be registered in features? Rocky Bernstein
2018-04-05 22:21 ` Stefan Monnier
2018-04-05 22:34   ` rocky [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1522967667743-0.post@n8.nabble.com \
    --to=rocky@gnu.org \
    --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.