emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [feature/native-comp] breakage on build


From: Andrea Corallo
Subject: Re: [feature/native-comp] breakage on build
Date: Mon, 08 Feb 2021 14:28:46 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Phillip Lord <phillip.lord@russet.org.uk> writes:

> Andrea Corallo <akrl@sdf.org> writes:
>
>> Phillip Lord <phillip.lord@russet.org.uk> writes:
>>> Eli, Oscar, Andrea
>>>
>>> Apologies, I had forgotten that I had moved machines during testing. It
>>> was simply the path (and exec-path) that was missing. My own time is
>>> mine to waste, but apologies for wasting yours.
>>>
>>> I am coming to the conclusion that I am going the wrong path here. I
>>> think supporting native-comp and keeping a sanely sized Emacs
>>> distribution are not compatible objectives. I do not want to return to
>>> the Emacs-26 distribution, which included a lot of msys2.
>>>
>>> I think that the base distribution of Emacs-28 should not include
>>> JIT native-comp. If people want this, they should get it through the
>>> msys2 co-installation that Oscar and I have been talking of.
>>>
>>> However, we could just do a full AOT native-comp, so at least the
>>> Emacs-28 packages would all benefit. Andrea, can the native-comp branch
>>> still load *eln files even if it can't produce them?
>>
>> Yes, libgccjit is not needed for loading elns.  There might be some minors to
>> look at as I've never tested this configuration but should be no
>> problem.
>
>
> For an Emacs compiled --with-nativecomp, how do I stop it attempting to
> native compile?

`comp-deferred-compilation'

But I was wrong there's another issue.  If we can't compile we cannot
synthesize trampolines, as a consequence we can't redefine or advice
primitive functions reliably... Sorry

  Andrea



reply via email to

[Prev in Thread] Current Thread [Next in Thread]