From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Making --with-wide-int the default Date: Fri, 16 Oct 2015 11:24:35 +0200 Message-ID: <87lhb3tbcc.fsf@fencepost.gnu.org> References: <83egpruiyp.fsf@gnu.org> <54E0FF93.2000104@dancol.org> <5610ED13.1010406@dancol.org> <56117F37.9060808@dancol.org> <83oag087gs.fsf@gnu.org> <83oafz70im.fsf@gnu.org> <5620AF43.4050401@cs.ucla.edu> <83k2qn6xfm.fsf@gnu.org> <5620B4FA.1000804@cs.ucla.edu> <87y4f3tdsr.fsf@fencepost.gnu.org> <83a8rj6uu5.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1444987515 955 80.91.229.3 (16 Oct 2015 09:25:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 16 Oct 2015 09:25:15 +0000 (UTC) Cc: lekktu@gmail.com, eggert@cs.ucla.edu, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 16 11:25:10 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zn1Fp-0002Pz-6b for ged-emacs-devel@m.gmane.org; Fri, 16 Oct 2015 11:24:49 +0200 Original-Received: from localhost ([::1]:52078 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zn1Fo-0003lH-HL for ged-emacs-devel@m.gmane.org; Fri, 16 Oct 2015 05:24:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36061) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zn1Fh-0003g5-35 for emacs-devel@gnu.org; Fri, 16 Oct 2015 05:24:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zn1Fg-0006JO-9G for emacs-devel@gnu.org; Fri, 16 Oct 2015 05:24:41 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41446) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zn1Fd-0006GO-GJ; Fri, 16 Oct 2015 05:24:37 -0400 Original-Received: from localhost ([127.0.0.1]:55263 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.82) (envelope-from ) id 1Zn1Fc-0001fv-Kg; Fri, 16 Oct 2015 05:24:36 -0400 Original-Received: by lola (Postfix, from userid 1000) id D9A08E239A; Fri, 16 Oct 2015 11:24:35 +0200 (CEST) In-Reply-To: <83a8rj6uu5.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 16 Oct 2015 12:12:02 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:191727 Archived-At: Eli Zaretskii writes: >> From: David Kastrup >> Cc: Eli Zaretskii , lekktu@gmail.com, emacs-devel@gnu.org >> Date: Fri, 16 Oct 2015 10:31:32 +0200 >> >> I don't it's sensible to configure a non-native default turning >> everything into multiple-register operations and obliterating compact >> data structures matching the architecture's choices. > > We only use 64-bit types in EMACS_INT, i.e. variables that reference > buffer and string positions. All the rest is kept intact. > > What is "non-native" about 'long long int'? > > Do you really use 32-bit GNU/Linux machines? I cannot even easily > find such beasts. Uh, that's not hard. I don't say that my CPU is incapable of going 64bit. But the system is 32bit mainly for disk space reasons (SSD). For a while, I even had a 64bit kernel running with a 32bit userland (which allowed me to create 64-bit executables and test them as well as the default 32-bit executables), but since this computer was given to me as a replacement for a computer where the hardware gave up, I am stuck to now having an NVidia card and the stupid binary-blob driver fails to figure out how to compile in a 64-bit kernel when the userland is 32-bit. So I am currently back again to a 32-bit kernel as well as to a 32-bit system. -- David Kastrup