all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: acm@muc.de, 69071@debbugs.gnu.org
Subject: bug#69071: Emacs master branch: c-ts-mode is slow with large C functions.
Date: Sun, 25 Feb 2024 07:48:00 +0200	[thread overview]
Message-ID: <86jzmtxffz.fsf@gnu.org> (raw)
In-Reply-To: <ECD08FB7-2737-4D6E-A738-7BB20A4BE1F5@gmail.com> (message from Yuan Fu on Sat, 24 Feb 2024 12:35:50 -0800)

> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 24 Feb 2024 12:35:50 -0800
> Cc: acm@muc.de,
>  69071@debbugs.gnu.org
> 
> 
> 
> > On Feb 20, 2024, at 5:55 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> >> From: Yuan Fu <casouri@gmail.com>
> >> Date: Mon, 19 Feb 2024 21:49:26 -0800
> >> Cc: Alan Mackenzie <acm@muc.de>,
> >> 69071@debbugs.gnu.org
> >> 
> >> Before we continue, let me note that this seems like another case where tree-sitter-c parser chokes on some extreme C code. Profiler reports shows that almost all time are spent in treesit-parser-root-node, which indicates that all the time are spent parsing the text.
> > 
> > So maybe this is something to report to tree-sitter and/or
> > tree-sitter-c developers?  (Does c++-ts-mode behave better with this
> > file?)
> 
> We could, but honestly I don’t think they can/want to do anything.

I suggest to report this anyway: we don't have anything to lose, and
there's a chance they would like to do something.

Thanks.





  reply	other threads:[~2024-02-25  5:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 11:30 bug#69071: Emacs master branch: c-ts-mode is slow with large C functions Alan Mackenzie
2024-02-12 13:14 ` Kévin Le Gouguec
2024-02-15  8:36 ` Eli Zaretskii
2024-02-16  4:06   ` Yuan Fu
2024-02-20  5:49     ` Yuan Fu
2024-02-20 13:55       ` Eli Zaretskii
2024-02-24 20:35         ` Yuan Fu
2024-02-25  5:48           ` Eli Zaretskii [this message]
2024-03-01  1:26             ` Yuan Fu
2024-03-01  7:09               ` Eli Zaretskii

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=86jzmtxffz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69071@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=casouri@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.