From: Emanuel Berg <incal@dataswamp.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: Tue, 21 Feb 2023 20:57:43 +0100 [thread overview]
Message-ID: <874jrerdu0.fsf@dataswamp.org> (raw)
In-Reply-To: <871qmj7z9e.fsf@dataswamp.org> (Emanuel Berg's message of "Tue, 21 Feb 2023 17:35:09 +0100")
>>> 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.
>
> It doesn't happen when you byte-compile but it also don't
> happen when you load it, or that depends what you mean
> by "load"ing.
Here it says:
Native-Compilation is implemented as a side effect of
byte-compilation (see Byte Compilation). Thus, compiling
Lisp code natively always produces its byte code as well,
and therefore all the rules and caveats of preparing Lisp
code for byte compilation (see Byte-Compilation Functions)
are valid for native-compilation as well. [1]
Maybe it's the source of some of the above confusion regarding
byte-compilation in particular?
[1] https://www.gnu.org/software/emacs/manual/html_node/elisp/Native_002dCompilation-Functions.html
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-02-21 19:57 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 [this message]
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
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=874jrerdu0.fsf@dataswamp.org \
--to=incal@dataswamp.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).