unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Theodor Thornhill <theo@thornhill.no>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, casouri@gmail.com, monnier@iro.umontreal.ca
Subject: Re: CC Mode -> Tree sitter challenge
Date: Sat, 05 Nov 2022 15:37:58 +0100	[thread overview]
Message-ID: <87eduhxy9l.fsf@thornhill.no> (raw)
In-Reply-To: <83tu3d34u7.fsf@gnu.org>


Hi again, Eli

> Only in the "go-to-EOB" one, it looks like?  in the others it is 3
> times faster on the average, or what did I miss?
>
> How about benchmarking indentation?  E.g., how long does it take to
> re-indent a large enough function when you add, say, 'if {' at the
> beginning and '}' at the end?

I took the function 'note_mouse_highlight' from xdisp.c, pushed all
lines to column 0 and ran:

Keep in mind that the indentation result is not 100% identical, but I
doubt that will change anything. I'll benchmark everything again when
we're satisfied with the behavior.  This is only 2 evenings worth of
hacking.

(defun xdisp-indent-benchmark (mode)
  (benchmark-run 10
    (progn
      (with-current-buffer (find-file "~/src/tree-sitter-modes/xdispfun.c")
        (funcall mode)
	      (mark-whole-buffer)
        (indent-for-tab-command)
        (undo))
      (kill-buffer "xdispfun.c"))))

;; C-MODE
;; xdisp-indent-benchmark
;; 1: (14.323358754000001 898 7.6331590500000015)
;; 2: (14.027956779 900 7.438876509)
;; 3: (13.631917978 904 7.006082581)

;; C-TS-MODE
;; xdisp-indent-benchmark
;; 1: (9.498073303 54 0.5114733610000002)
;; 2: (9.538100720000001 53 0.5083722219999984)
;; 3: (9.554900124000001 54 0.5174992560000007)


-- 
Theo



  parent reply	other threads:[~2022-11-05 14:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 20:34 CC Mode -> Tree sitter challenge Theodor Thornhill
2022-11-04 20:36 ` Theodor Thornhill
2022-11-04 20:38 ` Stefan Monnier
2022-11-04 20:44   ` Theodor Thornhill
2022-11-04 23:10 ` Yuan Fu
2022-11-05  7:56   ` Theodor Thornhill
2022-11-06  1:01     ` Yuan Fu
2022-11-06  5:54       ` Theodor Thornhill
2022-11-05  9:13 ` Eli Zaretskii
2022-11-05 13:12   ` Theodor Thornhill
2022-11-05 13:31     ` Eli Zaretskii
2022-11-05 13:42       ` Theodor Thornhill
2022-11-05 14:37       ` Theodor Thornhill [this message]
2022-11-05 14:55         ` Eli Zaretskii
2022-11-05 15:06           ` Theodor Thornhill
2022-11-05 15:27             ` Theodor Thornhill
2022-11-05 16:38               ` Theodor Thornhill
2022-11-05 16:43                 ` Eli Zaretskii
2022-11-06  1:13                 ` Yuan Fu
2022-11-06  6:04                   ` Theodor Thornhill
2022-11-07  0:11                     ` Yuan Fu
2022-11-07  8:05                       ` Theodor Thornhill
2022-11-05 14:34   ` Stefan Monnier
2022-11-05 14:46     ` Theodor Thornhill

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=87eduhxy9l.fsf@thornhill.no \
    --to=theo@thornhill.no \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).