From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet Newsgroups: gmane.emacs.devel Subject: Re: MPS: weak hash tables Date: Mon, 08 Jul 2024 05:37:08 +0000 Message-ID: <1f1JmLSBYHjrhb9MuEByD0oU6q8vo7F9bMhd2aV1rBLZsnt1d_RnbRZEqnHppfMDe4Dus8LSf_BwBe9FWCBvhUEiwH0ysgdOMzArDgdcrY0=@protonmail.com> References: <7PXYgVu5A8knQy6Q03cbm6FjO7s022nC0cqCRtUDhQBgA8ZrpLqmoVRgxD8moCTJpB_52ngFaJnW5JIflrzpHe09WcmbRqiHIdWQZE9kQgU=@protonmail.com> <87tth1xm4n.fsf@gmail.com> <87msmtxkpy.fsf@gmail.com> <87ed85xj67.fsf@gmail.com> <30QY4MPWicZAEpf5sFM5VRGbtFA2S9kRVXdpxH6_NBL-tldtwG1w66f76BbDJ49eeXGP_10WLsknlXTCgAbkxdQzTP0bt-vUo14wW9ngnwk=@protonmail.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="21413"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Helmut Eller , Ihor Radchenko , Eli Zaretskii , emacs-devel@gnu.org To: =?utf-8?Q?Gerd_M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jul 08 13:03:24 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 1sQm9U-0005LI-0f for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Jul 2024 13:03:24 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sQm8Q-0008K3-DW; Mon, 08 Jul 2024 07:02:18 -0400 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 1sQh3u-00047o-Vo for emacs-devel@gnu.org; Mon, 08 Jul 2024 01:37:19 -0400 Original-Received: from mail-40131.protonmail.ch ([185.70.40.131]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sQh3s-0004Qu-BM; Mon, 08 Jul 2024 01:37:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1720417033; x=1720676233; bh=vFHA2W52M1W9uQWztK7Xuw6OW6KUlv6Uz3toIYdTOdw=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=aeL6CgC25aXnohybrsGFpiIDR1JU6OoOiPBxt9isiMUcnkF7rbszoR8QuQ4+0H+AW +6qu2xIGc6dN7gVdi2ZP7ZVnnIHCy3zI+WpGQpW7zK6dMbMTmCufn/k43x+2p6QYFT kbijTHeqSVzJ8e3sIjkq1CEMm/hVK9bmygd5xhAU3PqkazSpVdhlvD1LU4aStZDciz 9GS0wCyko+LNUPgPUGzF80S2bOAtWKrD1okLcHqbK+qbiJh6pv35YpHyaNNiTy+IFl IhvBArvT15nk6T8JLOQEITJTixznSCq3bh76694xSofxxXIt/QtzA9HxH1wfbHOSbw EKhdDbKk/v9ZA== In-Reply-To: Feedback-ID: 112775352:user:proton X-Pm-Message-ID: 69383a815468530304b8f5f505b01ea56d6d8ba7 Received-SPF: pass client-ip=185.70.40.131; envelope-from=pipcet@protonmail.com; helo=mail-40131.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 08 Jul 2024 07:02:15 -0400 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:321534 Archived-At: On Monday, July 8th, 2024 at 05:17, Gerd M=C3=B6llmann wrote: > Pip Cet pipcet@protonmail.com writes: >=20 > > I think it would be better to create a list of strings and concatenate > > them with a single call instead. >=20 >=20 > We could also expose ramp allocation to Lisp for these kinds of things, > so that one doesn't drive the collector nuts by allocating objects in > this manner. We can and should expose that, but probably not use it in this case. It mig= ht be worth it for large vectors, but for strings it probably won't help: Ramp allocation is only supported by AMC (Automatic Mostly-Copying). String data is AMCZ. I've decided to go ahead with the ugly non-bitfield patch, mostly for one r= eason: I'd really like to record previous and current addresses of moved ob= jects somewhere, and the exthdr thing seems perfect for that--it lives in x= malloc'd memory so we can modify it from the scan function. Sorry it took s= uch a lot of sleeping over it :-) So, last chance to object there. Pip