From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: pipcet@gmail.com, Emacs-devel@gnu.org
Subject: Re: Emacs port to gcc -fcheck-pointer-bounds
Date: Mon, 11 Dec 2017 17:26:41 +0200 [thread overview]
Message-ID: <83374hthe6.fsf@gnu.org> (raw)
In-Reply-To: <ae5aff1b-82b8-a830-edc5-1f3c87541425@cs.ucla.edu> (message from Paul Eggert on Sun, 10 Dec 2017 23:54:59 -0800)
> Cc: pipcet@gmail.com, Emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> 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.
next prev parent reply other threads:[~2017-12-11 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 7:34 Emacs port to gcc -fcheck-pointer-bounds Paul Eggert
2017-12-08 13:45 ` Eli Zaretskii
2017-12-08 22:06 ` Paul Eggert
2017-12-09 8:33 ` Eli Zaretskii
2017-12-10 7:10 ` Paul Eggert
2017-12-10 17:27 ` Eli Zaretskii
2017-12-11 7:54 ` Paul Eggert
2017-12-11 15:26 ` Eli Zaretskii [this message]
2017-12-12 23:35 ` Paul Eggert
2017-12-13 16:20 ` Eli Zaretskii
2017-12-13 18:30 ` Paul Eggert
2017-12-13 19:17 ` Stefan Monnier
2017-12-13 19:39 ` Paul Eggert
2017-12-18 2:47 ` Paul Eggert
2017-12-08 16:13 ` Pip Cet
2017-12-08 22:09 ` Paul Eggert
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=83374hthe6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=pipcet@gmail.com \
/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.