From: "T.V Raman" <raman@google.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: Enabling native compilation by default when libgccjit is present
Date: Wed, 08 Dec 2021 09:08:18 -0800 [thread overview]
Message-ID: <p91ee6nuirh.fsf@google.com> (raw)
In-Reply-To: <87czm7wysa.fsf@web.de> (Michael Heerdegen's message of "Wed, 08 Dec 2021 04:39:17 +0100")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1551 bytes --]
Michael Heerdegen <michael_heerdegen@web.de> writes:
Note also that there isn't a 1:1 correspondence between bytecomp
warnings, ie when going from el->elc vs native comp ie when going from
el->eln.
To ensure equivalence I believe we need to go from elc->eln.
The emacs dev contract (implicit) has always been el->elc and developers
should feel responsible for fixing el->elc warnings. But given the
large number of already launched packages, changing that contract now
to say developers should fix el->eln warnings is unlikely to succeed
in the large.
> Po Lu <luangruo@yahoo.com> writes:
>
>> But how are those warnings different from what the user will get if he
>> runs `package-install' on a package that causes warnings from the
>> byte-compiler?
>
> Depends on when these warnings appear. When they appear as normal side
> effect when installing something, they are not different. When they
> appear out of nothing, delayed, from a background process, they are
> different because the user not necessarily knows that they are related
> to the installation.
>
> Most packages installed here were installed before turning native comp
> on. Maybe the experience is different when installing stuff after
> switching, I haven't checked. But lots of regular
> (non-Emacs-developer) users will undergo the same switch some time in
> the future, with already installed packages.
>
> Michael.
>
>
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2021-12-08 17:08 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 19:25 Enabling native compilation by default when libgccjit is present Andrea Corallo
2021-12-02 19:39 ` Eli Zaretskii
2021-12-03 16:52 ` Lars Ingebrigtsen
2021-12-03 18:30 ` Eli Zaretskii
2021-12-03 21:27 ` Lars Ingebrigtsen
2021-12-03 18:53 ` Stefan Kangas
2021-12-03 21:30 ` Lars Ingebrigtsen
2021-12-03 22:39 ` Stefan Kangas
2021-12-04 2:48 ` Lars Ingebrigtsen
2021-12-04 7:48 ` Eli Zaretskii
2021-12-04 19:28 ` Andrea Corallo
2021-12-04 19:41 ` Lars Ingebrigtsen
2021-12-04 19:57 ` Andrea Corallo
2021-12-05 5:04 ` Richard Stallman
2021-12-05 5:09 ` Lars Ingebrigtsen
2021-12-05 5:29 ` Po Lu
2021-12-05 5:31 ` Lars Ingebrigtsen
2021-12-05 5:46 ` Po Lu
2021-12-05 5:48 ` Lars Ingebrigtsen
2021-12-05 6:00 ` Po Lu
2021-12-05 5:54 ` Tim Cross
2021-12-05 8:20 ` Eli Zaretskii
2021-12-05 11:27 ` Stefan Kangas
2021-12-05 14:15 ` Jose A. Ortega Ruiz
2021-12-05 16:52 ` Arthur Miller
2021-12-05 17:42 ` Jose A. Ortega Ruiz
2021-12-05 20:48 ` Arthur Miller
2021-12-05 17:10 ` Óscar Fuentes
2021-12-05 19:25 ` Jose A. Ortega Ruiz
2021-12-05 20:55 ` Óscar Fuentes
2021-12-05 22:59 ` Stefan Monnier
2021-12-05 19:40 ` Lars Ingebrigtsen
2021-12-05 20:02 ` Eli Zaretskii
2021-12-05 20:32 ` Lars Ingebrigtsen
2021-12-05 23:03 ` Stefan Monnier
2021-12-05 23:05 ` Lars Ingebrigtsen
2021-12-05 23:27 ` Stefan Monnier
2021-12-05 20:37 ` Óscar Fuentes
2021-12-05 21:44 ` Arthur Miller
2021-12-05 21:48 ` Lars Ingebrigtsen
2021-12-05 22:58 ` Arthur Miller
2021-12-05 21:15 ` Arthur Miller
2021-12-06 4:33 ` Richard Stallman
2021-12-06 12:59 ` Eli Zaretskii
2021-12-06 13:57 ` Stefan Monnier
2021-12-06 14:08 ` Eli Zaretskii
2021-12-07 16:02 ` Matt Armstrong
2021-12-07 16:55 ` tomas
2021-12-07 17:02 ` T.V Raman
2021-12-05 20:00 ` Jim Myhrberg
2021-12-06 1:03 ` Dmitry Gutov
2021-12-06 2:50 ` Jim Myhrberg
2021-12-06 12:59 ` Dmitry Gutov
2021-12-07 0:34 ` João Pedro de Amorim Paula
2021-12-08 4:34 ` Richard Stallman
2021-12-09 17:00 ` David Koppelman
2021-12-06 4:33 ` Richard Stallman
2021-12-03 22:34 ` Michael Heerdegen
2021-12-04 7:26 ` Eli Zaretskii
2021-12-07 4:38 ` Michael Heerdegen
2021-12-07 5:02 ` Michael Heerdegen
2021-12-07 13:59 ` Eli Zaretskii
2021-12-08 2:31 ` Michael Heerdegen
2021-12-08 9:55 ` Robert Pluim
2021-12-09 0:56 ` Michael Heerdegen
2021-12-08 12:52 ` Eli Zaretskii
2021-12-08 8:16 ` Andreas Schwab
2021-12-08 13:21 ` Eli Zaretskii
2021-12-09 0:29 ` Michael Heerdegen
2021-12-09 4:49 ` Stefan Monnier
2021-12-09 5:27 ` Michael Heerdegen
2021-12-09 10:22 ` Andrea Corallo
2021-12-09 13:14 ` Stefan Monnier
2021-12-09 22:28 ` Michael Heerdegen
2021-12-09 22:50 ` Michael Heerdegen
2021-12-10 8:06 ` Eli Zaretskii
2021-12-11 3:11 ` Michael Heerdegen
2021-12-07 13:53 ` Eli Zaretskii
2021-12-08 2:25 ` Michael Heerdegen
2021-12-08 2:40 ` Po Lu
2021-12-08 3:39 ` Michael Heerdegen
2021-12-08 12:55 ` Eli Zaretskii
2021-12-08 17:08 ` T.V Raman [this message]
2021-12-08 13:52 ` Stefan Monnier
2021-12-08 14:31 ` Eli Zaretskii
2021-12-09 7:19 ` Óscar Fuentes
2021-12-08 12:51 ` Eli Zaretskii
2021-12-09 0:44 ` Michael Heerdegen
2021-12-09 4:13 ` Richard Stallman
2021-12-09 9:27 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2021-12-05 17:24 Angelo Graziosi
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=p91ee6nuirh.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).