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: MPS GC and its implications Date: Fri, 03 May 2024 16:33:07 +0300 Message-ID: <86a5l7hvfw.fsf@gnu.org> References: <87ttjlabic.fsf@gmail.com> <87v8408wsr.fsf@gmail.com> <87o79sasl5.fsf@gmail.com> <87plu72y8h.fsf@gmail.com> <877cgfwe5g.fsf_-_@gmail.com> <871q6mptkj.fsf@gmail.com> <86wmodofvw.fsf@gnu.org> <87frv1hclv.fsf@gmail.com> <86plu3i1nr.fsf@gnu.org> <87ikzvnnao.fsf@gmail.com> <86h6ffi00a.fsf@gnu.org> <878r0rnkpu.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12899"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gerd.moellmann@gmail.com, acorallo@gnu.org, emacs-devel@gnu.org To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 03 15:33:56 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 1s2t2y-000374-3J for ged-emacs-devel@m.gmane-mx.org; Fri, 03 May 2024 15:33:56 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s2t2I-0006sW-Bi; Fri, 03 May 2024 09:33:14 -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 1s2t2G-0006rn-0W for emacs-devel@gnu.org; Fri, 03 May 2024 09:33:12 -0400 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 1s2t2F-0005RO-OI; Fri, 03 May 2024 09:33:11 -0400 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=wCYDv1K+6VYUCeQ/borDqDbUCOezZDStNdcr9hBTdtY=; b=irxxH+nyyFFW AAtTDCjoJ6tva4itG4fnuWsK+awTn/zs+VSqjFIlR08eDqJDPA+m8gMhYQsKuO9OoDD2tz1nKpQ4I ne9UIWqp6tavdivbzQA0W3RF/fAJHEvlJzi2sGUIRWN4aDNT9SH7+IAJR+jHaKthzK4msuKHYVrqP kG7Q/ceGRpXW8J6Xs3Cwb/h3NxDZe/eE2rASjKwKU8wWP1FtrVa0TKzSXB/DiX8qQNN552pfG/+J0 0qMjOhPcEtLVuu06Kq1FTqzZzDTxxKA/DsK/VCGdHFK8jhdW1uqyoniMxMn0ud+dHMLz1Qx1euB9e WjwVOjVHp82C2+3gAsEmtA==; In-Reply-To: <878r0rnkpu.fsf@gmail.com> (message from Helmut Eller on Fri, 03 May 2024 14:28:13 +0200) 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:318679 Archived-At: > From: Helmut Eller > Cc: gerd.moellmann@gmail.com, acorallo@gnu.org, emacs-devel@gnu.org > Date: Fri, 03 May 2024 14:28:13 +0200 > > >> Memory barriers could be used for synchronization. When the mutator > >> hits a barrier, it executes the signal handler. The signal handler asks > >> the collector what to do. Essentially synchronizing those two. > > > > If this happens, I should have seen GDB intercept the exception and > > kick in. But it doesn't. (It also would have slowed the program > > quite a lot, I think.) > > Don't call igc--collect and do something to generate enough garbage. > Then you'll see it. I don't. Or maybe I don't know how to "do something to generate enough garbage". Can you suggest a couple of such "somethings"? I tried scrolling through xdisp.c and "M-x occur RET glyph RET" in xdisp.c (which finds about 3500 matches).