emacs-devel
[Top][All Lists]
Advanced

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

Re: Suppressing native compilation (short and long term)


From: Andrea Corallo
Subject: Re: Suppressing native compilation (short and long term)
Date: Tue, 18 Oct 2022 13:56:18 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Andrea Corallo <akrl@sdf.org> writes:
>
>>>>> I think it's a fine solution, but either comp-spawned-compilation
>>>>> should be renamed to comp-no-spawn, or its value in the forked Emacs
>>>>> processes should be nil...
>
> [...]
>
>> Okay 1a8015b837 should do the job.  I eventually opted for adding
>> `comp-no-spawn' for now, seen the current "debated" situation on what we
>> should offer as interface to the user, I thought was better for now to
>> add a variable supposed to be used for internal use only.  We can remove
>> it and link the mechanism to `native-comp-async-jobs-number' afterwards
>> if we decide for it.
>
> Is this supposed to fix the trampoline fork bomb?  (There's a lot of
> stuff discussed in this thread...)  If so, it doesn't, because the
> variable is set too late.  (As Eli suggested in another thread, we
> should add a command line argument for this, and as I noted, that kind
> of fits with the stuff discussed in bug#58509.)

Right, I replied in bug#58509 with a patch that should fix the issue.



reply via email to

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