all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Should wide-int be registered in features?
Date: Thu, 05 Apr 2018 20:56:42 -0400	[thread overview]
Message-ID: <jwvd0zdgnxv.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 1522967667743-0.post@n8.nabble.com

> "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.

You seem to refer to a known case where you think this would have been
useful, but I don't know what that case is.  AFAIK the recent
discussions were mostly concerned about whether Emacs's integers were
30bit or 62bit, which you can readily test by looking at
most-positive-fixnum or by checking something like (zerop (expt 2 40)).

> 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? 

Why/when would Elisp need to know?  The same slowdown could occur
because of load on the machine.  Similar object size limits could come
from the OS rather than from the way Emacs was compiled.




        Stefan




  parent reply	other threads:[~2018-04-06  0:56 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
2018-04-05 22:41     ` Noam Postavsky
2018-04-05 22:46       ` rocky
2018-04-06  0:56     ` Stefan Monnier [this message]
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=jwvd0zdgnxv.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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.