[Top][All Lists]

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

Re: Finalizing 'inhibit-automatic-native-compilation'

From: Sean Whitton
Subject: Re: Finalizing 'inhibit-automatic-native-compilation'
Date: Thu, 02 Feb 2023 09:17:25 -0700
User-agent: Gnus/5.13 (Gnus v5.13)

Aymeric, you investigated one of these cases in details.  Would you be
able to summarise the situation we had in Debian for Eli, please?

I don't myself have time for the next week or so.

On Thu 02 Feb 2023 at 09:55AM +02, Eli Zaretskii wrote:

>> From: Sean Whitton <spwhitton@spwhitton.name>
>> On Sun 29 Jan 2023 at 09:30PM -05, Stefan Monnier wrote:
>> > I don't know if they need trampolines, but I wouldn't be surprised if
>> > they do on occasion.
>> Some of our addon package test suites use advice in ways that mean we
>> need the trampolines.
> Thanks, but if this should be taken into consideration for the
> purposes of this discussion and the decision to be made as result, we
> need all the details you can provide about these uses.  So:
>   . what kind of advice are those and which functions they advise?
>   . where and under what circumstances will those advised functions be
>     called, as part of your preparation of the packages?  (if the
>     advised functions are only called when the end-user uses the
>     package, that is not relevant to the present discussion)
>   . what bad things will happen if the advice will not work (details, please)?
>   . if we provide a way to specify, via comp-enable-subr-trampolines,
>     the directory to which the trampolines will be written, will that
>     satisfy your uses? if not, why not (details, please)?
>   . why cannot you use native-comp-eln-load-path to force the
>     trampolines go to a directory of your choice?
>   . any other pertinent details you can provide

Sean Whitton

reply via email to

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