From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Re: Native compilation
Date: Fri, 24 Dec 2021 03:53:16 +0100 [thread overview]
Message-ID: <87r1a2af37.fsf@zoho.eu> (raw)
In-Reply-To: SJ0PR10MB5488E9E642771F7A100901F4F37F9@SJ0PR10MB5488.namprd10.prod.outlook.com
Drew Adams wrote:
>> Uhm, native code, what's that? Compile for the architecture
>> you're on? But isn't that the natural order of things?
>>
>> Except for special cases when you cross-compile for, say
>> a unit with less CPU power, to run but not compile?
>>
>> And, is that the whole field?
>>
>> No third way of doing it?
>
> The result of Emacs byte-compilation is not
> architecture-dependent. It runs on any architecture that
> Emacs supports. Emacs Lisp has always had the possibility of
> byte-compilation. Native compilation is new, for Emacs Lisp.
We are talking Elisp and not C, OK, wonderful, let's check the
man page for emacs(1) right away ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-12-24 2:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 0:44 [External] : Re: Native compilation Drew Adams
2021-12-24 2:53 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-12-24 4:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-29 13:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 8:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 9:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 12:18 ` Eli Zaretskii
2021-12-31 12:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 12:46 ` Eli Zaretskii
2021-12-31 13:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 13:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 13:37 ` Eli Zaretskii
2021-12-31 13:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-31 13:38 ` Eli Zaretskii
2022-01-09 5:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-09 7:13 ` Eli Zaretskii
2022-01-10 13:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-10 17:51 ` Eli Zaretskii
2022-01-11 13:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-11 17:04 ` Eli Zaretskii
2022-01-12 22:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-12 22:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 7:07 ` Eli Zaretskii
2022-01-13 7:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 7:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 7:05 ` Eli Zaretskii
2022-01-13 7:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=87r1a2af37.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).