From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 33670@debbugs.gnu.org, Chris Hecker <checker@d6.com>
Subject: bug#33670: 26.1; very large c++-mode yank performance regression 25.3_1-x86_64 -> 26.1-x86_64
Date: Sat, 29 Jan 2022 16:35:17 +0000 [thread overview]
Message-ID: <YfVsxbPEk4cgGXXI@ACM> (raw)
In-Reply-To: <87v8y2a7rs.fsf@gnus.org>
Hello, Lars.
On Sat, Jan 29, 2022 at 16:20:07 +0100, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > On Sun, Dec 09, 2018 at 09:57:10 -0800, Chris Hecker wrote:
> >> I think I can send it [the file demonstrating the bug] to you
> >> privately, I’ll mail you off the bug list later today.
> > That would be great. If you want it kept private, that won't be a
> > problem. Thanks!
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
> This was three years ago -- was there any progress on this issue? (And
> do you still see this problem in recent Emacs versions, Chris?)
Unfortunately, there was no further progress at the time. There was a
great deal of C++ raw-string processing and template marking happening,
although Chris told me there was no raw string in the text.
I suspect the bug, whatever it was, will have been fixed since late
2018. The raw string processing has been significantly enhanced since
then.
So, Chris, are the problems still apparent?
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2022-01-29 16:35 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
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 [this message]
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=YfVsxbPEk4cgGXXI@ACM \
--to=acm@muc.de \
--cc=33670@debbugs.gnu.org \
--cc=checker@d6.com \
--cc=larsi@gnus.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).