emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#52157: closed (CC Mode 5.35.1 (Profiler-Report); Objective C support


From: GNU bug Tracking System
Subject: bug#52157: closed (CC Mode 5.35.1 (Profiler-Report); Objective C support extremely slow)
Date: Wed, 01 Dec 2021 15:50:02 +0000

Your message dated Wed, 1 Dec 2021 15:49:20 +0000
with message-id <YaeZgB474OaE6KjZ@ACM>
and subject line Re: bug#52157: CC Mode 5.35.1 (Profiler-Report); Objective C 
support extremely slow
has caused the debbugs.gnu.org bug report #52157,
regarding CC Mode 5.35.1 (Profiler-Report); Objective C support extremely slow
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
52157: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52157
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: CC Mode 5.35.1 (Profiler-Report); Objective C support extremely slow Date: Sun, 28 Nov 2021 16:11:15 +0800
Package: cc-mode

Emacs  : GNU Emacs 29.0.50 (build 358, x86_64-pc-linux-gnu, GTK+ Version 
3.24.30, cairo version 1.17.4)
 of 2021-11-28
Package: CC Mode 5.35.1 (Profiler-Report)
Buffer Style: nil
c-emacs-features: (pps-extended-state col-0-paren posix-char-classes 
gen-string-delim gen-comment-delim syntax-properties 1-bit)

Open src/nsterm.m from Emacs master, and immediately go to line 603.

Once you try to move around after going to line 603, Emacs will lock up
and later become extremely slow.

current state:
==============
(setq
 c-basic-offset 'set-from-style
 c-comment-only-line-offset 'set-from-style
 c-indent-comment-alist 'set-from-style
 c-indent-comments-syntactically-p 'set-from-style
 c-block-comment-prefix 'set-from-style
 c-comment-prefix-regexp 'set-from-style
 c-doc-comment-style 'set-from-style
 c-cleanup-list 'set-from-style
 c-hanging-braces-alist 'set-from-style
 c-hanging-colons-alist 'set-from-style
 c-hanging-semi&comma-criteria 'set-from-style
 c-backslash-column 'set-from-style
 c-backslash-max-column 'set-from-style
 c-special-indent-hook nil
 c-label-minimum-indentation 'set-from-style
 c-offsets-alist nil
 c-buffer-is-cc-mode nil
 c-tab-always-indent t
 c-syntactic-indentation t
 c-syntactic-indentation-in-macros t
 c-ignore-auto-fill '(string cpp code)
 c-auto-align-backslashes t
 c-backspace-function 'backward-delete-char-untabify
 c-delete-function 'delete-char
 c-electric-pound-behavior nil
 c-default-style '((java-mode . "java") (awk-mode . "awk") (other . "gnu"))
 c-enable-xemacs-performance-kludge-p nil
 c-old-style-variable-behavior nil
 defun-prompt-regexp nil
 tab-width 8
 comment-column 32
 parse-sexp-ignore-comments nil
 parse-sexp-lookup-properties nil
 auto-fill-function nil
 comment-multi-line nil
 comment-start-skip nil
 fill-prefix nil
 fill-column 70
 paragraph-start "\f\\|[        ]*$"
 adaptive-fill-mode t
 adaptive-fill-regexp "[        ]*\\([-–!|#%;>*·•‣⁃◦]+[         ]*\\)*"
 )



--- End Message ---
--- Begin Message --- Subject: Re: bug#52157: CC Mode 5.35.1 (Profiler-Report); Objective C support extremely slow Date: Wed, 1 Dec 2021 15:49:20 +0000
Hello again, Po.

On Sun, Nov 28, 2021 at 16:11:15 +0800, Po Lu via CC-Mode-help wrote:
> Package: cc-mode

> Emacs  : GNU Emacs 29.0.50 (build 358, x86_64-pc-linux-gnu, GTK+ Version 
> 3.24.30, cairo version 1.17.4)
>  of 2021-11-28
> Package: CC Mode 5.35.1 (Profiler-Report)
> Buffer Style: nil
> c-emacs-features: (pps-extended-state col-0-paren posix-char-classes 
> gen-string-delim gen-comment-delim syntax-properties 1-bit)

> Open src/nsterm.m from Emacs master, and immediately go to line 603.

> Once you try to move around after going to line 603, Emacs will lock up
> and later become extremely slow.

I've committed a patch to the emacs-28 branch which I'm pretty sure has
fixed it.

The problem was in the code analysis, where a "struct foo {" wasn't
being properly recognised as a type.  A fight ensued between two bits of
code, one of which marked it as a type, the other then unmarking it, in
a fairly tight loop.

Anyhow, I'm closing the bug with this post.  If there're still problems
in the area, we can open it again.

[ .... ].

-- 
Alan Mackenzie (Nuremberg, Germany).


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]