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: Finalizing 'inhibit-automatic-native-compilation' Date: Mon, 30 Jan 2023 14:47:47 +0200 Message-ID: <83k0145guk.fsf@gnu.org> References: <837cx8cey0.fsf@gnu.org> <83357vauh5.fsf@gnu.org> <837cx6a8me.fsf@gnu.org> <83357ua6ja.fsf@gnu.org> <83zga28ra8.fsf@gnu.org> <83r0vd97s0.fsf@gnu.org> <83lell73yv.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2394"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, akrl@sdf.org, larsi@gnus.org, rlb@defaultvalue.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 30 13:49:00 2023 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 1pMTal-0000PT-RB for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Jan 2023 13:49:00 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pMTZz-0002FV-45; Mon, 30 Jan 2023 07:48:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pMTZi-0002EB-L1 for emacs-devel@gnu.org; Mon, 30 Jan 2023 07:47:56 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pMTZi-0007Ft-6p; Mon, 30 Jan 2023 07:47:54 -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=qxX6y8ogzjJnClpOZXKi6HMAaAfGDGOVo869ITO/Ngk=; b=aMgf+FLIrbAW ci2UpCvtjL1QDzXn61QKvp0Y2NVy/iKcS553K5dmfgWArX8z6+D8gjV/p6nbghgWnomlZdEdt7vie DFEZkTdEXgbi929fKsHRt2UteFU0+QtsweMDMFqqk8aizObW7bcJk8TdbF4q8PcKrOrkfTHSyPJ+f x0fTlKrMEIIHhByNd3shgMHWi9nLu7ZEg2hDxx5hSfire6ApRToRYlfrwwVPBhvosNaFYus9+3I7S cmyFOW5u2j7H5P5ORNvfJY+AAog3nWviddnv7JqaOIzUwyAn4qXdGk9P4i2bh3MoT1HKIC77hOy9H 357Y1l9Opve8I/Tklo2DHQ==; Original-Received: from [87.69.77.57] (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 1pMTZh-0004js-IX; Mon, 30 Jan 2023 07:47:53 -0500 In-Reply-To: (message from Stefan Monnier on Sun, 29 Jan 2023 21:30:41 -0500) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302777 Archived-At: > From: Stefan Monnier > Cc: emacs-devel@gnu.org, akrl@sdf.org, larsi@gnus.org, rlb@defaultvalue.org > Date: Sun, 29 Jan 2023 21:30:41 -0500 > > >> > IMO, the "no writable eln-cache" scenario should be solved by tweaking > >> > native-comp-eln-load-path to include a writable directory. That > >> > writable directory could be temporary-file-directory, or it could be > >> > anything else, but it should be specified by the caller/user, not > >> > pulled out of our hat behind the scenes. > >> > >> That's where I disagree: when it comes to trampolines I think users > >> would be better served if we silently used an eln-cache in > >> `temporary-file-directory` rather than ignoring the subr's redefinition > >> (usually due to an advice). > > > > Why? in the Debian use case all they care about is that the file is > > not written to HOME, and my proposal doesn't break that. > > AFAIK your proposal breaks some uses of advice. Are you alluding to some uses we've heard about, or is this just a theoretical possibility? AFAIU, for this to be a real issue, we'd need a use where the user (a) disables native-compilation for some reason, but (b) still wants advices of natively-compiled code to work. Why would someone do something like that? > > The trampoline isn't needed in their scenario, so there's no reason to > > generate it. > > I don't know if they need trampolines, but I wouldn't be surprised if > they do on occasion. We'd need them to answer that and explain.