From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Aymeric Agon-Rambosson Newsgroups: gmane.emacs.devel Subject: Re: Finalizing 'inhibit-automatic-native-compilation' Date: Sun, 12 Feb 2023 20:58:15 +0100 Message-ID: <87pmae1wrs.fsf@X570GP> References: <837cx8cey0.fsf@gnu.org> <83lell73yv.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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18745"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.6.10; emacs 28.1 Cc: akrl@sdf.org, spwhitton@spwhitton.name, monnier@iro.umontreal.ca, emacs-devel@gnu.org, larsi@gnus.org, rlb@defaultvalue.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 12 21:03:14 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 1pRIZ6-0004Z6-FR for ged-emacs-devel@m.gmane-mx.org; Sun, 12 Feb 2023 21:03:12 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pRIYX-0001Cd-71; Sun, 12 Feb 2023 15:02:37 -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 1pRIUU-0000fT-BD for emacs-devel@gnu.org; Sun, 12 Feb 2023 14:58:26 -0500 Original-Received: from forward501b.mail.yandex.net ([2a02:6b8:c02:900:1:45:d181:d501]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pRIUR-0000vz-Dn; Sun, 12 Feb 2023 14:58:25 -0500 Original-Received: from myt6-870ea81e6a0f.qloud-c.yandex.net (myt6-870ea81e6a0f.qloud-c.yandex.net [IPv6:2a02:6b8:c12:2229:0:640:870e:a81e]) by forward501b.mail.yandex.net (Yandex) with ESMTP id 988355E8A2; Sun, 12 Feb 2023 22:58:18 +0300 (MSK) Original-Received: by myt6-870ea81e6a0f.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id FwnVpeWYbOs1-3nTKFoYI; Sun, 12 Feb 2023 22:58:18 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1676231898; bh=/As8QNaDvdfFYhWCU/gyoyTig6ufY2hco7i6a2FGE04=; h=Cc:Message-ID:References:Date:Subject:In-reply-to:To:From; b=OKVpiC+VmXWG5mwWuCYfqyyMKsKGzH/c7iQ6vm9wFrV/UFp4zl9iBCZU1Lh6dgz7U m3pHVptwxzYBQL8UWvPJB4wRYGjyxYPFNK2f1FLKobADrQOC4lqDZtVdQZOdfC0qwK KDBFD1j9mWd2T43ZUcnOus32QK/t1kuXPdwPYhDY= Authentication-Results: myt6-870ea81e6a0f.qloud-c.yandex.net; dkim=pass header.i=@yandex.com In-reply-to: <837cwmhlgs.fsf@gnu.org> Received-SPF: pass client-ip=2a02:6b8:c02:900:1:45:d181:d501; envelope-from=aymeric.agon@yandex.com; helo=forward501b.mail.yandex.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sun, 12 Feb 2023 15:02:35 -0500 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:303197 Archived-At: Le dimanche 12 f=C3=A9vrier 2023 =C3=A0 18:55, Eli Zaretskii = =20 a =C3=A9crit : >> From: Aymeric Agon-Rambosson >> Cc: akrl@sdf.org, spwhitton@spwhitton.name,=20 >> monnier@iro.umontreal.ca, >> emacs-devel@gnu.org, larsi@gnus.org, rlb@defaultvalue.org >> Date: Sun, 12 Feb 2023 17:47:13 +0100 >>=20 >> Being able to do (setq comp-enable-subr-trampolines=20 >> 'compile-but-no-output) would be quite practical. The temporary=20 >> file would be created by `make-temp-file', according to the=20 >> value=20 >> of `temporary-file-directory', and we wouldn't have to worry=20 >> about=20 >> specifying some exact location ourselves > > Why is it a problem that you provide the location? > "/tmp/SOME-DIRECTORY" is always a possibility, and you can=20 > delete the > entire directory when you are done would then get rid of all the > leftovers, something that test runs and installations routinely=20 > do. > Why isn't this good enough? If we have to provide the location, we have to ensure the=20 directory exists. I guess it is not necessarily an issue, but I=20 figured that if the semantic of nil as last argument of=20 `comp--native-compile' and the underlying mechanism of temporary=20 files is already there, and is supposed to stay, we might as well=20 use it. The current meaning of `inhibit-automatic-native-compilation' is a=20 current "good" state that allowed a large number of build failures=20 to disappear, and it would be reassuring to be able to reproduce=20 that state exactly, before eventually migrating to providing the=20 location ourselves, if we see that we can do so without errors.