[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 15:14:50 +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:
>>
>>> Andrea Corallo <akrl@sdf.org> writes:
>>>
>>>> Phillip Lord <phillip.lord@russet.org.uk> writes:
>>>>
>>>> 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
>
>
> I didn't think we could do this anyway. I guess this means that
> native-compiled lisp to primitive adviced functions will skip the
> advice? So, that would be a change from the current situation where
> C calls to C functions don't get adviced, but lisp calls to C functions
> do.
Apologies let me be more precise.
- Advising C to C primitives is not possible in both implementations
- With bytecode you can effectively redefine primitives with _no_
dedicated op-bytecode.
- With native code you can redefine all of these except for the (very
few) primitives we open-code directly in the generated code. This is
a smaller set than the previous one but still not perfect.
Anyway, we can do this but relying on this trampoline syntheses
mechanism.
Removing this mechanism is therfore ATM not possible, unless we
precompile all trampolines AOT bug#44238. This should be rather easy
tho, we lack only some integration into the build system lets say.
Andrea
- Re: [feature/native-comp] breakage on build, (continued)
- Re: [feature/native-comp] breakage on build, Eli Zaretskii, 2021/02/05
- Re: [feature/native-comp] breakage on build, Phillip Lord, 2021/02/05
- Re: [feature/native-comp] breakage on build, Eli Zaretskii, 2021/02/06
- Re: [feature/native-comp] breakage on build, Phillip Lord, 2021/02/06
- Re: [feature/native-comp] breakage on build, Eli Zaretskii, 2021/02/06
- Re: [feature/native-comp] breakage on build, Phillip Lord, 2021/02/07
- Re: [feature/native-comp] breakage on build, Andrea Corallo, 2021/02/08
- Re: [feature/native-comp] breakage on build, Phillip Lord, 2021/02/08
- Re: [feature/native-comp] breakage on build, Andrea Corallo, 2021/02/08
- Re: [feature/native-comp] breakage on build, Phillip Lord, 2021/02/08
- Re: [feature/native-comp] breakage on build,
Andrea Corallo <=
- Re: [feature/native-comp] breakage on build, Stefan Monnier, 2021/02/08
- Re: [feature/native-comp] breakage on build, Andrea Corallo, 2021/02/09
- Re: [feature/native-comp] breakage on build, Phillip Lord, 2021/02/09
- Re: [feature/native-comp] breakage on build, Andrea Corallo, 2021/02/10
- Re: [feature/native-comp] breakage on build, Stefan Monnier, 2021/02/10
- Re: [feature/native-comp] breakage on build, Andrea Corallo, 2021/02/10
- Re: [feature/native-comp] breakage on build, Phillip Lord, 2021/02/15
- Re: [feature/native-comp] breakage on build, Eli Zaretskii, 2021/02/10
- Re: [feature/native-comp] breakage on build, Andrea Corallo, 2021/02/10
- Re: [feature/native-comp] breakage on build, Eli Zaretskii, 2021/02/11