From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Native compilation on as default?
Date: Fri, 09 Jun 2023 14:23:40 +0300 [thread overview]
Message-ID: <83legs281v.fsf@gnu.org> (raw)
In-Reply-To: <yp14jni9wdf.fsf@fencepost.gnu.org> (message from Andrea Corallo on Thu, 08 Jun 2023 04:44:12 -0400)
> From: Andrea Corallo <acorallo@gnu.org>
> Date: Thu, 08 Jun 2023 04:44:12 -0400
>
> native compilation was off by default in 28 and same will be for 29. I
> believe the 28 series proved this feature to be stable.
>
> Also I read a number of dristros (Fedora, Debian, openSUSE, Arch,
> Gentoo, NixOS, Guix) offer Emacs with native compilation on.
>
> What about having it on as default for emacs 30? In case two scenarios:
>
> 1- On by default when libgccjit is present otherwise off.
>
> 2- On by default and if libgccjit is not present we raise a complain at
> configure time, the user can either install libgccjit or manually
> indicate --with-native-compilation=no.
>
> WDYT?
I'd like to wait with this decision until after Emacs 29.1 is out. We
made several non-trivial changes in native compilation in Emacs 29, so
I'd like to see how it fares and how it is received by the community.
This decision isn't urgent yet, since Emacs 30 will not be released
soon enough to begin worry now.
next prev parent reply other threads:[~2023-06-09 11:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 8:44 Native compilation on as default? Andrea Corallo
2023-06-09 11:23 ` Eli Zaretskii [this message]
2023-06-09 16:56 ` Andrea Corallo
2023-06-09 17:22 ` Eli Zaretskii
2023-10-25 14:11 ` Andrea Corallo
2023-10-25 14:18 ` Eli Zaretskii
2023-10-25 14:42 ` Stefan Kangas
2023-10-25 20:50 ` Andrea Corallo
2023-10-25 21:22 ` Stefan Kangas
2023-10-25 21:33 ` Andrea Corallo
2023-10-25 22:48 ` Stefan Kangas
2023-10-26 0:32 ` Po Lu
2023-10-26 6:39 ` Eli Zaretskii
2023-10-26 3:47 ` Dr. Arne Babenhauserheide
2023-10-26 7:13 ` Eli Zaretskii
2023-10-26 4:58 ` Eli Zaretskii
2023-11-20 9:41 ` Andrea Corallo
2023-11-20 12:20 ` Eli Zaretskii
2023-11-20 22:21 ` Emanuel Berg
2023-11-21 10:39 ` Andrea Corallo
2023-11-21 10:38 ` Andrea Corallo
2023-10-26 2:27 ` Richard Stallman
2023-10-26 3:55 ` brickviking
2023-10-26 7:20 ` Eli Zaretskii
2023-10-26 7:36 ` Colin Baxter
2023-10-26 9:41 ` Andrea Corallo
2023-10-26 12:07 ` Colin Baxter
2023-10-26 12:14 ` Andrea Corallo
2023-10-26 13:02 ` Eli Zaretskii
2023-10-27 7:08 ` Colin Baxter
2023-10-26 14:22 ` Emanuel Berg
2023-10-27 14:41 ` Gregor Zattler
2023-10-26 6:44 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2024-02-29 10:56 Andrea Corallo
2024-02-29 13:39 ` Eli Zaretskii
2024-02-29 15:07 ` Andrea Corallo
2024-02-29 16:26 ` 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
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=83legs281v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acorallo@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).