From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.tangents Subject: Re: Shrinking the C core Date: Fri, 15 Sep 2023 19:11:22 +0200 Message-ID: <877core4zp.fsf@dataswamp.org> References: <83r0n0lwm7.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13183"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-tangents@gnu.org Cancel-Lock: sha1:/pYKbCUq5fYnbK7QupW3QziE7+c= Original-X-From: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Fri Sep 15 20:34:57 2023 Return-path: Envelope-to: get-emacs-tangents@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 1qhDeb-00038C-Fe for get-emacs-tangents@m.gmane-mx.org; Fri, 15 Sep 2023 20:34:57 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qhDeA-00086z-4R; Fri, 15 Sep 2023 14:34:30 -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 1qhCLv-0002KQ-Tn for emacs-tangents@gnu.org; Fri, 15 Sep 2023 13:11:35 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qhCLu-0002NM-ED for emacs-tangents@gnu.org; Fri, 15 Sep 2023 13:11:35 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qhCLr-0006zD-2c for emacs-tangents@gnu.org; Fri, 15 Sep 2023 19:11:31 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-tangents@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=get-emacs-tangents@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Fri, 15 Sep 2023 14:34:25 -0400 X-BeenThere: emacs-tangents@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Original-Sender: emacs-tangents-bounces+get-emacs-tangents=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.tangents:1093 Archived-At: Eli Zaretskii wrote: >> I think the biggest problem with uncooperative >> multi-threading in Emacs is that Emacs has so much global >> state. As a consequence, it's unsafe to let two threads use >> anything in the C code in parallel. > > Indeed, that's the main problem. Just adding threads to Lisp > is easy. Is there a part that is safe to access in parallel? If not, or for the part that is unsafe, where is synchronization of access to be done, in Lisp or in C? -- underground experts united https://dataswamp.org/~incal