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: Wed, 08 Dec 2021 14:51:33 +0200 Message-ID: <8335n3xnsa.fsf@gnu.org> References: <87czmdqpv9.fsf@web.de> <83h7bo7rvz.fsf@gnu.org> <87bl1tjage.fsf@web.de> <83fsr4zfl2.fsf@gnu.org> <87y24vvnnk.fsf@web.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11603"; 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 Wed Dec 08 13:54:42 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 1muwT4-0002j6-8N for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Dec 2021 13:54:42 +0100 Original-Received: from localhost ([::1]:39154 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1muwT2-0005jq-4x for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Dec 2021 07:54:40 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37570) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muwQS-0003db-Aq for emacs-devel@gnu.org; Wed, 08 Dec 2021 07:52:00 -0500 Original-Received: from [2001:470:142:3::e] (port=56026 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 1muwQL-0007Ef-Aq; Wed, 08 Dec 2021 07:51:59 -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=fpUDD2MHBVwT9n9Q0wuAMBfmbQ6uEEsxsATgZIc4JVI=; b=TYYMARu7P3AV q6K7q6eFauJ3be4rsEgP7XsrZx6ze4Yt7RuLfUUG09e0+l7OZe8PUvyBmZUcXfAK/B7bOsETpXRLG rHcJv+ZgvnweFhWaOZ5S/WkJ1dZzUZQc31tBPgiN7qDCp7Oy1rshU+iGLZ9leAKYnD1SjwuoKGhsV VjlQpxfL0HwTNfNFXem4/9S1UxjsNIpGTA8ZkRtUTESHEhBcOHMK7X12gIzd8B3TF2cT8bI8jkRpT l2KEhgWurvxYe+m3gZm9McZvNXPWWn86VDPc/0ikpr0J2n22YTDWMBSgwffqee95DhM0yWyrbz2Be z8mFWLpHEvQjL6nqwdEiWw==; Original-Received: from [87.69.77.57] (port=4489 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 1muwQL-0002aa-3s; Wed, 08 Dec 2021 07:51:53 -0500 In-Reply-To: <87y24vvnnk.fsf@web.de> (message from Michael Heerdegen on Wed, 08 Dec 2021 03:25:03 +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:281342 Archived-At: > From: Michael Heerdegen > Cc: emacs-devel@gnu.org > Date: Wed, 08 Dec 2021 03:25:03 +0100 > > Eli Zaretskii writes: > > > 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. > > Once this gets the default, the following will happen: regular users > that are not programmers will install packages and libraries, and then > they will get the popup warning windows. For Elisp developers this is > good and useful, but for regular users this will cause confusion and > annoy for no gain. That's my concern. Maybe the popup of the window > should be opt-in - unless it's due to my config that the window > containing the warnings pops up and even raises its frame. The JIT compilation doesn't just happen randomly because Emacs decides it's an opportune moment for it. It happens because the session loads some Lisp file. A live Emacs session used for real-life work will always load Lisp files, as needed. Loading a Lisp file (via 'load' or 'require' or any similar API) could potentially pop up warnings and errors without any relation to native compilation, because something went wrong while loading. I presume you won't argue for shutting up such messages caused by some problems in the load process or in the interaction of the loaded code with what you already have in the session, would you? Then how are the warnings triggered by JIT compilation different, in principle? They are the same phenomenon: Emacs loaded some Lisp package because some command needed it, and loading it caused warnings due to issues with the loaded code.