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: Tue, 14 Feb 2023 15:51:16 +0200 Message-ID: <83y1p0cq3v.fsf@gnu.org> References: <837cx8cey0.fsf@gnu.org> <87sffo3as7.fsf@melete.silentflame.com> <83v8kkxzzx.fsf@gnu.org> <87r0v811pm.fsf@melete.silentflame.com> <87cz6nxdqy.fsf@X570GP> <83357irhnv.fsf@gnu.org> <87ttzy2lgi.fsf@X570GP> <83a61pprm8.fsf@gnu.org> <87mt5ncjuk.fsf@X570GP> <83cz6jm9mo.fsf@gnu.org> <87a61lkjb7.fsf@X570GP> <87pmahs9um.fsf@EBx360> <877cwoo6ru.fsf@X570GP> <83bkm0jxbr.fsf@gnu.org> <87ttzq25m6.fsf@X570GP> <837cwmhlgs.fsf@gnu.org> <87pmae1wrs.fsf@X570GP> <83v8k6fxy5.fsf@gnu.org> <87y1p01qlc.fsf@EBx360> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33455"; mail-complaints-to="usenet@ciao.gmane.io" Cc: akrl@sdf.org, spwhitton@spwhitton.name, monnier@iro.umontreal.ca, emacs-devel@gnu.org, larsi@gnus.org, rlb@defaultvalue.org To: Aymeric Agon-Rambosson Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Feb 14 14:52:37 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 1pRvjZ-0008Uz-So for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Feb 2023 14:52:37 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pRvij-0002PP-Kf; Tue, 14 Feb 2023 08:51:45 -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 1pRvif-0002OP-Rk for emacs-devel@gnu.org; Tue, 14 Feb 2023 08:51:43 -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 1pRvid-0003cx-Pi; Tue, 14 Feb 2023 08:51:39 -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=k9IiLWSEHnBE1cI7TkSYTyPgpTeguG17cjuexxQyQZo=; b=H+T5yR8wKj7U mVIUQNfZE8i+WapiBNwtqJjqkizJ46rJpC/3q2mbDEem7+xeltggMIH0+Bq0V2nkFS/fPJjXZX/H+ tZZ6+jwAk1V0DxGErMvNOuJfrzErjabz1QeE7sdxZWxJK62jtsHrUUihvQsoYDT7M1Ugbw+XKTJDH E5+SimUCo8z4e+m11XR3QEl6BZWY91EaEXw2Lq98mkzweh9WDfJSbED612qPfFCc+w0M4nUf+BA6f YvH5LLLY8I0jhU/rw7Rw1n3FB1/vyUjeiwxNXgiddqERieUqFN6MIgNBwHY64+qxG3qozqlrd11MD LmdbKXpvbFEGJYHrOSxlsg==; 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 1pRvic-0001qb-S7; Tue, 14 Feb 2023 08:51:39 -0500 In-Reply-To: <87y1p01qlc.fsf@EBx360> (message from Aymeric Agon-Rambosson on Tue, 14 Feb 2023 11:36:15 +0100) 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:303274 Archived-At: > From: Aymeric Agon-Rambosson > Cc: akrl@sdf.org, spwhitton@spwhitton.name, monnier@iro.umontreal.ca, > emacs-devel@gnu.org, larsi@gnus.org, rlb@defaultvalue.org > Date: Tue, 14 Feb 2023 11:36:15 +0100 > > >From what I understand, passing nil as last argument to > `comp--native-compile' only means that a temporary file will be > created in `temporary-file-directory' to store the output of the > native compilation process. When will this be useful, and why the existing features don't already support whatever use case you had in mind? As people here pointed out just recently, if Emacs cannot write a .eln file, it will still work correctly by using the corresponding .elc file. So why do we need a subtle feature of depositing *.eln files in a temporary directory (which on many systems is ephemeral, or is regularly purged)? > So something like (setq comp-enable-subr-trampolines > 'compile-but-no-output) would *only* mean : output to a temporary > file in `temporary-file-directory'. It wouldn't also mean "and > remove it afterwards". This meaning is perfectly compatible with > the removal of the deletion after loading logic. By the very nature of temporary files and directories created by Emacs, you cannot know their exact name, and so putting a file there would be almost completely useless. So I'm asking when will this be useful. I'd like to avoid adding features whose usability is not well understood and whose justification is not solid enough. We have too many subtle knobs in native-compilation already.