unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dan.colascione@gmail.com>
To: Dimitri Fontaine <dim@tapoueh.org>
Cc: emacs-devel@gnu.org
Subject: Re: Recursive compilation?
Date: Mon, 06 Jun 2011 17:23:30 -0700	[thread overview]
Message-ID: <4DED6F82.5080603@gmail.com> (raw)
In-Reply-To: <m2ipsielhh.fsf@tapoueh.org>

[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]

On 6/6/11 1:46 PM, Dimitri Fontaine wrote:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>>   http://www.emacswiki.org/emacs/byte-code-cache.el
>>
>> That seems nice, but Stefan's simpler solution would do the trick for
>> me, and is something that I think Emacs should do by default.
> 
> Maybe we could arrange things so that byte-code-cache gets included?

The problem is that byte-code-cache doesn't _quite_ work. Sure, it
handles simple cases well enough, but:

1) it deals with dependency cycles by just not compiling certain files;

2) it breaks inexplicably (i.e., I haven't analyzed it) with nxhtml; and

3) [this may be a spurious effect] code compiled using byte-code-cache
somehow seems slower than code compiled the conventional way. When I
looked at cc-mode, I noticed a slight performance hit. I'd have to look
at it again in more detail to see whether I actually found a problem.

Regardless, the mode is an ugly hack. It shadows LOAD and calls the byte
compiler in a way it was never meant to be called. If we're going to
implement a feature like this, we ought to do it right, and that means
making the compiler reentrant and adding the proper hooks to LOAD.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2011-06-07  0:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 20:44 Recursive compilation? Lars Magne Ingebrigtsen
2011-05-31 21:52 ` Stefan Monnier
2011-05-31 22:17   ` Lars Magne Ingebrigtsen
2011-06-01  1:38     ` Stefan Monnier
2011-06-01 11:48       ` Lars Magne Ingebrigtsen
2011-06-01 20:14 ` Dimitri Fontaine
2011-06-03 21:55   ` Lars Magne Ingebrigtsen
2011-06-04  6:29     ` Eli Zaretskii
2011-06-04 15:54       ` Lars Magne Ingebrigtsen
2011-06-04 16:08         ` Eli Zaretskii
2011-06-04 17:50           ` Glenn Morris
2011-06-06 20:05           ` Stefan Monnier
2011-06-09 17:51             ` Lars Magne Ingebrigtsen
2011-06-04 17:48         ` Glenn Morris
2011-06-06 20:46     ` Dimitri Fontaine
2011-06-07  0:23       ` Daniel Colascione [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=4DED6F82.5080603@gmail.com \
    --to=dan.colascione@gmail.com \
    --cc=dim@tapoueh.org \
    --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).