From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: Native compilation: the bird-eye view
Date: Sun, 17 May 2020 12:11:45 +0800 [thread overview]
Message-ID: <87mu67urni.fsf@localhost> (raw)
In-Reply-To: <83ftbzdewp.fsf@gnu.org>
> And for the "non-average" user, who builds Emacs from sources? AFAIU,
> native compilation of all Lisp files takes many hours even on fast
> machines -- won't this be an annoyance if we don't come up with a JIT
> mechanism?
I am using Gentoo and thus compiling pretty much everything from source.
According to my experience so far, compilation takes even more time than
compiling something like chromium. Moreover, I got memory overflow (for
8Gb RAM) when compiling ja-dic.elc. In order to compile that file, I had
to manually fallback to comp-speed 0.
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Date: Sat, 16 May 2020 12:58:11 +0000
>> Cc: emacs-devel@gnu.org
>>
>> > If so, they will have
>> > to be generated on the end-user machines, or perhaps by whoever
>> > prepares the Emacs binary distributions -- assuming that the binary
>> > distributions are sufficiently compatible to allow that,
>> > notwithstanding the differences between the system where the *.eln
>> > files were generated and the system where they will be installed and
>> > used. (I don't know what is the granularity of the binary distros wrt
>> > machine architecture and OS versions -- will that allow to be sure the
>> > *.eln files are compatible with the target system?)
>>
>> Given .eln are just shareds with (almost) no dependecies [1] their
>> degree of compatibility should be higher then the Emacs binary itself.
>
> Well, the "almost" part means we aren't actually sure about this.
> E.g., what about the dependencies related to the GCC version used to
> build libgccjit and compile the .eln files?
>
>> > The next question is whether we want the *.eln files to exist up front
>> > for all the Lisp files on the end-user system, or we want them to be
>> > generated in JIT-like manner, whenever the corresponding Lisp library
>> > is loaded on demand? The answer to this question might then influence
>> > the place where the *.eln files are kept -- the JIT alternative would
>> > suggest to have some kind of cache directory where we put the compiled
>> > files, similar to what Guile does.
>>
>> I suspect that for the average user the best is to have the distribution
>> do all the compilation upfront for him and have deferred compilation
>> handling only additional libraries and packages.
>
> And for the "non-average" user, who builds Emacs from sources? AFAIU,
> native compilation of all Lisp files takes many hours even on fast
> machines -- won't this be an annoyance if we don't come up with a JIT
> mechanism?
>
--
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg
next prev parent reply other threads:[~2020-05-17 4:11 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 11:51 Native compilation: the bird-eye view Eli Zaretskii
2020-05-16 12:58 ` Andrea Corallo
2020-05-16 15:57 ` Paul Eggert
2020-05-16 16:26 ` Eli Zaretskii
2020-05-16 17:03 ` Andrea Corallo
2020-05-16 17:35 ` Eli Zaretskii
2020-05-16 17:44 ` Andrea Corallo
2020-05-16 17:50 ` Eli Zaretskii
2020-05-16 18:26 ` Andrea Corallo
2020-05-16 18:32 ` Eli Zaretskii
2020-05-16 18:41 ` Andrea Corallo
2020-05-18 14:27 ` Andrea Corallo
2020-05-19 5:08 ` ASSI
2020-05-19 16:25 ` Andrea Corallo
2020-05-19 16:37 ` Stefan Kangas
2020-05-19 19:16 ` Andrea Corallo
2020-05-29 17:25 ` Andrea Corallo
2020-06-02 15:16 ` Stefan Monnier
2020-06-03 14:23 ` Andrea Corallo
2020-06-03 14:38 ` Stefan Monnier
2020-08-10 9:23 ` Andrea Corallo via Emacs development discussions.
2020-08-10 12:20 ` Stefan Monnier
2020-08-10 21:34 ` Andrea Corallo via Emacs development discussions.
2020-08-15 10:51 ` Andrea Corallo via Emacs development discussions.
2020-08-15 15:00 ` Eli Zaretskii
2020-08-19 15:01 ` Andrea Corallo via Emacs development discussions.
2020-08-20 0:53 ` tumashu
2020-08-20 8:11 ` Andrea Corallo via Emacs development discussions.
2020-08-23 12:19 ` Andrea Corallo via Emacs development discussions.
2020-08-23 15:37 ` Stefan Monnier
2020-08-23 16:31 ` Andrea Corallo via Emacs development discussions.
2020-08-23 18:20 ` Stefan Monnier
2020-08-24 8:03 ` Andrea Corallo via Emacs development discussions.
2020-08-24 13:31 ` Stefan Monnier
2020-08-24 14:09 ` Andrea Corallo via Emacs development discussions.
2020-08-30 10:18 ` Path for system-wide .eln files (was: Native compilation: the bird-eye view) Ulrich Mueller
2020-08-30 20:50 ` Path for system-wide .eln files Andrea Corallo via Emacs development discussions.
2020-08-30 21:51 ` Stefan Monnier
2020-08-31 19:13 ` Andrea Corallo via Emacs development discussions.
2020-08-31 21:16 ` Ulrich Mueller
2020-09-01 4:28 ` Yuri Khan
2020-09-01 7:16 ` Ulrich Mueller
2020-09-01 8:46 ` tomas
2020-09-04 17:55 ` Andrea Corallo via Emacs development discussions.
2020-09-04 18:25 ` Ulrich Mueller
2020-09-04 19:47 ` Andrea Corallo via Emacs development discussions.
2020-09-04 20:01 ` Ulrich Mueller
2020-09-04 21:42 ` Stefan Monnier
2020-09-04 22:59 ` Ulrich Mueller
2020-09-05 2:58 ` Stefan Monnier
2020-09-05 7:10 ` Ulrich Mueller
2020-09-06 6:24 ` Andrea Corallo via Emacs development discussions.
2020-09-05 7:48 ` Alfred M. Szmidt
2020-05-16 19:11 ` Native compilation: the bird-eye view Yuan Fu
2020-05-17 4:04 ` Ihor Radchenko
2020-05-17 11:18 ` Arthur Miller
2020-05-16 22:09 ` John Wiegley
2020-05-17 4:11 ` Ihor Radchenko [this message]
2020-05-17 7:43 ` Andrea Corallo
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=87mu67urni.fsf@localhost \
--to=yantar92@gmail.com \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).