unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 10 Dec 2017 19:27:13 +0200	[thread overview]
Message-ID: <83efo2trwu.fsf@gnu.org> (raw)
In-Reply-To: <e3b5c988-cf0f-caa5-7acd-3fb7ea2c883c@cs.ucla.edu> (message from Paul Eggert on Sat, 9 Dec 2017 23:10:43 -0800)

> From: Paul Eggert <eggert@cs.ucla.edu>
> Cc: pipcet@gmail.com, Emacs-devel@gnu.org
> Date: Sat, 9 Dec 2017 23:10:43 -0800
> 
> 1. The Emacs C code should store pointer values only in objects declared to be 
> of type pointer. Otherwise, every time Emacs converted an integer to a pointer, 
> machine code generated by -fcheck-pointer-bounds would disable bounds checking 
> for that pointer (which would defeat the point of bounds checking).
> 
> This is what the first patch does. I like this patch anyway, since it cleans up 
> the Emacs internals a bit and it doesn't significantly affect performance in the 
> typical case where -fcheck-pointer-bounds is not used.

But if we install this patch regardless of -fcheck-pointer-bounds,
then the --with-wide-int build will cease working, won't it?

Thanks for the other explanations.



  reply	other threads:[~2017-12-10 17:27 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 [this message]
2017-12-11  7:54           ` Paul Eggert
2017-12-11 15:26             ` Eli Zaretskii
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83efo2trwu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).