Re: Emacs port to gcc -fcheck-pointer-bounds

[Eli Zaretskii]

> Cc: address@hidden, address@hidden
> From: Paul Eggert <address@hidden>
> Date: Tue, 12 Dec 2017 15:35:01 -0800
> 
> Here's another way to think about it. Our current practice of defaulting 
> to --enable-check-lisp-object-type for developers is an outgrowth of the 
> fact that integer Lisp_Objects are so error-prone. Unfortunately, this 
> practice is dicey in its own right, as it means developers are dealing 
> with different object code than non-developers. I would favor going back 
> to the old practice of disabling --enable-check-lisp-object-type by 
> default, even for developers, once we've shaken out the change that I 
> just installed. That way, developers and non-developers will default to 
> more-similar machine code.

But using a (fake) pointer is only marginally safer than using an
integer, isn't it?