all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Roland Winkler" <winkler@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Is compiling autoloads useful?
Date: Fri, 9 Dec 2011 09:11:48 -0600	[thread overview]
Message-ID: <20194.9524.974939.951450@gargle.gargle.HOWL> (raw)
In-Reply-To: <jwvr50dn8h8.fsf-monnier+emacs@gnu.org>

On Fri Dec 9 2011 Stefan Monnier wrote:
> > The Makefile used by the rather old BBDB v2 compiles the file
> > with BBDB autoloads.  Does such a step offer any advantage with a
> > recent version of GNU Emacs?
> 
> It all depends on what gets put in there.  But if you only get calls to
> `autoload' and a few calls to `add-to-list', byte-compilation should not
> make any difference to the speed of the code.

Thanks!

The file bbdb-autoloads.el is much like the various *loaddefs.el in
the lisp directory (which are not compiled either). It contains
a bunch of autoloads only, except for the lines

(provide 'bbdb-autoloads)
(if (and load-file-name (file-name-directory load-file-name))
    (add-to-list 'load-path (file-name-directory load-file-name)))

> Some people have reported that byte-compiling their .emacs makes a
> measurable difference to their Emacs's startup time, tho, so there
> might some advantage, but I must say I don't know where it comes
> from

I'll try to see whether I can get any measureable difference. Yet I
assume if compiling it made a noticable difference, then compiling the
much bigger standard lisp/loaddefs.el should speed up startup yet
more.

Roland



  parent reply	other threads:[~2011-12-09 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 10:15 Is compiling autoloads useful? Roland Winkler
2011-12-09 14:12 ` Stefan Monnier
2011-12-09 15:06   ` Lluís
2011-12-09 15:11   ` Roland Winkler [this message]
2011-12-09 15:22     ` Andreas Schwab
2011-12-09 15:38       ` Roland Winkler

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20194.9524.974939.951450@gargle.gargle.HOWL \
    --to=winkler@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.