unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: John Wiegley <johnw@gnu.org>, 36216@debbugs.gnu.org
Subject: bug#36216: 27.0.50; Variable binding depth exceeds max-specpld-size during bootstrap
Date: Sun, 16 Jun 2019 21:49:29 +0200	[thread overview]
Message-ID: <CAAeL0SQROCzVS4P5jRpqDOg6P8V1U-BoHg+iaRXx06wTnGdnzA@mail.gmail.com> (raw)
In-Reply-To: <jwvh88p8h53.fsf-monnier+emacs@gnu.org>

> That pcase situation is different (not only because pcase is not
> pre-loaded, contrary to cl-generic, but also because this trick is used
> to break a circular dependency, rather than to minimize stack depth).

Still, the trick of skipping the macro-expansion sort of worked with
cl-generic, on normal compilations. Broke bootstrapping. And I accept
it was a bit gross.

> We've been increasing the stack size bit by bit for a long time now
> (and IIRC max-specpld-size is not allocated on the C stack, so we can
> go crazy without any risk of crashing on a small C stack), so:
> No objection from me.

Ok, I'll commit it.

> I do wonder what caused the increase of stack depth, tho: I can't
> remember offhand anything recent that would explain it in this part of
> the code.

The problem does not happen (at least on Windows) on the release branch.

In this case, with max-specpdl-size = 1300 it was working, now it
requires on the order of 1435 or so, which is at least a 10% increment
(likely a bit more, assuming it didn't need exactly 1300 before).
That's not very big, but certainly significant.





  reply	other threads:[~2019-06-16 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-15  0:53 bug#36216: 27.0.50; Variable binding depth exceeds max-specpld-size during bootstrap Juanma Barranquero
2019-06-15  6:29 ` Eli Zaretskii
2019-06-15 10:00   ` Juanma Barranquero
2019-06-15 10:13     ` Eli Zaretskii
2019-06-16  5:57       ` Juanma Barranquero
2019-06-16 12:01         ` Juanma Barranquero
2019-06-16 14:04           ` Eli Zaretskii
2019-06-16 14:17             ` Juanma Barranquero
2019-06-16 14:20               ` Eli Zaretskii
2019-06-16 19:34                 ` Stefan Monnier
2019-06-16 19:49                   ` Juanma Barranquero [this message]
2019-06-16 21:22                     ` Juanma Barranquero
2019-06-27 20:17                       ` Juanma Barranquero
2019-06-16 21:32                     ` Stefan Monnier
2019-06-15 11:22 ` Lars Ingebrigtsen
2019-06-16  6:01   ` Juanma Barranquero

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=CAAeL0SQROCzVS4P5jRpqDOg6P8V1U-BoHg+iaRXx06wTnGdnzA@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=36216@debbugs.gnu.org \
    --cc=johnw@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).