[Top][All Lists]

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

Re: The emacs-28 release branch has been created

From: Andrea Corallo
Subject: Re: The emacs-28 release branch has been created
Date: Tue, 05 Oct 2021 16:52:14 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: kbrown@cornell.edu, emacs-devel@gnu.org
>> Date: Tue, 05 Oct 2021 15:37:15 +0000
>> > If so, what is special in byte+native-compile and
>> > batch-native-compile that they require not to spawn a child process?
>> Nothing special, we used to discriminate if we wanted to spawn a child
>> process using `byte+native-compile', but this worked only for
>> byte+native-compile' and not for `batch-native-compile'.  For both these
>> two function we do not want to spawn a child process as its really not
>> necessary, so my fix.
> I guess I'm asking whether all batch-mode native-compilations need
> this, or only these two functions?

The rationale behind is that when these two function are used we
(likely) know that the session will not be a long standing one as Emacs
is run to perform a compilation and die, therefore we can accept some
memory leakage from GCC.  Not sure we want to do that for any
compilation running in batch mode.  WDYT?



reply via email to

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