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 17:21:24 +0000 Message-ID: References: <87pn2dq3xv.fsf@russet.org.uk> <83ft39hnk1.fsf@gnu.org> <87sg78kew7.fsf@russet.org.uk> <87pn2b7qlb.fsf@russet.org.uk> <871rerxwre.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="19054"; 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 18:40:39 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 1kz1BH-0004rO-0n for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Jan 2021 18:40:39 +0100 Original-Received: from localhost ([::1]:50010 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kz1BF-0006u4-Vq for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Jan 2021 12:40:38 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52108) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kz0sk-00041L-PJ for emacs-devel@gnu.org; Mon, 11 Jan 2021 12:21:30 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:49334) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kz0sh-0000bJ-Er; Mon, 11 Jan 2021 12:21:30 -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 10BHLODl004594; Mon, 11 Jan 2021 17:21:25 GMT In-Reply-To: <871rerxwre.fsf@russet.org.uk> (Phillip Lord's message of "Mon, 11 Jan 2021 16:29:25 +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:262923 Archived-At: Phillip Lord writes: > Andrea Corallo writes: > >>> 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? > > > Yes, I think so, but it's probably an issue of thinking about the user > interface. Having this a bit more consistent (i.e. a single name space, > rather than two (native-comp and comp) and none (i.e. load-no-native)) > and perhaps a single option that does both ("comp-disable"). > > Just thoughts. Welcome thoughts from my side. I did my best to fit current name conventions but indeed this might be not the best arrangement, especially looking at it as single UI interface towards the "native compiler" seen as single entity. Looking forward to discuss and tackle this in the code review. Andrea