From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cpitclaudel@gmail.com, emacs-devel@gnu.org, raman@google.com
Subject: Re: More reliable byte compilation, take 45
Date: Mon, 04 Oct 2021 22:51:14 +0300 [thread overview]
Message-ID: <831r506025.fsf@gnu.org> (raw)
In-Reply-To: <jwvee90k3jm.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 04 Oct 2021 15:18:30 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: "T.V Raman" <raman@google.com>, cpitclaudel@gmail.com,
> emacs-devel@gnu.org
> Date: Mon, 04 Oct 2021 15:18:30 -0400
>
> > Why do you assume that starting from .elc will have fewer problems
> > than starting from .el?
>
> Converting a `.elc` file to a `.eln` file can be done by a pure function
> with no need for any extra information.
I very much doubt that.
> In contrast, converting a `.el` to a `.elc` or `.eln` requires extra
> information (typically extra files that define macros and functions used
> during macro expansion, plus `load-path` settings to find those files, or
> commands to load those files, sometimes in a particular order).
I have no reason to believe that the problems we see with native
compilation are related to these aspects. Do you have evidence of
that?
next prev parent reply other threads:[~2021-10-04 19:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:51 More reliable byte compilation, take 45 Lars Ingebrigtsen
2021-10-04 15:36 ` Clément Pit-Claudel
2021-10-04 16:16 ` Lars Ingebrigtsen
2021-10-04 18:16 ` T.V Raman
2021-10-04 18:21 ` Eli Zaretskii
2021-10-04 19:18 ` Stefan Monnier
2021-10-04 19:51 ` Eli Zaretskii [this message]
2021-10-04 20:13 ` Stefan Monnier
2021-10-05 11:52 ` Eli Zaretskii
2021-10-05 13:27 ` Stefan Monnier
2021-10-05 14:06 ` Adam Porter
2021-10-05 15:41 ` Eli Zaretskii
2021-10-04 16:03 ` Steingold
2021-10-04 17:35 ` Lars Ingebrigtsen
2021-10-04 18:59 ` Steingold
2021-10-05 7:14 ` Lars Ingebrigtsen
2021-10-05 14:50 ` Steingold
2021-10-05 14:51 ` Steingold
2021-10-05 19:30 ` Stefan Monnier
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=831r506025.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.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 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).