Commit 5959b48e authored by Paul Eggert's avatar Paul Eggert

Default CHECK_LISP_OBJECT_TYPE to "no"

* configure.ac: Go back to not defining CHECK_LISP_OBJECT_TYPE by
default for developer builds, since it is no longer that useful.
We can make it a no-op entirely later, if in practice it's not
that helpful to enable it.
parent b4486de0
......@@ -900,10 +900,9 @@ AC_ARG_ENABLE([gcc-warnings],
AC_ARG_ENABLE([check-lisp-object-type],
[AS_HELP_STRING([--enable-check-lisp-object-type],
[Enable compile-time checks for the Lisp_Object data type,
which can catch some bugs during development.
The default is "no" if --enable-gcc-warnings is "no".])])
if test "${enable_check_lisp_object_type-$gl_gcc_warnings}" != "no"; then
[Enable compile time checks for the Lisp_Object data type,
which can catch some bugs during development.])])
if test "$enable_check_lisp_object_type" = yes; then
AC_DEFINE([CHECK_LISP_OBJECT_TYPE], 1,
[Define to enable compile-time checks for the Lisp_Object data type.])
fi
......
......@@ -38,6 +38,13 @@ interpreter or modules that it uses. If your platform supports it you
can enable it when configuring, e.g., './configure CFLAGS="-g3 -O2
-mmpx -fcheck-pointer-bounds"' on Intel MPX platforms.
** Emacs now normally uses a pointer type instead of an integer type
for the fundamental word in the Emacs Lisp interpreter, to help
catch typos and support -fcheck-pointer-bounds. The 'configure'
option --enable-check-lisp-object-type is therefore no longer as
useful and so is no longer enabled by default in developer builds,
to reduce differences between developer and production builds.
* Startup Changes in Emacs 27.1
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment