unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 55676@debbugs.gnu.org
Subject: bug#55676: [PATCH] non-recursive Lisp reader
Date: Fri, 27 May 2022 19:01:54 +0300	[thread overview]
Message-ID: <83v8trm0b1.fsf@gnu.org> (raw)
In-Reply-To: <DE3A6131-7640-4981-BD60-367B3B5BB6D8@acm.org> (message from Mattias Engdegård on Fri, 27 May 2022 15:33:35 +0200)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 27 May 2022 15:33:35 +0200
> 
> You probably saw this one coming. It's a restructuring of the Lisp reader so that it no longer uses recursion for reading nested data structures.
> 
> The primary motivation is eliminating the limitation of the C stack (and potential overflow crash). As a happy side-effect, the change improves reader performance by a few percent, exact amount depending on what is being read. This translates into a small but measurable speed-up in loading packages (.el and .elc), and in byte-compilation. The performance increase is both from removal of recursion and closer attention to performance.

Thanks.  One minor nit: you seem to have customized indentation in C
source files in a way that is different from our conventions.  Please
reformat using our defaults (which use a mix of TABs and SPACEs).





  parent reply	other threads:[~2022-05-27 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 13:33 bug#55676: [PATCH] non-recursive Lisp reader Mattias Engdegård
2022-05-27 14:03 ` Lars Ingebrigtsen
2022-05-27 16:01 ` Eli Zaretskii [this message]
2022-05-27 16:49   ` Mattias Engdegård
2022-05-27 17:26     ` Eli Zaretskii
2022-05-29  8:27       ` Mattias Engdegård
2022-05-29  1:15   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-29  8:45     ` Mattias Engdegård
2022-05-29  9:09       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-29 10:33         ` Mattias Engdegård
2022-05-30 15:21           ` Mattias Engdegård

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=83v8trm0b1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55676@debbugs.gnu.org \
    --cc=mattiase@acm.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).