From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: emacs-devel@gnu.org
Subject: Re: Not using DOC for ELisp files
Date: Sat, 08 Jan 2022 09:08:51 +0200 [thread overview]
Message-ID: <83iluu4scc.fsf@gnu.org> (raw)
In-Reply-To: <d923f7f0-4229-b278-1edc-ad37ab3c7215@raeburn.org> (message from Ken Raeburn on Fri, 7 Jan 2022 17:59:25 -0500)
> Date: Fri, 7 Jan 2022 17:59:25 -0500
> Cc: emacs-devel@gnu.org
> From: Ken Raeburn <raeburn@raeburn.org>
>
> There was an optimization I did, for platforms supporting the "section"
> attribute extension (at least MacOS and the GNU tools on ELF), to group
> together the strings in the object file (and hopefully the executable)
> so that, if the doc strings weren't actually used, none of those pages
> need be paged in from disk, because they aren't intermixed with other
> data (except maybe at the ends of the range). But if that support isn't
> available, the rest should still work fine. And if the non-Lisp doc
> strings amount to less than a megabyte, as I think an earlier email in
> this thread indicated, the memory cost of not doing this apparently
> isn't huge anyway.
Beware: adding new sections to the binary causes problems when the
binary is stripped.
prev parent reply other threads:[~2022-01-08 7:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 1:48 Not using DOC for ELisp files Stefan Monnier
2021-12-28 2:25 ` Po Lu
2021-12-28 3:48 ` Stefan Kangas
2021-12-28 5:39 ` Po Lu
2021-12-28 4:11 ` LdBeth
2021-12-28 5:03 ` Stefan Monnier
2021-12-28 5:38 ` Po Lu
2021-12-28 9:52 ` Phil Sainty
2021-12-28 10:31 ` Po Lu
2021-12-28 12:47 ` Po Lu
2021-12-28 7:10 ` Lars Ingebrigtsen
2021-12-28 3:39 ` Stefan Kangas
2021-12-28 5:10 ` Stefan Monnier
2021-12-28 6:56 ` Lars Ingebrigtsen
2021-12-28 12:44 ` Eli Zaretskii
2021-12-28 17:14 ` Stefan Monnier
2021-12-28 18:17 ` Eli Zaretskii
2021-12-29 0:15 ` Stefan Monnier
2021-12-29 12:30 ` Johann Klähn
2021-12-29 23:08 ` Stefan Monnier
2021-12-29 12:52 ` Eli Zaretskii
2021-12-29 23:23 ` Stefan Monnier
2021-12-30 7:20 ` Eli Zaretskii
2021-12-31 4:19 ` Stefan Monnier
2021-12-31 8:57 ` Eli Zaretskii
2021-12-31 16:16 ` Stefan Monnier
2021-12-31 18:45 ` Eli Zaretskii
2022-01-03 13:48 ` Ken Raeburn
2022-01-03 14:30 ` Eli Zaretskii
2022-01-07 22:59 ` Ken Raeburn
2022-01-08 7:08 ` Eli Zaretskii [this message]
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=83iluu4scc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raeburn@raeburn.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).