From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: preloading newcomment.el
Date: Mon, 04 Nov 2002 09:45:40 -0500 [thread overview]
Message-ID: <200211041445.gA4EjeT23347@rum.cs.yale.edu> (raw)
In-Reply-To: E188LEh-00036C-00@fencepost.gnu.org
> It adds 16388 bytes of pure storage if byte-compiled normally
> and 3632 if byte-compile-dynamic is used.
>
> What do you think then of preloading it but using byte-compile-dynamic?
It turns out that it doesn't work: byte-compile-dynamic doesn't work
for preloaded files (because the external reference to the code
is read in as 0 (assuming that it is a docstring reference and
will be filled in by Snarf-documentation).
The problem is "fixed" by the patch below, but it's not
a satisfactory fix (it increases the amount of pure storage used)
and I have no idea how to really fix things.
Stefan
Index: src/lread.c
===================================================================
RCS file: /cvsroot/emacs/emacs/src/lread.c,v
retrieving revision 1.301
diff -u -r1.301 lread.c
--- src/lread.c 30 Oct 2002 19:15:17 -0000 1.301
+++ src/lread.c 4 Nov 2002 14:44:09 -0000
@@ -2844,7 +2844,7 @@
this file is described in the DOC-MM.NN file
and Snarf-documentation will fill in the right value later.
For now, replace the whole list with 0. */
- doc_reference = 1;
+ doc_reference = 0;
else
/* We have already called Snarf-documentation, so make a relative
file name for this file, so it can be found properly
next prev parent reply other threads:[~2002-11-04 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 0:11 preloading newcomment.el Stefan Monnier
2002-11-01 9:40 ` Richard Stallman
2002-11-01 16:56 ` Stefan Monnier
2002-11-03 13:56 ` Richard Stallman
2002-11-04 14:45 ` Stefan Monnier [this message]
2002-11-06 4:51 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2012-02-23 17:20 Preloading newcomment.el Stefan Monnier
2012-02-23 17:24 ` Glenn Morris
2012-02-23 21:49 ` 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=200211041445.gA4EjeT23347@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.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).