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: Enabling native compilation by default when libgccjit is present Date: Tue, 07 Dec 2021 15:53:29 +0200 Message-ID: <83fsr4zfl2.fsf@gnu.org> References: <87czmdqpv9.fsf@web.de> <83h7bo7rvz.fsf@gnu.org> <87bl1tjage.fsf@web.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21063"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Michael Heerdegen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 07 14:56:26 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 1muaxF-0005Bz-BE for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 14:56:25 +0100 Original-Received: from localhost ([::1]:33870 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1muaxE-0008QZ-3m for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Dec 2021 08:56:24 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:41272) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muauP-0005Y5-NL for emacs-devel@gnu.org; Tue, 07 Dec 2021 08:53:29 -0500 Original-Received: from [2001:470:142:3::e] (port=41152 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muauP-00027a-E1; Tue, 07 Dec 2021 08:53:29 -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=g3YxMrcAGX9wtATiievwelLozCYIo7JBaZ1CUF7jx+Q=; b=CmONq2O4uRYa il5+u82unNYP3xNntWr8/dHUtyHmt/hcqnbwwNBn52SXobSPL4uWLmGpMKtFG9KgewH/j4tXRXPmA athrEifWW+NJDO2UJ+EBg0A2h1MqdafDvqRKbLTQFUE3Y0spLrCb1emD4bY2BqYACuH9/yjdLGBMi BYjT8mTOncNvUaN+pLSZ+sAQg0RjKLdc6V56byfcV+FaFctxIK+RFBAjciKVqoTnoHpsgLWw49aqH GMwNdKHnFxriOsguinFUQHh5GJa3vRrdH0sNRF1jMHu4BmzCqhnZ9psVF6SJOaf9yGUVtTFy/QRrX 2t46UECPBuQQpew/pUqG2w==; Original-Received: from [87.69.77.57] (port=2703 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 1muauP-0007OO-6a; Tue, 07 Dec 2021 08:53:29 -0500 In-Reply-To: <87bl1tjage.fsf@web.de> (message from Michael Heerdegen on Tue, 07 Dec 2021 05:38:41 +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" Xref: news.gmane.io gmane.emacs.devel:281245 Archived-At: > From: Michael Heerdegen > Cc: emacs-devel@gnu.org > Date: Tue, 07 Dec 2021 05:38:41 +0100 > > Eli Zaretskii writes: > > > It is normal, yes. You are supposed to either fix the warnings by > > adding the missing 'require's, or tell Emacs not to natively-compile > > the files where you don't want that (like your init files), or > > customize the option to turn off the warnings. > > But don't you think these warnings should not be presented to the end > user who maybe doesn't know what these warnings mean? I mean, these > warnings pop up while using Emacs, not when installing or upgrading. That these warning appear during routine usage is a direct consequence of JIT compilation. This JIT compilation can be disabled, but IMO doing so by default would make little sense. So the warnings are the price we pay for having Emacs silently compile code in the background. But once we agree to have it compile automatically, it should be clear that messages related to compilation will be produced, and ignoring those messages might not necessarily be a good idea. > Even after every restart. No, not unless the code changes between restarts. If the code doesn't change, then this compilation is a one-time thing (assuming you left Emacs up and running enough seconds to allow it to finish the compilation). > And it takes a while, and there are a lot. The first time you fire up Emacs with native-compilation, yes, it can take a few minutes (how many depends on how many packages you load at startup). But again, this is a one-time thing, and it is quite fast even the first time. > I think that has to be improved before it gets the default behavior > in a release. We don't build Emacs with native-compilation by default yet, you have to request that at configure time. This discussion is about the warnings which are emitted when you did request feature, not about whether the feature itself should be included by default.