From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: [feature/dll-only-windows] A new windows build, comments wanted Date: Mon, 11 Jan 2021 11:01:51 +0000 Message-ID: References: <87pn2dq3xv.fsf@russet.org.uk> <83ft39hnk1.fsf@gnu.org> <87sg78kew7.fsf@russet.org.uk> <87pn2b7qlb.fsf@russet.org.uk> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5137"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Phillip Lord Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 11 12:03:00 2021 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 1kyuyS-0001AR-0U for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Jan 2021 12:03:00 +0100 Original-Received: from localhost ([::1]:47568 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kyuyR-0007Km-3y for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Jan 2021 06:02:59 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41118) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kyuxQ-0006p1-HK for emacs-devel@gnu.org; Mon, 11 Jan 2021 06:01:56 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:58970) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kyuxN-0001Xx-UA; Mon, 11 Jan 2021 06:01:56 -0500 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 10BB1pwr015782; Mon, 11 Jan 2021 11:01:51 GMT In-Reply-To: <87pn2b7qlb.fsf@russet.org.uk> (Phillip Lord's message of "Mon, 11 Jan 2021 09:47:12 +0000") 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.23 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:262901 Archived-At: Phillip Lord writes: > Andrea Corallo writes: > >> Phillip Lord writes: >> >>> >>> I think there are two hairs here. Having an emacs compiled with >>> nativecomp behave cleanly if libgccjit is not available at runtime. >> >> Right, at this stage this should be easy to implement (on Windows). >> >>> And having a runtime mechanism for switching nativecomp of totally >>> even if it is compiled in. >> >> We should define "switching nativecomp of" and the triggering mechanism, >> this might be already implmentented. > > >>>From a user perspective, I think that there are two reasons we might > want to switch off native-comp. > > The first is because it's broken or providing buggy behaviour. In the > extreme, and if I understand the build process fully, I guess this is > impossible to switch of in a binary distribution, because some > native-comp happens before dumping. Other than that, we can "switch off" > native-comp by just deleting the *eln files, right, or otherwise > preventing their loading. In practice, I think this is a minor > motivation; if we discover bugs in the native-comp, they would be fixed > by making another release. Hi Phillip, ATM we can prevent Emacs loading .eln file in place of .elc automatically setting `load-no-native' to t. > The second reason is that the initial compilation takes quite a lot of > CPU. I wouldn't like that to happen while my laptop where in battery > power, for instance. At the moment, it's possible to drop the number of > jobs that native-comp uses. I don't think that there is a way to drop > this to zero at the moment. Probably, we need that. Setting `comp-deferred-compilation' to nil should stop any automatic attempt of compiling asycronousy. Maybe these two settings are already covering most of these needs? Regards Andrea