master b5130367704: * lisp/loadup.el: Don't accidentally reduce `max-lisp-eval-depth`

[Stefan Monnier]

branch: master
commit b513036770499cf7981957d6f5f1626b0b5ef45d
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Commit: Stefan Monnier <monnier@iro.umontreal.ca>

    * lisp/loadup.el: Don't accidentally reduce `max-lisp-eval-depth`
---
 lisp/loadup.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/loadup.el b/lisp/loadup.el
index 7044a629848..532d2ca176d 100644
--- a/lisp/loadup.el
+++ b/lisp/loadup.el
@@ -103,7 +103,7 @@
       ;; During bootstrapping the byte-compiler is run interpreted
       ;; when compiling itself, which uses a lot more stack
       ;; than usual.
-      (setq max-lisp-eval-depth 3400)))
+      (setq max-lisp-eval-depth (max max-lisp-eval-depth 3400))))
 
 (if (eq t purify-flag)
     ;; Hash consing saved around 11% of pure space in my tests.