From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pip Cet via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: igc, macOS avoiding signals Date: Mon, 30 Dec 2024 11:11:20 +0000 Message-ID: <87r05p1l5t.fsf@protonmail.com> References: <799DDBC5-2C14-4476-B1E0-7BA2FE9E7901@toadstyle.org> <86ed1rswup.fsf@gnu.org> <87h66loc17.fsf@gmail.com> Reply-To: Pip Cet 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="19811"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Helmut Eller , Eli Zaretskii , spd@toadstyle.org, 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 Dec 30 13:00:41 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 1tSERt-0004zI-BC for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Dec 2024 13:00:41 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tSER2-0006fp-Pa; Mon, 30 Dec 2024 06:59:48 -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 1tSDgI-00074G-V9 for emacs-devel@gnu.org; Mon, 30 Dec 2024 06:11:31 -0500 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 1tSDgG-0004Lb-4b for emacs-devel@gnu.org; Mon, 30 Dec 2024 06:11:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1735557085; x=1735816285; bh=3Jh6Mha+W1OEW0V3ANV5y7FTc5WqIcwH94gAz2JMVBA=; 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:List-Unsubscribe:List-Unsubscribe-Post; b=cV8rrZAN0J8Vunwicve9UtEBKMZkQ2yvZ7CJEGm5k6NYxIOmcoxsLexsLyRTLqSiD L1p9JvnWPiaK4geBHoYibh+u2oZh7uznja40c37ZLKGLgHPDRj3MhjpVQBohrDxVD2 pMaaDiuwCG7yjMP6CbWRxeoUENm0XcbCwMkUWekuXwxKRjChDSB7oKjFCaodBYlvnZ ch5bdV1iZcEhDvYq+kWm0k/9niZ27x6K1FaJz8zVz0hdSffI4t1Rc46W+BO3FNEt0O r9V9xzj0CuuIwnyIEhdVGHafleQx6ChvkyrXX0CcMpMW7TxcPkqp44iMkyqziNhfyB p/0kKIRvZCbLg== In-Reply-To: Feedback-ID: 112775352:user:proton X-Pm-Message-ID: e8226903bd4164bf7e701c07c10b6e16ab0d28eb 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_H2=-0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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, 30 Dec 2024 06:59:40 -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:327410 Archived-At: Gerd M=C3=B6llmann writes: > Helmut Eller writes: > >> On Mon, Dec 30 2024, Gerd M=C3=B6llmann wrote: >>> Anyway, it definitely seems to be the case that MPS is _not_ running GC= s >>> concurrently, unless it would do things that I find highly unlikely. >>> >>> I find that a bit, let's say, disappointing, TBH :-(. >> >> Richard Brooksby thinks[*] that MPS could be concurrent with software >> barriers. Feel like going down that road? :-) >> >> Helmut >> >> [*] https://memory-pool-system.readthedocs.io/en/latest/design/shield.ht= ml#concurrent-collection > > Yep, found that too, with git grep. > > Still grumpy. > > I'm afraid Modifying MPS is not my thing, But What about using something > more modern like Oilpan (aka cppgc) from V8? Can be used as a lib, is > concurrent for real. That would also be a perfect time to lift Emacs to > C++. Ultimately, I'm still surprised there isn't that much work on precise GC with compiler support, allawing us to mark the C stack precisely by emitting DWARF tables indicating precisely which registers or stack locations references live in at the time of an interruption. (Identifying them is the easy part. Emitting only code which allows you to move such references asynchronously is the hard part). But if you're doing all that, why not go all the way and implement resumable exceptions? (I wasn't going to mention it, but there's always my experiment with the SpiderMonkey garbage collector. Lots of bitrot, and I never got things working quite the way I wanted to (no ambiguous references)). Pip