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: Some experience with the igc branch Date: Mon, 23 Dec 2024 21:00:53 +0200 Message-ID: <864j2u442i.fsf@gnu.org> References: <87o713wwsi.fsf@telefonica.net> <87ldw7fwet.fsf@protonmail.com> <87a5cnfj8t.fsf@protonmail.com> <86seqe4j4f.fsf@gnu.org> <87ttaucub8.fsf@protonmail.com> <87pllicrpi.fsf@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8432"; mail-complaints-to="usenet@ciao.gmane.io" Cc: pipcet@protonmail.com, ofv@wanadoo.es, emacs-devel@gnu.org, eller.helmut@gmail.com, acorallo@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 23 20:02:23 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 1tPnh9-00023q-Gb for ged-emacs-devel@m.gmane-mx.org; Mon, 23 Dec 2024 20:02:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tPng4-0000xx-P5; Mon, 23 Dec 2024 14:01:16 -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 1tPnft-0000uZ-89 for emacs-devel@gnu.org; Mon, 23 Dec 2024 14:01:12 -0500 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 1tPnfq-0006dx-TJ; Mon, 23 Dec 2024 14:01:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=44UljX0jUjeMSGw3ZgCp8+S6KaYptMBeNNMf+9yEXLY=; b=QE9pDp//knynpaGsT4vS UcnAsv/bjueRk1buPp/S13iEi47TvKKd367nC7UHda1n4ZW2cDICZE9Sn23d3N17hB9kubXMagHP0 YvOVE6S+bAPJoftUdNfL68FxGQ2y+z58I1ONzVcic4jJrqbi1ruBtV1Op0Ef5+Pf+eyCDvLH/evDv OUCa3ch1pEnUOQnBxYcqgMdtb9WgBIHyKxNhrFZMGxKUekcJ5ZSqPeIcZi8BGAvFjU+yJDxX1cwEb st10aa/O/YloPgSj8h4Iu3fd7WN/ZMwleWi70S7n0eKuHi1B8Uf4c4uVnk7YwroUa/Axxi+UEBDbi Tlpjgnh28tUs9w==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Mon, 23 Dec 2024 18:44:42 +0100) 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:326930 Archived-At: > From: Gerd Möllmann > Cc: Eli Zaretskii , ofv@wanadoo.es, emacs-devel@gnu.org, > eller.helmut@gmail.com, acorallo@gnu.org > Date: Mon, 23 Dec 2024 18:44:42 +0100 > > BTW, do you know which signal handlers use Lisp, i.e. allocate Lisp > objects or access some? All? Or, would it be realistic to rewrite signal > handlers to not do that? SIGPROF does (it's the basis for our Lisp profiler). SIGCHLD doesn't run Lisp (I think), but it examines objects and data structures of the Lisp machine (those related to child processes). > One thing I've seen done elsewhere is to publish a message to a message > board so that it can be handled outside of the signal handler. Something > like that, you know what I mean. This is tricky for the profiler, because you want to sample the function in which you are right there and then, not some time later. For SIGCHLD this could work, but it might make Emacs slower in handling subprocesses (there are some Lisp packages that fire subprocesses at very high rate).