From: Eli Zaretskii <eliz@gnu.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Add a configure option for NATIVE_FULL_AOT?
Date: Tue, 17 Aug 2021 20:13:08 +0300 [thread overview]
Message-ID: <83y2905717.fsf@gnu.org> (raw)
In-Reply-To: <CA+G3_PNC6haycBfZVmqNG7dBRMtYSEke8sMZ3NHNxH=ntX1CeA@mail.gmail.com> (message from Tom Gillespie on Tue, 17 Aug 2021 09:03:45 -0700)
> From: Tom Gillespie <tgbugs@gmail.com>
> Date: Tue, 17 Aug 2021 09:03:45 -0700
> Cc: Eli Zaretskii <eliz@gnu.org>
>
> > My fear is that this change of concept will delay the release of Emacs
> > 28, because we are moving the carpet under our feet too close to
> > cutting the release branch, and will most probably bump into problems
> > we didn't see until now.
>
> I don't think that there is any change of concept here.
Maybe for you and some others, but it doesn't mean there isn't a
conceptual shift. I've been following the development of the
native-compilation feature for many months, during which we bumped
into and resolved quite a few problems with it, and I can tell you
that some solutions explicitly assumed JIT compilation as the main
paradigm, otherwise they would have made little sense. I just
mentioned some of them up-thread.
> This was one of the original ways to build the eln files and I have
> been using it for over a year.
I'm not talking about you or anyone else personally. The issues we
found depend on many different installation/usage habits and patterns,
and typically rear their heads only on some system configurations. It
is not a coincidence it took us several months to have all the issues
reported, analyzed, and resolved. Some of the solutions required
several iterations of non-trivial changes to code parts that are quite
sensitive, because Emacs runs them early during startup, where not
everything is yet set up.
> I understand the concern, but wouldn't it be better to get the functionality
> out so that we can get more eyeballs/systems using it to see if there are
> any issues?
I'm not against letting this out, I'm just saying that it will
probably delay the release of Emacs 28, which is a pity.
> > Also, please note that the *.eln files are stored without keeping the
> > subdirectory structure below lisp/, they are all lumped in the same
> > directory, unlike the *.elc files. I guess next we will be asked to
> > preserve the tree structure...
>
> We had this conversation almost exactly a year ago as well.
> https://lists.gnu.org/archive/html/emacs-devel/2020-08/msg01036.html
> The eln files are architecture specific and should not be stored along
> with the elc files
I didn't say *.eln should be near the *.elc, I said that they maybe
should have the same directory hierarchy as the *.el files, just under
a different root.
> Quite a bit of though and testing have gone in to make sure that
> system wide full AOT compilation works and is distro and packaging
> friendly.
I didn't invest any thought in it, FWIW. For me, it was always a "you
are on your own" option. I didn't even try it, as all of the efforts
went into making the JIT compilation working well and reliably.
next prev parent reply other threads:[~2021-08-17 17:13 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 16:03 Add a configure option for NATIVE_FULL_AOT? Tom Gillespie
2021-08-17 17:13 ` Eli Zaretskii [this message]
2021-08-17 21:52 ` Tom Gillespie
2021-08-18 12:04 ` Eli Zaretskii
2021-08-18 0:33 ` Arthur Miller
-- strict thread matches above, loose matches on Subject: below --
2021-08-17 8:53 Ulrich Mueller
2021-08-17 11:42 ` Eli Zaretskii
2021-08-17 11:56 ` Ulrich Mueller
2021-08-17 12:09 ` Lars Ingebrigtsen
2021-08-17 13:03 ` Eli Zaretskii
2021-08-18 14:44 ` Lars Ingebrigtsen
2021-08-17 12:53 ` Eli Zaretskii
2021-08-17 13:07 ` Arthur Miller
2021-08-17 15:32 ` Yuri D'Elia
2021-08-17 17:01 ` Eli Zaretskii
2021-08-17 17:12 ` Yuri D'Elia
2021-08-17 18:19 ` Eli Zaretskii
2021-08-17 18:33 ` Andreas Schwab
2021-08-17 18:42 ` Eli Zaretskii
2021-08-17 18:46 ` Andreas Schwab
2021-08-17 19:01 ` Eli Zaretskii
2021-08-17 19:05 ` Andreas Schwab
2021-08-17 19:09 ` Eli Zaretskii
2021-08-17 19:36 ` Ulrich Mueller
2021-08-18 0:48 ` Arthur Miller
2021-08-18 7:29 ` Andreas Schwab
2021-08-18 15:43 ` Yuri D'Elia
2021-08-19 0:57 ` Arthur Miller
2021-08-19 7:04 ` tomas
2021-08-19 21:17 ` Arthur Miller
2021-08-20 7:20 ` tomas
2021-08-20 12:06 ` Arthur Miller
2021-08-20 13:13 ` tomas
2021-08-20 19:51 ` Arthur Miller
2021-08-20 20:06 ` tomas
2021-08-20 21:25 ` Arthur Miller
2021-08-21 6:44 ` tomas
2021-08-21 18:20 ` Arthur Miller
2021-08-19 7:13 ` Eli Zaretskii
2021-08-19 21:01 ` Arthur Miller
2021-08-18 2:23 ` Eli Zaretskii
2021-08-18 4:53 ` Tassilo Horn
2021-08-18 12:07 ` Eli Zaretskii
2021-08-19 2:34 ` Richard Stallman
2021-08-19 6:30 ` tomas
2021-08-19 7:07 ` Eli Zaretskii
2021-08-19 7:17 ` Andreas Schwab
2021-08-19 7:46 ` Eli Zaretskii
2021-08-19 7:27 ` tomas
2021-08-19 8:09 ` Eli Zaretskii
2021-08-19 10:05 ` tomas
2021-08-19 10:51 ` Eli Zaretskii
2021-08-19 12:49 ` tomas
2021-08-19 12:52 ` Eli Zaretskii
2021-08-19 13:09 ` tomas
2021-08-18 7:04 ` Ulrich Mueller
2021-08-18 12:12 ` Eli Zaretskii
2021-08-18 7:33 ` tomas
2021-08-18 12:14 ` Eli Zaretskii
2021-08-18 13:32 ` tomas
2021-08-18 13:45 ` Eli Zaretskii
2021-08-18 16:22 ` tomas
2021-08-18 16:26 ` Eli Zaretskii
2021-08-18 16:34 ` tomas
2021-08-18 16:43 ` Eli Zaretskii
2021-08-18 16:56 ` tomas
2021-08-18 17:12 ` Eli Zaretskii
2021-08-18 16:48 ` Stefan Monnier
2021-08-18 17:00 ` tomas
2021-08-18 17:17 ` Eli Zaretskii
2021-08-18 17:34 ` tomas
2021-08-18 19:43 ` Andrea Corallo via Emacs development discussions.
2021-08-19 1:19 ` Stefan Monnier
2021-08-19 7:11 ` Eli Zaretskii
2021-08-19 8:01 ` Andrea Corallo via Emacs development discussions.
2021-08-18 17:04 ` Eli Zaretskii
2021-08-18 19:44 ` Andrea Corallo via Emacs development discussions.
2021-08-19 7:17 ` Eli Zaretskii
2021-08-19 7:52 ` Andrea Corallo via Emacs development discussions.
2021-08-18 14:11 ` Stefan Kangas
2021-08-18 15:54 ` Eli Zaretskii
2021-08-18 19:13 ` Gunnar Horrigmo
2021-08-18 19:24 ` Eli Zaretskii
2021-08-20 8:22 ` Gunnar Horrigmo
2021-08-20 10:47 ` Eli Zaretskii
2021-08-20 13:06 ` Gunnar Horrigmo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y2905717.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tgbugs@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.