Tuesday, April 19, 2022

Re: [update] emacs-28.1

Jeremie Courreges-Anglas <jca@wxcvbn.org> wrote:
> On Sat, Apr 16 2022, Kenneth R Westerback <kwesterback@gmail.com> wrote:
> > On Wed, Apr 13, 2022 at 02:23:04PM +0200, Jeremie Courreges-Anglas wrote:
> >>
> >> Here's an update to the latest emacs version, very lightly tested so
> >> far on amd64, test build running on sparc64.
> >>
> >> Test reports welcome.
> >
> > So far so good on my amd64 E595.
> >
> > The only comment doom makes is
> >
> > ! Emacs was not built with native compilation support
> > Users will see a substantial performance gain by building Emacs with native
> > compilation support, availible in emacs 28+.You must install a prebuilt
> > Emacs binary with this included, or compile Emacs with the
> > --with-native-compilation option.
> >
> > Dunno if avoiding native compilation is deliberate on your part or not. :-)
>
> Yeah I didn't look into it, it would require libgccjit from a recent-ish
> lang/gcc port (op@ said lang/gcc/8 wasn't enough).

yep, i tried a year ago or so with gcc8 but I remember all sorts of
error popping up. When I re-tried with gcc10 it worked flawlessly, no
need to patch anything, it just worked.

> Timo Myyra has sent
> a patch for lang/gcc:
>
> https://marc.info/?l=openbsd-ports&s=gccjit

keep in mind that his diff doesn't build IIRC. I've used a diff sent by
someone on IRC (sorry, I don't remember the nick) and tweaked it a bit,
but eventually lost it ^^" -- apologize.

> I haven't tried this yet and I don't know how much it can speed up
> emacs, but it will require careful thinking. People who want it, feel
> free to beat me to it. :)

I've heard really good things about it, but in my case it I didn't feel
any difference. I only got *a lot* of annoying warnings buffers popping
up as soon as Emacs started to compile 3rd parties packages. It seemed
easier to disable it rather than tweak display-buffers-alist ;)

No comments:

Post a Comment