From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Questions about throw-on-input Date: Tue, 12 May 2020 17:37:08 +0300 Message-ID: <83wo5h8bjf.fsf@gnu.org> References: <72ec0924-42f3-9f55-7edb-b2f9b678f707@web.de> <742c0a6f-fc4c-6ac1-0233-85ad8671e199@dancol.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="31631"; mail-complaints-to="usenet@ciao.gmane.io" Cc: alexanderm@web.de, emacs-devel@gnu.org, monnier@iro.umontreal.ca, yyoncho@gmail.com To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 12 16:38:40 2020 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 1jYW3L-00085O-G6 for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 16:38:39 +0200 Original-Received: from localhost ([::1]:44354 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYW3K-0005XS-Ig for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 10:38:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57250) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYW2E-0003kX-9b for emacs-devel@gnu.org; Tue, 12 May 2020 10:37:30 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41918) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYW2D-0001MR-2z; Tue, 12 May 2020 10:37:29 -0400 Original-Received: from [176.228.60.248] (port=2625 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jYW2B-00086d-V0; Tue, 12 May 2020 10:37:28 -0400 In-Reply-To: <742c0a6f-fc4c-6ac1-0233-85ad8671e199@dancol.org> (message from Daniel Colascione on Mon, 11 May 2020 19:39:33 -0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:249971 Archived-At: > Cc: eliz@gnu.org, yyoncho@gmail.com, emacs-devel@gnu.org > From: Daniel Colascione > Date: Mon, 11 May 2020 19:39:33 -0700 > > > And while we are on the topic of threads, I wonder what is the > > maintainers' opinion on https://nullprogram.com/blog/2018/05/31/, > > specifically this part: > > > > > Update: ThreadSanitizer (TSan) quickly shows that Emacs’ threading > > > implementation has many data races, making it completely > > > untrustworthy. Until this is fixed, nobody should use Emacs threads > > > for any purpose, and threads should disabled at compile time. > > Is TSan is just getting confused by the global lock? We don't have any > parallelism, so data races shouldn't be happening at all. There doesn't seem to be any detailed description of the races it uncovered, so it could well be that this is a red herring. I do know about some racy conditions where we release the GIL and select the next thread to run, but I'm cannot be sure they are the same ones this blog is talking about.