From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: FW: [External] : Re: Native compilation by default?: Was [Re: stats say SBCL is 78 875 % faster than natively compiled Elisp
Date: Sun, 26 Feb 2023 21:05:10 +0100 [thread overview]
Message-ID: <87zg90ur9l.fsf@dataswamp.org> (raw)
In-Reply-To: 83bklgi6yc.fsf@gnu.org
Eli Zaretskii wrote:
>> And the doc makes clear that `M-x load-file FOO.el' or
>> (load-file "FOO.el") loads FOO.el.
>
> No, it doesn't.
We need like a native compile FAQ to answer more basic
questions, in a simple way.
1. When does it happen to an individual file without you
doing anything?
2. How do you explicitely native compile stuff, from
a Makefile as well as from Emacs?
3. How do you load it?
4. How much faster is it than byte-compiled code? Is it around
7% as the test say? Why is it still so much slower than
SBCL which is 78 875% faster? Is it because Elisp has
dynamic typing and the compiler also lacks optimizations
that, perhaps, will come in time?
5. (And so on.)
I can answer question 2, see these files:
https://dataswamp.org/~incal/emacs-init/native.el
https://dataswamp.org/~incal/emacs-init/Makefile
I can also answer 3: In each file f, do
(provide 'f)
last, then `native-compile' it, then do (load "f").
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-02-26 20:05 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 [this message]
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=87zg90ur9l.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).