From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: acm@muc.de, emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org
Subject: Re: A proposal for the future of open-paren-in-column-0-is-defun-start.
Date: Tue, 07 Apr 2020 17:06:34 +0300 [thread overview]
Message-ID: <83o8s3qtjp.fsf@gnu.org> (raw)
In-Reply-To: <dbce9069-1f97-9c5d-fb68-d4db48360d5d@gmx.at> (message from martin rudalics on Tue, 7 Apr 2020 10:33:58 +0200)
> Cc: acm@muc.de, rms@gnu.org, emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Tue, 7 Apr 2020 10:33:58 +0200
>
> > Actually, we had a few detailed profiles posted which show many levels
> > below "somewhere in jit-lock", at least for CC Mode.
>
> When comparing -O0 with -O3 builds I noticed one additional difference
> with simple repetitions of 'scroll-up' in xdisp.c. The optimized build
> spent 25% of the CPU time consumed collecting garbage, the debug build
> 42%. Does an -O0 build produce more garbage or is it collecting slower?
I think the latter. I don't think --enable-checking causes
significantly more Lisp object to be produced. GC is very recursive,
so optimizations that put variables in registers make it faster.
next prev parent reply other threads:[~2020-04-07 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 13:47 A proposal for the future of open-paren-in-column-0-is-defun-start Alan Mackenzie
2020-04-05 14:33 ` Stefan Monnier
2020-04-05 15:23 ` Alan Mackenzie
2020-04-05 18:39 ` Stefan Monnier
2020-04-06 2:37 ` Richard Stallman
2020-04-06 15:40 ` Stefan Monnier
2020-04-06 16:04 ` Eli Zaretskii
2020-04-06 16:25 ` Stefan Monnier
2020-04-06 16:36 ` Eli Zaretskii
2020-04-06 17:49 ` Stefan Monnier
2020-04-06 18:16 ` Eli Zaretskii
2020-04-06 18:32 ` andres.ramirez
2020-04-07 8:33 ` martin rudalics
2020-04-07 13:47 ` Stefan Monnier
2020-04-07 14:06 ` Eli Zaretskii [this message]
2020-04-06 19:08 ` Dmitry Gutov
2020-04-06 21:42 ` Stefan Monnier
2020-04-06 21:58 ` Dmitry Gutov
2020-04-06 23:44 ` Stefan Monnier
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=83o8s3qtjp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=rudalics@gmx.at \
/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).