From: Alan Mackenzie <acm@muc.de>
To: Chris Hecker <checker@d6.com>
Cc: 33670@debbugs.gnu.org
Subject: bug#33670: 26.1; very large c++-mode yank performance regression 25.3_1-x86_64 -> 26.1-x86_64
Date: Sun, 9 Dec 2018 12:01:02 +0000 [thread overview]
Message-ID: <20181209120102.GB4878@ACM> (raw)
In-Reply-To: <CAOdMLc1da--htqCC2+k4qfQDkbOB=SFhp=_nPeyeaTi67gMCug@mail.gmail.com>
Hello, Chris.
On Sat, Dec 08, 2018 at 13:31:42 -0800, Chris Hecker wrote:
> It wasn’t a string, it was a single line function call. Very simple code.
> Like:
> Foo();
Ah. That's worrying. The cause of the slowdown will not be found in
that single line of code, rather in its context.
The way CC Mode works is, at each buffer change, a region around the
change where side effects might propagate is calculated. This region is
then checked for any such side effects. I'm guessing here, but it might
well be that the region in this case has been extended far more than is
necessary.
Is there any way you could get a copy of the file to me, specifying a
line which shows the problem? It's practically impossible to debug
otherwise.
Thanks!
> Chris
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-12-09 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 2:42 bug#33670: 26.1; very large c++-mode yank performance regression 25.3_1-x86_64 -> 26.1-x86_64 Chris Hecker
2018-12-08 2:56 ` bug#33670: adding some info to my yank perf regression Chris Hecker
2018-12-08 7:49 ` bug#33670: 26.1; very large c++-mode yank performance regression 25.3_1-x86_64 -> 26.1-x86_64 Eli Zaretskii
[not found] ` <mailman.5359.1544236991.1284.bug-gnu-emacs@gnu.org>
2018-12-08 20:40 ` Alan Mackenzie
2018-12-08 21:31 ` Chris Hecker
2018-12-09 12:01 ` Alan Mackenzie [this message]
2018-12-09 17:57 ` Chris Hecker
2018-12-09 18:26 ` Alan Mackenzie
2022-01-29 15:20 ` Lars Ingebrigtsen
2022-01-29 16:35 ` Alan Mackenzie
2022-02-28 9:53 ` Lars Ingebrigtsen
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=20181209120102.GB4878@ACM \
--to=acm@muc.de \
--cc=33670@debbugs.gnu.org \
--cc=checker@d6.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 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).