From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Suppressing native compilation (short and long term) Date: Wed, 28 Sep 2022 18:49:43 +0000 Message-ID: References: <87ill8paw7.fsf@trouble.defaultvalue.org> <834jwrig5s.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23471"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: rlb@defaultvalue.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 28 21:06:58 2022 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 1odcOY-0005t2-95 for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Sep 2022 21:06:58 +0200 Original-Received: from localhost ([::1]:56458 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1odcOX-00047f-8N for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Sep 2022 15:06:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39706) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odc7y-0004sQ-CB for emacs-devel@gnu.org; Wed, 28 Sep 2022 14:49:50 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:55720) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1odc7w-0006W7-0w; Wed, 28 Sep 2022 14:49:50 -0400 Original-Received: from ma.sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 28SInh23022649 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 28 Sep 2022 18:49:43 GMT In-Reply-To: <834jwrig5s.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Sep 2022 20:04:47 +0300") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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" Xref: news.gmane.io gmane.emacs.devel:296418 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: emacs-devel@gnu.org >> Date: Wed, 28 Sep 2022 12:52:59 +0000 >> >> This is what `native-comp-deferred-compilation' does. Well except for >> trampolines but this is extremly light as cpu/energy cost. > > I think if we want to allow people to turn off async compilation, we > should provide a way to force native-comp-available-p to return nil. > When that function returns nil, Emacs already does react correctly (or > at least it's supposed to). Yes `native-comp-deferred-compilation' AFAIK does exactly this already, `native-comp-available-p' is to check if the native compiler is available (not necessarily the deferred/async mechanism). Best Regards Andera