From: Drew Adams <drew.adams@oracle.com>
To: "'Help-Gnu-Emacs (help-gnu-emacs@gnu.org)'" <help-gnu-emacs@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: 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 16:14:14 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488AD883FB9294583380DA1F3AE9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: jwv8rglm4oz.fsf-monnier+emacs@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
[Forwarding to the list. For some reason, "Reply All"
with my email client replies only to Stefan.]
-----Original Message-----
Sent: Sunday, February 26, 2023 8:06 AM To: 'Stefan Monnier'
[Caveat: I haven't read the doc and am not familiar
with native compilation. Just commenting on what
I see written here (which is without context). If
what I say helps, good; if not, please ignore.]
> > (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
>
> We want the users to be able to load a `.elc` file even if a `.eln` file
> has been generated. The way the users do that is by giving to
> `load` the file name *with* the `.elc` extension. Of course, they can
> also load the `.eln` file by specifying that file explicitly as well.
If that's not already pointed out explicitly in the
doc, it would help to do so. It can help _greatly_
to understand not only what happens but some of the
logic behind that design. Once someone reads what
you wrote there, things are much clearer, I think.
> If you want to load "the most efficient option available", then just
> don't specify any extension, and Emacs will load the `.el`, `.elc`,
> or `.eln` file according to what it finds.
Again, please point that out explicitly (though this
one will be familiar to longtime Emacs users, as the
same logic has long existed for *.el and *.elc).
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 14821 bytes --]
next prev parent reply other threads:[~2023-02-26 16:14 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 ` Drew Adams [this message]
2023-02-26 16:31 ` FW: [External] : " 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=SJ0PR10MB5488AD883FB9294583380DA1F3AE9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).