unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 34910@debbugs.gnu.org
Subject: bug#34910: 27.0.50; Too much matching reentrancy
Date: Sat, 30 Mar 2019 14:05:50 +0100	[thread overview]
Message-ID: <1967BB79-8AD9-41F7-B046-0ECC787FDC3C@acm.org> (raw)
In-Reply-To: <jwv8swwed8l.fsf-monnier+emacs@gnu.org>

30 mars 2019 kl. 13.55 skrev Stefan Monnier <monnier@IRO.UMontreal.CA>:
> 
> It was probably just an oversight, because whether we're searching
> within strings or within buffers the same problems appear with \{N\}
> repetitions (where the counter is stored directly inside the
> regexp-byte-code) and with on-the-fly strength-reduction (where we
> replace some byte-code with cheaper ones (where applicable) on the first
> pass through the regexp).

Is the reentrancy just in preparation for future needs, or is it possible to re-enter the regexp code right now?

If the latter, we may just as well fix the string case here and now; otherwise, I'd like to close the bug.






  reply	other threads:[~2019-03-30 13:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 21:34 bug#34910: 27.0.50; Too much matching reentrancy Mattias Engdegård
2019-03-19  8:05 ` Eli Zaretskii
2019-03-19  9:27   ` Mattias Engdegård
2019-03-19 10:01     ` Eli Zaretskii
2019-03-19 12:25       ` Mattias Engdegård
2019-03-19 12:31         ` Eli Zaretskii
2019-03-30  9:29         ` Eli Zaretskii
2019-03-19 12:50       ` Mattias Engdegård
2019-03-30  9:30         ` Eli Zaretskii
2019-03-30 11:18           ` Mattias Engdegård
2019-03-30 14:52             ` Daniel Colascione
2019-03-30 12:55           ` Stefan Monnier
2019-03-30 13:05             ` Mattias Engdegård [this message]
2019-03-30 13:37               ` Eli Zaretskii
2019-03-30 16:22               ` Stefan Monnier
2019-03-30 17:10                 ` Daniel Colascione
2019-03-30 19:06                   ` Mattias Engdegård

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=1967BB79-8AD9-41F7-B046-0ECC787FDC3C@acm.org \
    --to=mattiase@acm.org \
    --cc=34910@debbugs.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).