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: Finalizing 'inhibit-automatic-native-compilation' Date: Tue, 14 Feb 2023 10:09:44 -0500 Message-ID: References: <837cx8cey0.fsf@gnu.org> <83pmaddj5e.fsf@gnu.org> <83bklwe6i6.fsf@gnu.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="10770"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: akrl@sdf.org, emacs-devel@gnu.org, larsi@gnus.org, rlb@defaultvalue.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Feb 14 16:10:57 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 1pRwxM-0002b6-Fi for ged-emacs-devel@m.gmane-mx.org; Tue, 14 Feb 2023 16:10:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pRwwm-0007fe-5e; Tue, 14 Feb 2023 10:10:20 -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 1pRwwh-0007cu-Qi for emacs-devel@gnu.org; Tue, 14 Feb 2023 10:10:15 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pRwwe-0003m2-UI; Tue, 14 Feb 2023 10:10:14 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id DEAFA4426D2; Tue, 14 Feb 2023 10:10:01 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 843E24426B9; Tue, 14 Feb 2023 10:10:00 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1676387400; bh=huGXPJNNM1lwDY3Eexvi3PQuFtP1TKNawByHDVnM8p4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Mr1RuJdGBYyeXEiAnQrZ3/SNu+YdGJ/VmEaRbjtlYKmU8ffdpKdMqGvAQLwY+SLbt mH2jvLZrkFUzjb9GZDdy7x5IWnQesM9TJ2o2Snc9lo/2a4Y/WjpoznMq/ltUcPjTNN HXKRJsT0rthrd9uh91krYr8MKuf77g19EkoJhUJTOLDzatgEBhn1BdLFsD0EAcBSZb XaKNfgejhCc/gBigY/e0rE9hvlZFSwAIpcz7kxGtt8Z4tVhEfKBdHwrIQV0j26Y93K wvGaScnNDkfCr1lJ/97Tppm49RyKgJc8nJjS53HocRyEeDj89ZvNFZtqLasW3kO323 ZV6hcteJFcBvg== Original-Received: from pastel (69-165-145-123.dsl.teksavvy.com [69.165.145.123]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B5654121C5C; Tue, 14 Feb 2023 10:09:59 -0500 (EST) In-Reply-To: <83bklwe6i6.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Feb 2023 15:11:45 +0200") 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 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:303277 Archived-At: >> > If we do this, any reasons not to do that also for any other .eln >> > files, not just trampolines? >> >> Generating&using trampolines is necessary for correct execution. >> In contrast other `.eln` affect only performance. >> >> Generating files in `temporary-file-directory` is definitely not ideal, >> so I'd rather limit it to the cases where it's necessary for correctness. > > If by this you mean that we should not allow > comp-enable-subr-trampolines to have a string value, No, that's not what I mean (and I don't understand the connection you see between what I wrote and what you wrote). > meaning the directory to place the trampolines, then I think we > should, since that can support use cases other than unwritable > home directory. I have no objection to the string value of comp-enable-subr-trampolines`. Stefan