From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: limit native compilation - how
Date: Tue, 18 Jan 2022 16:34:04 +0200 [thread overview]
Message-ID: <83mtjtun8j.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoSMZ7p=e0JNDzR5QQnm=pw=kNy9t10LS17+cZesp99tfA@mail.gmail.com> (message from Corwin Brust on Mon, 17 Jan 2022 15:54:55 -0600)
> From: Corwin Brust <corwin@bru.st>
> Date: Mon, 17 Jan 2022 15:54:55 -0600
> Cc: Eli Zaretskii <eliz@gnu.org>, Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
>
> I don't know if it is it safe to simply include the native-lisp folder
> or if this would causes issues for Windows users who do have libgccjib
> but don't have the same CPU as I do. (Locally I have: Intel(R)
> Core(TM) i7-6950X CPU @ 3.00GHz 3.00 GHz) I don't know if the eln
> files are CPU/arch-specific or if this should work fine for (e.g.) i9,
> AMD chips, those with newer chipsets than my x99, and so forth.
This is not about the CPU you have, this is about the CPU-specific
code-tuning options you pass to libgccjit when you natively-compile
the *.el files. Since I find it hard to believe you tweaked
native-comp-compiler-options to pass non-default options to the
compiler, the resulting code should be generic enough to run on any
64-bit machine running Windows (if you build for x86_64) or on any
machine running any version of Windows if you build for x86.
Again, this is the theory. But here we have at leas partial proof
from the fact that Emacs itself runs on all those other systems, since
emacs.exe is compiled and linked by the same utilities used to produce
the *.eln files.
next prev parent reply other threads:[~2022-01-18 14:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 15:42 limit native compilation - how Colin Baxter 😺
2022-01-15 15:58 ` Eli Zaretskii
2022-01-15 16:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 16:38 ` Eli Zaretskii
2022-01-15 16:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 17:55 ` Eli Zaretskii
2022-01-15 18:58 ` Colin Baxter 😺
2022-01-15 19:12 ` Eli Zaretskii
2022-01-15 19:21 ` H. Dieter Wilhelm
2022-01-15 20:31 ` Colin Baxter 😺
2022-01-15 22:15 ` H. Dieter Wilhelm
2022-01-16 7:13 ` Eli Zaretskii
2022-01-16 7:15 ` Eli Zaretskii
2022-01-16 7:41 ` Colin Baxter 😺
2022-01-16 9:26 ` Eli Zaretskii
2022-01-17 19:37 ` H. Dieter Wilhelm
2022-01-17 20:39 ` Colin Baxter 😺
2022-01-16 8:39 ` Eli Zaretskii
2022-01-16 11:30 ` H. Dieter Wilhelm
2022-01-16 11:42 ` Eli Zaretskii
2022-01-16 12:01 ` H. Dieter Wilhelm
2022-01-16 12:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 12:17 ` Eli Zaretskii
2022-01-16 13:24 ` H. Dieter Wilhelm
2022-01-16 13:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 13:52 ` H. Dieter Wilhelm
2022-01-16 13:59 ` Eli Zaretskii
2022-01-16 18:37 ` H. Dieter Wilhelm
2022-01-16 18:46 ` Eli Zaretskii
2022-01-17 13:38 ` H. Dieter Wilhelm
2022-01-17 13:49 ` Eli Zaretskii
2022-01-17 16:11 ` H. Dieter Wilhelm
2022-01-17 16:30 ` Corwin Brust
2022-01-17 19:03 ` H. Dieter Wilhelm
2022-01-17 19:23 ` Corwin Brust
2022-01-17 21:54 ` Corwin Brust
2022-01-18 14:34 ` Eli Zaretskii [this message]
2022-01-18 19:04 ` H. Dieter Wilhelm
2022-01-17 16:55 ` Eli Zaretskii
2022-01-18 2:57 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-18 3:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 21:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-16 22:10 ` Michael Heerdegen
2022-01-16 13:48 ` Eli Zaretskii
2022-01-16 17:08 ` Andy Moreton
2022-01-16 18:09 ` H. Dieter Wilhelm
2022-01-15 17:55 ` Colin Baxter 😺
2022-01-15 16:01 ` 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=83mtjtun8j.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).