From: "T.V Raman" <raman@google.com>
To: eliz@gnu.org
Cc: raman@google.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Should native compilation be enabled by default?
Date: Tue, 5 Mar 2024 08:03:31 -0800 [thread overview]
Message-ID: <26087.16979.320201.148528@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <86msrcllrc.fsf@gnu.org>
First I am hearing of that ar, glad it is there.
So for the average user, who adds things to that list? Some examples
in the docs -- especially illustrating how to use it to "fix broken
packages" might improve things.
Eli Zaretskii writes:
> > From: "T.V Raman" <raman@google.com>
> > Date: Tue, 5 Mar 2024 07:04:07 -0800
> > Cc: raman@google.com,
> > rms@gnu.org,
> > emacs-devel@gnu.org
> >
> > but users then have to edit files from packages that they didn't
> > write
>
> That's one method of disabling native compilation. If that is not
> appropriate in some cases, we also have
> native-comp-jit-compilation-deny-list to cover those.
--
next prev parent reply other threads:[~2024-03-05 16:03 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 10:56 Native compilation on as default? Andrea Corallo
2024-02-29 13:39 ` Eli Zaretskii
2024-02-29 15:07 ` Andrea Corallo
2024-02-29 16:26 ` Eli Zaretskii
2024-03-02 3:08 ` Should native compilation be enabled by default? Richard Stallman
2024-03-02 7:16 ` Eli Zaretskii
2024-03-05 3:42 ` Richard Stallman
2024-03-05 4:51 ` T.V Raman
2024-03-05 9:31 ` Andrea Corallo
2024-03-05 15:02 ` T.V Raman
2024-03-05 15:39 ` Andrea Corallo
2024-03-05 16:01 ` T.V Raman
2024-03-05 17:03 ` Andrea Corallo
2024-03-05 15:59 ` Suhail Singh
2024-03-05 16:46 ` T.V Raman
2024-03-05 12:25 ` Eli Zaretskii
2024-03-05 15:04 ` T.V Raman
2024-03-05 15:51 ` Eli Zaretskii
2024-03-05 16:03 ` T.V Raman [this message]
2024-03-05 16:37 ` Eli Zaretskii
2024-03-05 16:11 ` Andrea Corallo
2024-03-05 16:47 ` T.V Raman
2024-03-05 9:57 ` Andrea Corallo
2024-03-08 2:29 ` Richard Stallman
2024-03-08 8:13 ` Eli Zaretskii
2024-03-05 12:24 ` Eli Zaretskii
2024-03-08 2:29 ` Richard Stallman
2024-03-08 8:28 ` Eli Zaretskii
2024-03-08 2:29 ` Richard Stallman
2024-03-05 20:42 ` Björn Bidar
2024-03-14 17:15 ` Emanuel Berg
2024-03-15 12:44 ` Colin Baxter
2024-03-15 16:01 ` Ihor Radchenko
2024-03-15 13:14 ` Colin Baxter
2024-03-15 13:29 ` Colin Baxter
2024-03-15 13:53 ` Corwin Brust
2024-03-15 15:08 ` Colin Baxter
2024-03-15 15:13 ` Emanuel Berg
2024-03-15 15:15 ` Eli Zaretskii
2024-03-15 16:26 ` Colin Baxter
2024-03-15 17:08 ` Andrea Corallo
2024-03-15 20:35 ` Emanuel Berg
2024-03-16 8:26 ` Eli Zaretskii
2024-03-15 15:21 ` Emanuel Berg
2024-03-15 16:24 ` Andrea Corallo
2024-03-15 16:47 ` Emanuel Berg
2024-03-15 15:13 ` Eli Zaretskii
[not found] ` <87a5ncfm1r.fsf@>
2024-03-08 2:29 ` Richard Stallman
2024-03-08 8:06 ` Eli Zaretskii
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=26087.16979.320201.148528@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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.