[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs port to gcc -fcheck-pointer-bounds
From: |
Eli Zaretskii |
Subject: |
Re: Emacs port to gcc -fcheck-pointer-bounds |
Date: |
Fri, 08 Dec 2017 15:45:58 +0200 |
> From: Paul Eggert <address@hidden>
> Date: Wed, 6 Dec 2017 23:34:54 -0800
> Cc: Pip Cet <address@hidden>
>
> In <https://debbugs.gnu.org/29600> 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?
- Emacs port to gcc -fcheck-pointer-bounds, Paul Eggert, 2017/12/07
- Re: Emacs port to gcc -fcheck-pointer-bounds,
Eli Zaretskii <=
- Re: Emacs port to gcc -fcheck-pointer-bounds, Paul Eggert, 2017/12/08
- Re: Emacs port to gcc -fcheck-pointer-bounds, Eli Zaretskii, 2017/12/09
- Re: Emacs port to gcc -fcheck-pointer-bounds, Paul Eggert, 2017/12/10
- Re: Emacs port to gcc -fcheck-pointer-bounds, Eli Zaretskii, 2017/12/10
- Re: Emacs port to gcc -fcheck-pointer-bounds, Paul Eggert, 2017/12/11
- Re: Emacs port to gcc -fcheck-pointer-bounds, Eli Zaretskii, 2017/12/11
- Re: Emacs port to gcc -fcheck-pointer-bounds, Paul Eggert, 2017/12/12
- Re: Emacs port to gcc -fcheck-pointer-bounds, Eli Zaretskii, 2017/12/13
- Re: Emacs port to gcc -fcheck-pointer-bounds, Paul Eggert, 2017/12/13
- Re: Emacs port to gcc -fcheck-pointer-bounds, Stefan Monnier, 2017/12/13