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: Merging scratch/no-purespace to remove unexec and purespace Date: Tue, 17 Dec 2024 15:47:14 -0500 Message-ID: References: <87zfku6ra9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17463"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Stefan Kangas , emacs-devel@gnu.org, Pip Cet To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 17 21:48:25 2024 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 1tNeUT-0004Q2-2u for ged-emacs-devel@m.gmane-mx.org; Tue, 17 Dec 2024 21:48:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tNeTl-0008FQ-1j; Tue, 17 Dec 2024 15:47:41 -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 1tNeTT-00083f-VI for emacs-devel@gnu.org; Tue, 17 Dec 2024 15:47:26 -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 1tNeTS-0004gp-0T for emacs-devel@gnu.org; Tue, 17 Dec 2024 15:47:23 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 9AF884446C2; Tue, 17 Dec 2024 15:47:15 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1734468434; bh=LkpHzXQyKZUcukfpjxE1mNFCcxBFQtRS/6y+jW/O3dk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=f0InzR3kIZK1Xw48cKz7zevqf28hRaAI0mJKgk+hSRc5uuZh1rTBEWSQBVlJCbeM7 qOzDxGv4KhBePX/1KOuBuVBflIM9biAzZGLU+S/j8xAwWlN60GAbgAwKWx2usBNHsl yhwyyQNJrBqH92laWr5xzJalL3BRhuI/4EmESTy3qm080NDL46o8mJ7uuXMdVR4EM6 oUAXrDh/A4u3jnGbzcV4m3rA+KfdLWdNh84qB/YwdYqIuSXnqKX/mlL4TjdPEANsDN eCq9qe+HYmE7JnfhNd25KxjRWXbovgnNByqvtck80HSsxFx0/mfKSpVgj0VhXWsS0P tbb3bwjv0g4cw== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 929BF4446BA; Tue, 17 Dec 2024 15:47:14 -0500 (EST) Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 7CE9B12014F; Tue, 17 Dec 2024 15:47:14 -0500 (EST) In-Reply-To: <87zfku6ra9.fsf@gmail.com> (Helmut Eller's message of "Tue, 17 Dec 2024 20:30:38 +0100") 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, 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:326616 Archived-At: >> We, the maintainers, believe that the scratch/no-purespace branch is >> now ready to merge, and would appreciate any final feedback, testing, >> and code reviews. Specifically, the branch has been primarily tested >> on GNU/Linux and macOS, so testing on other systems would be greatly >> appreciated. > > Do you have an estimate what removing purespace will cost in terms of GC > time? I mean something like "1ms per collection". Or perhaps a > suggestion how I could measure it? In the pdump case it should have no effect at all, or maybe even a slight *speedup*. That's because the pdump already fails to take advantage of the purespace (i.e. the GC traces through the purespace like the rest of the heap). Stefan