From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs port to gcc -fcheck-pointer-bounds Date: Mon, 11 Dec 2017 17:26:41 +0200 Message-ID: <83374hthe6.fsf@gnu.org> References: <83indhwcx5.fsf@gnu.org> <83k1xwuwq3.fsf@gnu.org> <83efo2trwu.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1513006222 6580 195.159.176.226 (11 Dec 2017 15:30:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 11 Dec 2017 15:30:22 +0000 (UTC) Cc: pipcet@gmail.com, Emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 11 16:30:16 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eOQ23-0000z1-Ba for ged-emacs-devel@m.gmane.org; Mon, 11 Dec 2017 16:30:15 +0100 Original-Received: from localhost ([::1]:53992 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOQ1y-0003dO-K0 for ged-emacs-devel@m.gmane.org; Mon, 11 Dec 2017 10:30:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOPys-0001gr-AV for Emacs-devel@gnu.org; Mon, 11 Dec 2017 10:26:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eOPyo-0002NE-Dm for Emacs-devel@gnu.org; Mon, 11 Dec 2017 10:26:58 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39899) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eOPyo-0002N9-Aa; Mon, 11 Dec 2017 10:26:54 -0500 Original-Received: from [176.228.60.248] (port=3747 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eOPyn-0005Yt-OX; Mon, 11 Dec 2017 10:26:54 -0500 In-reply-to: (message from Paul Eggert on Sun, 10 Dec 2017 23:54:59 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:220880 Archived-At: > Cc: pipcet@gmail.com, Emacs-devel@gnu.org > From: Paul Eggert > Date: Sun, 10 Dec 2017 23:54:59 -0800 > > Eli Zaretskii wrote: > > But if we install this patch regardless of -fcheck-pointer-bounds, > > then the --with-wide-int build will cease working, won't it? > > No, --with-wide-int still works fine, because it causes LISP_WORDS_ARE_POINTERS > to be false, so src/lisp.h falls back on using EMACS_INT for the basic Lisp > type, just as before. So we will have two different data types implementing a Lisp object, one --with-wide-int and another without it? That sounds suboptimal to me. Why not reserve the new representation to the -fcheck-pointer-bounds builds only? Such builds will anyway be used only by Emacs developers (not even by all of them), and for those who do a different representation won't be a significant obstacle.