From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: master 05d240997a 2/2: Add native-compile-prune-cache command Date: Fri, 22 Jul 2022 19:38:09 -0400 Message-ID: References: <165675959499.8421.12451308740112322312@vcs2.savannah.gnu.org> <20220702105957.4B7EFC016B5@vcs2.savannah.gnu.org> <87bkthedix.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6046"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Robert Pluim , emacs-devel@gnu.org, Lars Ingebrigtsen To: Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 23 01:40:58 2022 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 1oF2GP-0001Ob-Im for ged-emacs-devel@m.gmane-mx.org; Sat, 23 Jul 2022 01:40:57 +0200 Original-Received: from localhost ([::1]:32856 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oF2GO-0001cT-0z for ged-emacs-devel@m.gmane-mx.org; Fri, 22 Jul 2022 19:40:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60724) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oF2Dn-00009v-Uw for emacs-devel@gnu.org; Fri, 22 Jul 2022 19:38:16 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:65497) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oF2Dl-0004sh-JI for emacs-devel@gnu.org; Fri, 22 Jul 2022 19:38:15 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 0629E4417B6; Fri, 22 Jul 2022 19:38:12 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 950AD44179B; Fri, 22 Jul 2022 19:38:10 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1658533090; bh=TxlwwTSwMOcafbt5d9OfupTpv8MUSpB8gnd1Ws1DCS4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=EAobIiwrDDwRZHH/eCtcpIG7lCDR+FVWK9KjCsgzs9AIC6+49R2k5FFYLMXMv6mb8 l8bdOzkP5OFcXnq+94NH1okx0g54gTpPxjGXINwQ7a6hoB+7dMXSWowC4h+OMGbzwE cavcvakOT4IJ9JlqfOeuRroColIyfZKT8+y+dkD3uCEl9rhOhtHrc8uqjyP0x676mq GkDpxhwvBv2mMOaS395o8p3n7YggCOv9XqacjLdrK2Mg1sjfYyqI85K+KP3/SQ6eid Npfbc/rTZdhbxIyucqTRKNIBYw/Fh+jvp+Zk9d7nS+3M5qTWMvvbeB9KFOCuyc//GT mHq7k/b0pN3/w== Original-Received: from pastel (unknown [45.72.195.111]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 5703012020A; Fri, 22 Jul 2022 19:38:10 -0400 (EDT) In-Reply-To: (Andrea Corallo's message of "Fri, 22 Jul 2022 23:17:44 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:292492 Archived-At: Andrea Corallo [2022-07-22 23:17:44] wrote: > Stefan Monnier writes: >>> do we support loading comp.el and using in non native builds? >> >> We should support loading `comp.el`, yes. >> Using it (e.g. calling functions therein) probably not unless the call >> can be given a reasonable semantics. > > Sounds sensible, but then should we protect all functions or just say > that using them not supported? I don't think we can/should have a general policy in this respect. I'd rather do it on a case-by-case basis. Regarding "prune cache" I earlier suggested that it could just "prune nothing" when called from an Emacs with no native-compiler, but I later saw that the docstring says: Remove .eln files that aren=E2=80=99t applicable to the current Emacs i= nvocation. so another valid option would be for it to delete *all* the .eln files when called from an Emacs without support for native compilation (because none of the .eln files are "applicable to the current Emacs invocation"). Stefan