unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Native compilation by default?: Was [Re: stats say SBCL is 78 875 % faster than natively compiled Elisp
Date: Sun, 26 Feb 2023 08:25:32 +0200	[thread overview]
Message-ID: <83k005j63n.fsf@gnu.org> (raw)
In-Reply-To: <m3ilfpceda.fsf@leonis4.robolove.meer.net> (message from Madhu on Sun, 26 Feb 2023 08:38:49 +0530)

> From: Madhu <enometh@meer.net>
> Date: Sun, 26 Feb 2023 08:38:49 +0530
> 
> * Eli Zaretskii <83k00btcsl.fsf @gnu.org> :
> Wrote on Tue, 21 Feb 2023 14:37:14 +0200:
> >> From: Madhu <enometh@meer.net>
> >> Date: Tue, 21 Feb 2023 12:34:21 +0530
> 
> >> Is my understanding of the documentation - that native compilation is
> >> an automatic side effect of byte compiling, wrong?
> >
> > Yes, it's wrong.  Native compilation happens automatically when you
> > _load_ a .elc file, not when you compile it.
> 
> The info manual I was looking at (info "(elisp) Native-Compilation
> Functions") has this text
> 
> 	"Native-Compilation is implemented as a side effect of
> 	byte-compilation"

It goes on by saying

  Thus, compiling Lisp code natively always produces its byte code as well

So the above has nothing to do with _when_ does native compilation
happen.  It just says _how_ it works: by launching a byte-compilation
and using its by-products internally to produce native code.

> In any case maybe I should file a bug? because this the behaviour I
> reported doesn't meet the expectations. In a fresh emacs -Q: the
> following 3 forms all load a fib.elc file from the current directory
> (say "/dev/shm") without producing an eln file. ("doesn't work")
> 
> (byte-compile-file "fib.el" t)  ; doesn't work
> (load-file "fib.elc")           ; doesn't work
> (load "/dev/shm/fib.elc" nil nil t) ; doesn't work

This is a feature, so filing a bug report against it won't be useful.
Think about it: if the above would load a .eln file instead, how would
a Lisp program be able to force Emacs to load a .elc file?

Therefore, when you specify an explicit extension, be it .el or .elc,
Emacs loads that specific file, nothing more, nothing less.  Exactly
like '(load "foo.el")' in previous versions of Emacs always loaded the
.el file, even if the .elc file was available.

> The only form which works seems to be when load is called with a full
> pathname after omitting the ".el" or ".elc" suffix provided there is an
> elc at that location.
> i.e.
> (load "/dev/shm/fib")
> 
> only this form produces an eln file in the user's eln-cache directory.

That's how it is supposed to work.



  parent reply	other threads:[~2023-02-26  6:25 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  7:56 stats say SBCL is 78 875 % faster than natively compiled Elisp Emanuel Berg
2023-02-15  5:04 ` Chen Zhaoyang
2023-02-15 11:37   ` Emanuel Berg
2023-02-15  6:59 ` Jean Louis
2023-02-16  6:04   ` Emanuel Berg
2023-02-17 17:38     ` Jean Louis
2023-02-18 19:54       ` Emanuel Berg
2023-02-18 20:15         ` Emanuel Berg
2023-02-18 20:39           ` Eli Zaretskii
2023-02-18 20:47             ` Emanuel Berg
2023-02-19  6:35               ` Eli Zaretskii
2023-02-21  7:04                 ` Native compilation by default?: Was [Re: " Madhu
2023-02-21 12:37                   ` Eli Zaretskii
2023-02-21 16:35                     ` Emanuel Berg
2023-02-21 19:57                       ` Emanuel Berg
2023-02-21 22:21                       ` Native compilation by default? (was: Re: stats say SBCL is 78 875 % faster than natively compiled Elisp) Emanuel Berg
2023-02-21 23:54                         ` Emanuel Berg
     [not found]                           ` <87h6vetquk.fsf@dataswamp.org>
2023-02-22  1:47                             ` Emanuel Berg
2023-02-23 10:46                         ` Emanuel Berg
2023-02-23 20:18                           ` Jean Louis
2023-02-26  1:05                             ` Emanuel Berg
2023-02-22 12:32                       ` Native compilation by default?: Was [Re: stats say SBCL is 78 875 % faster than natively compiled Elisp Eli Zaretskii
2023-02-26  3:08                     ` Madhu
2023-02-26  4:32                       ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-26  5:15                         ` Emanuel Berg
2023-02-26  6:27                         ` Eli Zaretskii
2023-02-26  7:10                         ` Emanuel Berg
2023-02-26 16:14                         ` FW: [External] : " Drew Adams
2023-02-26 16:31                           ` Eli Zaretskii
2023-02-26 17:12                             ` Drew Adams
2023-02-26 17:31                               ` Eli Zaretskii
2023-02-26 18:29                                 ` Drew Adams
2023-02-26 19:04                                   ` Eli Zaretskii
2023-02-26 20:05                                     ` Emanuel Berg
2023-02-27  8:42                         ` Madhu
2023-03-03 14:55                           ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-26  6:25                       ` Eli Zaretskii [this message]
2023-02-26 16:10                         ` [External] : " Drew Adams
2023-02-19  5:58         ` Jean Louis
2023-02-15 12:36 ` full native compile (was: Re: stats say SBCL is 78 875 % faster than natively compiled Elisp) Emanuel Berg
2023-02-15 14:05   ` Eli Zaretskii

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=83k005j63n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).