From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Finalizing 'inhibit-automatic-native-compilation' Date: Sat, 28 Jan 2023 10:08:02 +0200 Message-ID: <83edrfaxp9.fsf@gnu.org> References: <837cx8cey0.fsf@gnu.org> <86wn57bmjt.fsf@stephe-leake.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34489"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, akrl@sdf.org, larsi@gnus.org, monnier@iro.umontreal.ca, rlb@defaultvalue.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 28 09:09:07 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pLgGo-0008l1-T2 for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Jan 2023 09:09:06 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pLgG5-00053Q-2X; Sat, 28 Jan 2023 03:08:21 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pLgG3-000539-BU for emacs-devel@gnu.org; Sat, 28 Jan 2023 03:08:19 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pLgG1-0007DV-NQ; Sat, 28 Jan 2023 03:08:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=bf9DloZG8jTWGeDMtpH3Qpw6OP4hZLmaLj+jyLmETkI=; b=MszWMcQVacLL XRRFVarXvKnGaoIhrM53L/pcGuKAGsBg6R9bO1giSxX5GWGUw5pH9VHHhaZFftfFntaEZiiGmCRwa Ud1e7v/rtortzo+7IMbCoHWLPF+med1xOOrCvuZxf6rl5VXYzVJssxFMzpGO8s+9rOslEEG2yCAW9 8Xk2DQi5DEmGysMiO2t+JUmMcR7KL/14qu9mhLNfdRrnmjpURbYOK6xaMAt06hhBk77BoSsmWWYOe AER2Bvv0DM/Tfd1hvIsgwJ3FcyNDKD9HTP7ffIYWbG2n0XoYioLqzi41GIFzLE5+JDCHatG6HDBcS o7dfJotb+TwAdyB3dSqlUw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pLgG0-0001Vt-SW; Sat, 28 Jan 2023 03:08:17 -0500 In-Reply-To: <86wn57bmjt.fsf@stephe-leake.org> (message from Stephen Leake on Fri, 27 Jan 2023 15:11:18 -0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302703 Archived-At: > From: Stephen Leake > Cc: emacs-devel@gnu.org, Andrea Corallo , Lars Ingebrigtsen > , Stefan Monnier , Rob > Browning > Date: Fri, 27 Jan 2023 15:11:18 -0800 > > Eli Zaretskii writes: > > > Here are the questions I think we want to be answered to finalize the > > implementation and effects of 'inhibit-automatic-native-compilation': > > > > . Do people actually use 'inhibit-automatic-native-compilation' or > > the corresponding environment variable? If so, for what reasons, > > and why tweaking 'native-comp-eln-load-path' to direct the *.eln > > files to some other place, including the temporary-file directory, > > was not enough? > > I do. > > When running Emacs ada-mode tests, I spawn lots of Emacsen. If each one > tries to native compile stuff, it just slows down the tests. > > I could try to ensure the stuff is native compiled first, but that's a > maintenance burden. Disabling async native-compilation was supported before we introduced this variable (via native-comp-deferred-compilation) and will continue being supported, for several valid reasons. Removing that capability is not on the table. I understand that if inhibiting native-compilation would still produce trampolines in the rare cases where they are needed, it will not do any significant harm to your use case, is that right? > > . What do we want to do about compiling trampolines when > > native-compilation is disabled? > > What is the name of the "temporary directory" that is not deleted on > Windows? I can check it see if is created when I run my tests. It's the system temporary directory, the one that's the value of temporary-file-directory. And it isn't the directory that is not deleted, it's the comp-lambda-*.eln files (and maybe also *.eln files under different names, like *--trampoline-*.eln) in that directory. > > . Do we want to keep the EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION > > environment variable? > > I don't need this for my use case. Thanks for the feedback.