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: Fri, 08 Dec 2017 15:45:58 +0200 Message-ID: <83indhwcx5.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1512740850 32244 195.159.176.226 (8 Dec 2017 13:47:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 8 Dec 2017 13:47:30 +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 Fri Dec 08 14:47:20 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 1eNIzm-0007zZ-Uj for ged-emacs-devel@m.gmane.org; Fri, 08 Dec 2017 14:47:19 +0100 Original-Received: from localhost ([::1]:37323 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eNIzq-0000wJ-TP for ged-emacs-devel@m.gmane.org; Fri, 08 Dec 2017 08:47:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33303) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eNIz7-0000w0-EJ for Emacs-devel@gnu.org; Fri, 08 Dec 2017 08:46:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eNIz6-0006l6-El for Emacs-devel@gnu.org; Fri, 08 Dec 2017 08:46:37 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39065) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eNIz1-0006fX-8e; Fri, 08 Dec 2017 08:46:31 -0500 Original-Received: from [176.228.60.248] (port=3111 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eNIyz-0002NN-9k; Fri, 08 Dec 2017 08:46:31 -0500 In-reply-to: (message from Paul Eggert on Wed, 6 Dec 2017 23:34:54 -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:220788 Archived-At: > From: Paul Eggert > Date: Wed, 6 Dec 2017 23:34:54 -0800 > Cc: Pip Cet > > In I published patches to port Emacs to the > -fcheck-pointer-bounds option of GCC, so that I can debug Emacs with hardware > pointer bounds checking on platforms that support it (such as the Kaby Lake chip > in my year-old laptop running Ubuntu 17.10). This entails changing the > fundamental Emacs internal word from an integer to a pointer of the same width - > which is not as big a deal as one might think, as the commonly-used EMACS_INT > type does not change and Emacs users and Emacs Lisp programmers should not > notice any change. Thanks. It's a large patch, so I think the discussion could benefit from an overview of the main points of the implementation. In particular, how would this work in a build --with-wide-int?