From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: contovob@tcd.ie, rgm@gnu.org, 46818@debbugs.gnu.org
Subject: bug#46818: leim bootstrap: Variable binding depth exceeds max-specpdl-size
Date: Sun, 28 Feb 2021 05:42:27 +0200 [thread overview]
Message-ID: <83y2f8n9i4.fsf@gnu.org> (raw)
In-Reply-To: <jwvft1h5d1p.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 27 Feb 2021 19:02:13 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sat, 27 Feb 2021 19:02:13 -0500
> Cc: Glenn Morris <rgm@gnu.org>, 46818@debbugs.gnu.org
>
> Then again, I had to increase max_specpdl_size from 1600 to 1740 to get
> past that problem, which seems like a higher impact than what I expect
> from this little change in `pcase--if`.
>
> In any case, rather than bump the pdl limit, I suggest the patch below,
> which completely avoids the need to macroexpand all that code we won't
> be using anyway.
I'd rather increase the pdl limit. Having code that subtly evades
using our normal machinery sounds a maintenance headache in the long
run.
Thanks.
next prev parent reply other threads:[~2021-02-28 3:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 18:17 bug#46818: leim bootstrap: Variable binding depth exceeds max-specpdl-size Glenn Morris
2021-02-27 18:34 ` Basil L. Contovounesios
2021-02-27 20:55 ` Stefan Monnier
2021-02-27 21:03 ` Stefan Monnier
2021-02-28 0:01 ` Basil L. Contovounesios
2021-02-28 0:02 ` Stefan Monnier
2021-02-28 0:22 ` Basil L. Contovounesios
2021-02-28 0:51 ` Stefan Monnier
2021-02-28 2:18 ` Basil L. Contovounesios
2021-02-28 2:31 ` Glenn Morris
2021-02-28 3:42 ` Eli Zaretskii [this message]
[not found] ` <87wnusnx0n.fsf@gnus.org>
2021-03-01 17:02 ` Stefan Monnier
2021-02-27 18:44 ` Eli Zaretskii
2021-02-27 18:50 ` Basil L. Contovounesios
2021-02-27 18:51 ` Eli Zaretskii
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=83y2f8n9i4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46818@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.org \
/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).