From: Gregor Zattler <telegraph@gmx.net>
To: Emanuel Berg <incal@dataswamp.org>, emacs-devel@gnu.org
Subject: Re: Native compilation on as default?
Date: Fri, 27 Oct 2023 16:41:32 +0200 [thread overview]
Message-ID: <874jict9er.fsf@no.lan> (raw)
In-Reply-To: <87y1fpihup.fsf@dataswamp.org>
Hi Emanuel, Colin, emacs developers,
* Emanuel Berg <incal@dataswamp.org> [2023-10-26; 16:22 +02]:
> Colin Baxter wrote:
>> Well, I do have libjccjit-6-dev on a machine running Debian
>> 9.13. This is the machine on which I did try native
>> compilation. As I said, I could see zero change in
>> performance of my emacs (30.0.50). There's also libjccjit-8
>> on another machine of mine running Debian 10.13.
>
> Strange you do not experience it being faster, maybe a more
> recent Debian could be the explanation. I just upgraded my
> stable Debian and am now on Debian 12.2, so 9.13 and 10.13 are
> quite old, on the other hand we have the same GNU Emacs
> 30.0.50 so it can't be that :)
>
> libgccjit-12-dev
>
> gcc (Debian 12.2.0-14) 12.2.0
>
> So maybe one should aim for the twelve then.
I started using native compilation with Debian 11 /
libgccjit-8-dev and the effect was just notable to me.
But since I upgraded to Debian 12 / libgccjit-12-dev
Emacs feels much more snappy, also starts faster. Even
the compilation process is faster than under Debian 11.
Thanks, Andrea.
Ciao; Gregor
next prev parent reply other threads:[~2023-10-27 14:41 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
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 [this message]
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=874jict9er.fsf@no.lan \
--to=telegraph@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=incal@dataswamp.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).