From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Concurrency via isolated process/thread Date: Tue, 25 Jul 2023 09:27:03 +0000 Message-ID: <87r0owqr2w.fsf@localhost> References: <871qhnr4ty.fsf@localhost> <83a5w6cwdr.fsf@gnu.org> <87pm518m0g.fsf@localhost> <83o7kl9tyj.fsf@gnu.org> <874jmd89us.fsf@localhost> <878rb53dkj.fsf@localhost> <83edkxsclz.fsf@gnu.org> <87tttt1mzh.fsf@localhost> <83351ds9de.fsf@gnu.org> <87ila91j6n.fsf@localhost> <83y1j5qoyo.fsf@gnu.org> <87wmypi7s0.fsf@localhost> <87fs5czvs2.fsf@yahoo.com> <87mszk7glc.fsf@localhost> <877cqozc14.fsf@yahoo.com> <87bkg0s9p4.fsf@localhost> <87351cz993.fsf@yahoo.com> <87wmyoqt0j.fsf@localhost> <87y1j4xtgr.fsf@yahoo.com> <87tttsqs5d.fsf@localhost> <87tttsxsd1.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5271"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jul 25 11:27:54 2023 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 1qOEKe-0000z8-5Q for ged-emacs-devel@m.gmane-mx.org; Tue, 25 Jul 2023 11:27:52 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qOEJn-0004QI-5S; Tue, 25 Jul 2023 05:26:59 -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 1qOEJk-0004Pw-Gv for emacs-devel@gnu.org; Tue, 25 Jul 2023 05:26:56 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qOEJh-0004co-J6 for emacs-devel@gnu.org; Tue, 25 Jul 2023 05:26:55 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 804F0240027 for ; Tue, 25 Jul 2023 11:26:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1690277210; bh=AwAmc8yAbS+K80euI4pzvTGaDkw2y5ZN4gBwRTGq6bI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=SA8hJcXx03K7meFAN4s7O/akAdqHaQiVoVWA52BvWWuwASksSaV1OS5BTNojxHlQn BKGxuz6NpwA/LVF04MnhtT9KgThiteSktfeLIGxnxnHphTyhj05P5m3XSkWSkzbIUj zw4ZfpDoYifqV0+wnuEcKjmxrgbbYM/63sQyOBwHITF6a8hrDeQ867xGga0jUoZn8S LhOtfs3mv+qW0194ORF+my6dAfthULSg/NvugESDwDembHxdfQ25AgWpArcyEYSLkR EtjXwwrpGpBHAIUt2xn0se5t4u12aiGgplf5JKvHZ5WHddte58nDagtXzV6xJSDf5i rA1Wg/yKbDVnQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4R9BVx64ZJz6tyX; Tue, 25 Jul 2023 11:26:49 +0200 (CEST) In-Reply-To: <87tttsxsd1.fsf@yahoo.com> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action 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:308084 Archived-At: Po Lu writes: >> Sure, but the whole chapter design shows that READ_ONCE/WRITE_ONCE is >> not the best design. They go deep and complex just to avoid using it too >> much. > > That's because READ_ONCE and WRITE_ONCE both have additional semantics > beyond ensuring that loads and stores are coherently propagated and > received to and from other CPUs. For example, the compiler is not > allowed to merge loads and stores, although it and the CPU are both > allowed to reorder them. > > We don't have similar requirements in Emacs. I've seen a couple of volatile variables in the code. So, there is at least some fighting with GCC optimizations going on. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at