5 ms·

Anyone running the jit Emacs? Can't wait for it. I did try compiling it from source for my linux setup. Would love to see it on windows.

prussian 6y ago
I am. I honestly don't notice much of a difference, but at the same time I keep seeing deferred compilation warnings for plugins I have added via straight.el I've been using https://github.com/flatwhatson/guix-channel https://github.com/flatwhatson/guix-channel to manage it. I don't recommend trying the Pure GTK+ stuff yet though; some context menus don't seem to work. Specifically, treemacs rename seems broken with PGTK.
TacticalCoder 6y ago
> Anyone running the jit Emacs? I'm running the "native-comp" (libgccjit) branch daily since months and months now: not a single problem here and I've got quite a "heavy" config (thousands of lines of custom config and all the usual suspects: magit / org-mode / lsp / cider etc.). > I did try compiling it from source for my linux setup. And it worked? Worked on the first try for me (on the Debian distro). I was somehow expecting lots of problems (because it's one heck of a change) but it really all just compiled and worked perfectly fine.
- rataata_jr 6y ago
  I followed this tutorial from mastering emacs blog iirc. I built it inside docker. I think it worked on the first try for me as well. I didn't use it much since it was in docker.
- voodoologic 6y ago
  I found an easy installer for native-comp (for mac os). https://github.com/d12frosted/homebrew-emacs-plus https://github.com/d12frosted/homebrew-emacs-plus I'm new to emacs and so I am unaware how much faster it is or isn't.
hypersoar 6y ago
I've been using it for a few months on wsl and it's been great. I'm using the Nix package and have run into only a couple of minor issues.
- rataata_jr 6y ago
  That's a good idea, will finally try nix package manager on windows.
iib 6y ago
I have compiled straight from source on the feature/native-comp branch, and it works noticeably much faster. I am actually scared of going back to the regular Emacs, as I may find it way too slow. I am not sure how much it is from native Emacs, as when I did this, I also enabled all the other recommended optimizations from lsp (increasing the gc threshold early in the config, installing and compiling with native json support etc.) As far as I know, the latest branch has all the necessary flags enabled, so you can just do ./autogen.sh && ./configure --with-nativecomp --with-xwidgets --with-json && make -j4 && make install after you installed the dependencies and cloned the Emacs repo (--with-nativecomp may actually be set to default now in this branch). You also need a very recent version of gcc, as the libgccjit is somewhat new, and it may err on the compilation process.
- taeric 6y ago
  I also enable march=native for the compile. My guess is it is mostly placebo, but I feel it helps.
  - iib 6y ago
    I only know of this discussion[1] on Daniel Lemire's blog regarding -march=native, which seems to have the "it's complicated" conclusion. But yes, _theoretically_ that is a way to compile for better performance, for your own machine. [1] https://lemire.me/blog/2018/07/25/it-is-more-complicated-than-i-thought-mtune-march-in-gcc/ https://lemire.me/blog/2018/07/25/it-is-more-complicated-tha...
    - taeric 6y ago
      Yeah, "complicated" sums it up perfectly. I know it /should/ be faster. And, it does feel so. But, I don't have hard data to prove it, such that I have to ack it could just be placebo.
- indy 6y ago
  It looks like the configure option has been renamed to --with-native-compilation on the feature/native-comp branch (and it has to be specified otherwise it defaults to no)
rurban 6y ago
Running the native-comp + wayland copr on fc32 for about a year, whithout any problem. About 3x faster. https://copr.fedorainfracloud.org/coprs/deathwish/emacs-pgtk-nativecomp/ https://copr.fedorainfracloud.org/coprs/deathwish/emacs-pgtk...
TeMPOraL 6y ago
Over half a year now, as a daily driver. Personally on Ubuntu, at work on WSL (Windows Subsystem for Linux) - which I then x-forward to an VcXsrv on Windows. Works pretty much flawlessly, and it's much snappier on some of the workloads I put it through - like big collections of big Org Mode files, or viewing (and fontifying) large files.
lsllc 6y ago
Yes, it's pretty solid running Doom Emacs. There's a handy macOS build script/helper: https://github.com/jimeh/build-emacs-for-macos https://github.com/jimeh/build-emacs-for-macos The author curates a list of "known good" commits to the feature/native-comp branch so you don't waste your time with bad builds: https://github.com/jimeh/build-emacs-for-macos/issues/6 https://github.com/jimeh/build-emacs-for-macos/issues/6
bambataa 6y ago
I've just tried it on macOS, built by this tool: https://github.com/jimeh/build-emacs-for-macos https://github.com/jimeh/build-emacs-for-macos Unfortunately it keeps locking up my entire computer so might not be a goer just yet.

prussian 6y ago

I am. I honestly don't notice much of a difference, but at the same time I keep seeing deferred compilation warnings for plugins I have added via straight.el I've been using https://github.com/flatwhatson/guix-channel https://github.com/flatwhatson/guix-channel to manage it. I don't recommend trying the Pure GTK+ stuff yet though; some context menus don't seem to work. Specifically, treemacs rename seems broken with PGTK.

TacticalCoder 6y ago

> Anyone running the jit Emacs? I'm running the "native-comp" (libgccjit) branch daily since months and months now: not a single problem here and I've got quite a "heavy" config (thousands of lines of custom config and all the usual suspects: magit / org-mode / lsp / cider etc.). > I did try compiling it from source for my linux setup. And it worked? Worked on the first try for me (on the Debian distro). I was somehow expecting lots of problems (because it's one heck of a change) but it really all just compiled and worked perfectly fine.

rataata_jr 6y ago
I followed this tutorial from mastering emacs blog iirc. I built it inside docker. I think it worked on the first try for me as well. I didn't use it much since it was in docker.
voodoologic 6y ago
I found an easy installer for native-comp (for mac os). https://github.com/d12frosted/homebrew-emacs-plus https://github.com/d12frosted/homebrew-emacs-plus I'm new to emacs and so I am unaware how much faster it is or isn't.

hypersoar 6y ago

I've been using it for a few months on wsl and it's been great. I'm using the Nix package and have run into only a couple of minor issues.

rataata_jr 6y ago
That's a good idea, will finally try nix package manager on windows.

iib 6y ago

I have compiled straight from source on the feature/native-comp branch, and it works noticeably much faster. I am actually scared of going back to the regular Emacs, as I may find it way too slow. I am not sure how much it is from native Emacs, as when I did this, I also enabled all the other recommended optimizations from lsp (increasing the gc threshold early in the config, installing and compiling with native json support etc.) As far as I know, the latest branch has all the necessary flags enabled, so you can just do ./autogen.sh && ./configure --with-nativecomp --with-xwidgets --with-json && make -j4 && make install after you installed the dependencies and cloned the Emacs repo (--with-nativecomp may actually be set to default now in this branch). You also need a very recent version of gcc, as the libgccjit is somewhat new, and it may err on the compilation process.

taeric 6y ago
I also enable march=native for the compile. My guess is it is mostly placebo, but I feel it helps.
- iib 6y ago
  I only know of this discussion[1] on Daniel Lemire's blog regarding -march=native, which seems to have the "it's complicated" conclusion. But yes, _theoretically_ that is a way to compile for better performance, for your own machine. [1] https://lemire.me/blog/2018/07/25/it-is-more-complicated-than-i-thought-mtune-march-in-gcc/ https://lemire.me/blog/2018/07/25/it-is-more-complicated-tha...
  - taeric 6y ago
    Yeah, "complicated" sums it up perfectly. I know it /should/ be faster. And, it does feel so. But, I don't have hard data to prove it, such that I have to ack it could just be placebo.
indy 6y ago
It looks like the configure option has been renamed to --with-native-compilation on the feature/native-comp branch (and it has to be specified otherwise it defaults to no)

rurban 6y ago

Running the native-comp + wayland copr on fc32 for about a year, whithout any problem. About 3x faster. https://copr.fedorainfracloud.org/coprs/deathwish/emacs-pgtk-nativecomp/ https://copr.fedorainfracloud.org/coprs/deathwish/emacs-pgtk...

TeMPOraL 6y ago

Over half a year now, as a daily driver. Personally on Ubuntu, at work on WSL (Windows Subsystem for Linux) - which I then x-forward to an VcXsrv on Windows. Works pretty much flawlessly, and it's much snappier on some of the workloads I put it through - like big collections of big Org Mode files, or viewing (and fontifying) large files.

lsllc 6y ago

Yes, it's pretty solid running Doom Emacs. There's a handy macOS build script/helper: https://github.com/jimeh/build-emacs-for-macos https://github.com/jimeh/build-emacs-for-macos The author curates a list of "known good" commits to the feature/native-comp branch so you don't waste your time with bad builds: https://github.com/jimeh/build-emacs-for-macos/issues/6 https://github.com/jimeh/build-emacs-for-macos/issues/6

bambataa 6y ago

I've just tried it on macOS, built by this tool: https://github.com/jimeh/build-emacs-for-macos https://github.com/jimeh/build-emacs-for-macos Unfortunately it keeps locking up my entire computer so might not be a goer just yet.