projects / emacs.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ceebf3e) | patch
Don’t debug fset by default
authorPaul Eggert <eggert@cs.ucla.edu>
Thu, 22 Aug 2019 05:19:03 +0000 (22:19 -0700)
committerPaul Eggert <eggert@cs.ucla.edu>
Thu, 22 Aug 2019 05:30:18 +0000 (22:30 -0700)
commit2b552f34892ee3c73f4b5fb5380218dc6ebbf4bb
treea5c875fa6082cb43b403a9bfa0b3ef2b90d93ebctree | snapshot
parentceebf3efbea7faffc01558d88c91250539c737e0commit | diff
Don’t debug fset by default

This GC bug seems to have been fixed, so the check is no longer
needed in production code.  From a suggestion by Pip Cet in:
https://lists.gnu.org/r/emacs-devel/2019-08/msg00316.html
* src/alloc.c (SUSPICIOUS_OBJECT_CHECKING) [!ENABLE_CHECKING]:
Do not define.
(find_suspicious_object_in_range, detect_suspicious_free):
Expand to proper dummy expressions if !SUSPICIOUS_OBJECT_CHECKING.
* src/data.c (Ffset): Convert test to an eassert.
src/alloc.c diff | blob | history
src/data.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.