From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#57627: 29.0.50; [native-compilation] cl-loaddefs.el recompiled on startup Date: Sat, 15 Oct 2022 12:13:32 +0200 Message-ID: <871qr95r8z.fsf@gnus.org> References: <87bkrsr1g2.fsf@gnus.org> <875yi0qz5b.fsf@gnus.org> <83sfl4ihfo.fsf@gnu.org> <87mtbcp774.fsf@gnus.org> <877d2e5ba1.fsf@gnus.org> <87czc4v5id.fsf@gnus.org> <874jxfsv9o.fsf@gnus.org> <874jw6d6cl.fsf@gnus.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="24875"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: germanp82@hotmail.com, 57627@debbugs.gnu.org, Eli Zaretskii , Andrea Corallo To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Oct 15 12:14:11 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1ojeBG-0006En-MW for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 15 Oct 2022 12:14:10 +0200 Original-Received: from localhost ([::1]:57304 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ojeBF-0007Hx-4n for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 15 Oct 2022 06:14:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43284) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojeB9-0007HZ-4W for bug-gnu-emacs@gnu.org; Sat, 15 Oct 2022 06:14:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40457) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ojeB8-0005sr-Sl for bug-gnu-emacs@gnu.org; Sat, 15 Oct 2022 06:14:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ojeB8-0002fE-Hc for bug-gnu-emacs@gnu.org; Sat, 15 Oct 2022 06:14:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 15 Oct 2022 10:14:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57627 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 57627-submit@debbugs.gnu.org id=B57627.166582882810203 (code B ref 57627); Sat, 15 Oct 2022 10:14:02 +0000 Original-Received: (at 57627) by debbugs.gnu.org; 15 Oct 2022 10:13:48 +0000 Original-Received: from localhost ([127.0.0.1]:39535 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ojeAu-0002eV-HO for submit@debbugs.gnu.org; Sat, 15 Oct 2022 06:13:48 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:56178) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ojeAs-0002eE-10 for 57627@debbugs.gnu.org; Sat, 15 Oct 2022 06:13:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=f2mD0hrDxTuWks1Uv4nKpdb8qAmlVXBw6mAl91ERE7A=; b=gmEIOqBAC7xD7a8fIDVofi3lYr 9ZmUtKq6fpZWg/m72qJzHHPXUO4zww27V451NSSo2xGAxdkBiRy/IH3qNAaGvpXEmSTHRerYYi2VQ KoM7l3fqiRiFdcOKrvwWcf49SFNBCtL8yhGR0TlnSYC4onWDpHvGlRRu5nvl/2M3UFz0=; Original-Received: from [84.212.220.105] (helo=downe) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ojeAf-00070N-9S; Sat, 15 Oct 2022 12:13:35 +0200 In-Reply-To: (Stefan Monnier's message of "Fri, 14 Oct 2022 15:00:00 -0400") Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAgMAAAAqbBEUAAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAADFBMVEWpSz40JSiDjbz/ ///rtNpNAAAAAWJLR0QDEQxM8gAAAAd0SU1FB+YKDwoAAv2DvjIAAAGgSURBVCjPNdDBatwwEAbg 32YFG59EkC49LhQ2fgq5dKHxSbtoBPEth0KjpzBLDyGnUupAc/IuMdjzlB05VL7Mx1gzowHg87f3 kOOgETam1husJAuz01bCCk0gRxutHXDqCxI4fSugd7XCZwTB0RmpkzEp8o/kSx7lt4mI7khju11h 6Z78tqoyDkSg02V77uFVtILYu7KHfTeWFAV8y/gpfWzR9sh3ghU0/nydgUGKkVKh5Iyc2dtQ5owN 9kB7Y8B7QAVzJGiDOQGHUDhBV891rqb6UE6J+QPPoVqYK4G0rzif6kUmoEOd47GUIeQ1a+Jr0TIW styxtC++MFjbFCUjUyXwQF13Zt4tlwimp/t0zlMWERd6uksuAyyglvtu2GTIptrUy/tGx3iW5X4S xOsvgSrcjbMUoRl/LDU3MkYynvGmqFlyR5I7Y0NX9rIukmqjt7cPg8Q58xhUXGOSQY+hiANP1L0y 43ugB5JpeZgZKU5HYin9d5exnJhfh8RvjPbIpuZhSrPceeHlR+JpkcUxfi95gcwrxs8fyAdLXLr/ +AcNOcONF1pRZwAAACV0RVh0ZGF0ZTpjcmVhdGUAMjAyMi0xMC0xNVQxMDowMDowMiswMDowMLDE cj4AAAAldEVYdGRhdGU6bW9kaWZ5ADIwMjItMTAtMTVUMTA6MDA6MDIrMDA6MDDBmcqCAAAAAElF TkSuQmCC X-Now-Playing: Bill Callahan & Bonnie Prince Billy's _Blind Date Party (2)_: "I Want To Go To The Beach" X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:245533 Archived-At: Stefan Monnier writes: > After spending many milliseconds thinking about it, my conclusion is > that the bytecompiler should add a little code snippet like > (puthash load-file-name t comp--no-native-compile) in the > file if `no-native-compile` was specified. So it then be easy for the > lazy native compilation to detect that it should skip this file (since > lazy native compilation is triggered after loading the file) by just > consulting `comp--no-native-compile`. > > For that, there's no need to change the way `no-native-compile` is specified. True, but it's kinda hacky, and if possible, I'd like to avoid adding more hacks in this area... >> That is, in this case, we'd say >> >> (pragma 'no-native-compile) >> >> somewhere in the file. > > I guess that could work for `no-native-compile`, indeed. But if you ask > to native compile this file and the pragma is halfway down the file, > what happens? Yes, that's no good. Uhm... we could make a rule that all `pragma's have to appear as the first form(s) in a Lisp file? And error out if somebody tries to add a `pragma' later in the file. I think that would make sense in general -- we're trying to express something about the file as a whole, after all. >> We could have >> >> (pragma 'dynamic-binding) > > I guess this one could work (of course, it'd have to be at top-level), > and we could switch back&forth within the same file (yuck!). > > But if we allow such `pragma` to be output by macros, then it becomes > tricky for `eval-region` to reliably decide which dialect to use. Hm, yes... But we have the same issue today, don't we? That is (progn (pop-to-buffer "*foo*") (emacs-lisp-mode) (insert ";;; -*- lexical-binding: t -*-\n(message \"Lex: %s\" lexical-binding)") (eval-region (pos-bol) (point))) Well, OK, that's the same result with point-min, but... > So we could allow such `pragma`, but we'd likely end up restricting its > syntax so we're able to find it with something like a regexp search, so > in the end it's not clear what's the advantage over > file-local variables. If they have to be the first forms, there may be some advantages...