From: Alan Mackenzie <acm@muc.de>
To: Bastian Beischer <bastian.beischer@gmail.com>
Cc: 30367-done@debbugs.gnu.org
Subject: bug#30367: 26.0.91; CC-Mode: Major slowdown when isearching big C++ file.
Date: Tue, 20 Mar 2018 18:49:47 +0000 [thread overview]
Message-ID: <20180320184947.GA16673@ACM> (raw)
In-Reply-To: <87372a8quy.fsf@gmail.com>
Hello, Bastian.
On Fri, Feb 09, 2018 at 10:16:53 +0100, Bastian Beischer wrote:
> Hello Alan,
> Alan Mackenzie <acm@muc.de> writes:
[ .... ]
> > Would you please try out the following patch on real code, and either
> > confirm to me that it fixes the bug, or tell me what it breaks. Thanks!
> > diff -r e8b2c6141f97 cc-engine.el
> > --- a/cc-engine.el Fri Feb 02 20:34:15 2018 +0000
> > +++ b/cc-engine.el Thu Feb 08 18:39:40 2018 +0000
> > @@ -10547,13 +10547,6 @@
> > (looking-at c-return-key))
> > (setq braceassignp t)
> > nil)
> > - ((and c-has-compound-literals
> > - (eq (char-after) ?,))
> > - (save-excursion
> > - (when (and (c-go-up-list-backward nil lim)
> > - (eq (char-after) ?\())
> > - (setq braceassignp t)
> > - nil)))
> > ((eq (char-after) ?=)
> > ;; We've seen a =, but must check earlier tokens so
> > ;; that it isn't something that should be ignored.
> > [ .... ]
> Yes, this patch fixes the slowdown. But since I don't understand what
> the original commit which introduced the slowdown tried to fix I cannot
> comment on whether or not its the right thing to do within the context
> of that commit.
Thanks for the prompt, positive reply. I'm afraid I can't remember
either, what the original patch was for.
> I will run emacs with the patch included for a while and will let you
> know in case I find any problems!
Nothing heard from you in the meantime. Good!
> Thanks for tackling this so quickly!
Sorry I've not maintained this speed in committing it. I have now
committed the fix, in revision 16559146f9db1b36d5e8b6c92edb5bb36fafdb85,
and I'm closing the bug.
> >> > Cheers
> >> > Bastian
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2018-03-20 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 10:34 bug#30367: 26.0.91; CC-Mode: Major slowdown when isearching big C++ file Bastian Beischer
2018-02-06 10:40 ` Bastian Beischer
[not found] ` <mailman.8662.1517913372.27995.bug-gnu-emacs@gnu.org>
2018-02-07 15:24 ` Alan Mackenzie
[not found] ` <20180207152435.72040.qmail@mail.muc.de>
2018-02-07 15:27 ` Bastian Beischer
2018-02-07 21:21 ` Alan Mackenzie
[not found] ` <20180207212145.GA3963@ACM>
2018-02-07 21:53 ` Bastian Beischer
2018-02-07 22:26 ` Alan Mackenzie
2018-02-07 22:45 ` Bastian Beischer
2018-02-08 17:25 ` Alan Mackenzie
[not found] ` <20180208172558.GA4335@ACM>
2018-02-08 18:42 ` Alan Mackenzie
[not found] ` <20180208184232.GB4335@ACM>
2018-02-09 9:16 ` Bastian Beischer
2018-03-20 18:49 ` Alan Mackenzie [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180320184947.GA16673@ACM \
--to=acm@muc.de \
--cc=30367-done@debbugs.gnu.org \
--cc=bastian.beischer@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.