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: Thu, 26 Dec 2024 09:33:24 +0200 Message-ID: <86msgizynv.fsf@gnu.org> References: <87o713wwsi.fsf@telefonica.net> <86o7112rnq.fsf@gnu.org> <867c7p2nz4.fsf@gnu.org> <87y104aih6.fsf@protonmail.com> <87ikr89gyp.fsf@protonmail.com> <87jzbn8zmu.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="1167"; mail-complaints-to="usenet@ciao.gmane.io" Cc: pipcet@protonmail.com, stefankangas@gmail.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 Thu Dec 26 08:34:05 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 1tQiNh-00007G-I4 for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Dec 2024 08:34:05 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tQiN8-0004V1-Py; Thu, 26 Dec 2024 02:33:30 -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 1tQiN6-0004Um-R7 for emacs-devel@gnu.org; Thu, 26 Dec 2024 02:33:28 -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 1tQiN6-0003j3-2f; Thu, 26 Dec 2024 02:33:28 -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=dZzRuKSbbYSjsu3IVlOs6dxyeZYMRlk64NXmv8gaEWI=; b=QtVbAg+r+8Yk36bCRpDS 2R2rBseYfuhgdOMAaS4NLrl2Qn0g4o6T3ztHy9cVujw5+IhXnUEmk13yZ7ngVDHjAaOLk/Tt9qPDI cLQv6boxsuDvLBrlBWHzN3qFagKw98+kMPfYY/Zw1qjsJvHDRxtoOzCf/T6TLjfhPZ8w/jfLOrHyq TWLVMODuIgJK1QS/y7ckSToQtFxMccFibXmgakg0mD59adlBX8vR7h7YnwQaWonc5XnKgVtztPNqO AQPDYfLPljAnDN91qe5d3WfDqa2cGO4TyPE/n6RoMFz9O2U2Vfum8YXrWUcdagxS+fgkX5LV1GcKu 1Dz/VMWzoOrUTA==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Thu, 26 Dec 2024 06:22:17 +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:327136 Archived-At: > From: Gerd Möllmann > Cc: Stefan Kangas , Eli Zaretskii , > ofv@wanadoo.es, emacs-devel@gnu.org, eller.helmut@gmail.com, > acorallo@gnu.org > Date: Thu, 26 Dec 2024 06:22:17 +0100 > > I'm coming to all this from a completely different angle. My > understanding is (1) the signal handling/MPS thing, is the only thing > preventing landing in master That's not so. It is not the only thing we need to figure out and solve before we can consider landing this on master. At the very least, we have unresolved issues with patches to MPS for some platforms, whereby we considered forking MPS or some other course of actions. Also, there are several FIXMEs in igc.c itself. For the MS-Windows build, we have the issue of registering some threads with MPS (see our discussion Re: "MPS: w32 threads" back in May). So we still have a way to go. > My approach is "focus!" :-). Get a signal handling/MPS thing into igc > that is good enough to be accepted, land in master, and only then > proceed with anything else that has come up. The "focus!" approach is correct, IMO, but landing the feature on master is only possible if we believe the branch is stable enough, because there are enough people who use master for production to consider its being reasonably stable a necessary requirement. I believe we still have unresolved reports about freezes on GNU/Linux, so we are not there yet. I also don't have a clear idea of which Emacs configurations (in terms of toolkits, PGTK yes/no, native-compilation yes/no, etc.) were or are being tested on GNU/Linux -- this is also relevant to assessing the stability.