From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Perry E. Metzger" Newsgroups: gmane.emacs.devel Subject: Re: Can we go GTK-only? Date: Tue, 1 Nov 2016 15:35:33 -0400 Message-ID: <20161101153533.5c5e4670@jabberwock.cb.piermont.com> References: <24db2975-17ca-ad01-20c8-df12071fa89a@dancol.org> <4615E73A-19E2-4B79-9889-D3FA686DDDE6@raeburn.org> <83bmy0pl8p.fsf@gnu.org> <831sywp7ew.fsf@gnu.org> <83y413nsjm.fsf@gnu.org> <20161101124112.2604a08c@jabberwock.cb.piermont.com> <83h97rnnsk.fsf@gnu.org> <20161101132202.02a5e1eb@jabberwock.cb.piermont.com> <838tt3nle1.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1478029005 25109 195.159.176.226 (1 Nov 2016 19:36:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 1 Nov 2016 19:36:45 +0000 (UTC) Cc: dancol@dancol.org, raeburn@raeburn.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 01 20:36:41 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1er9-00041q-Mk for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 20:36:23 +0100 Original-Received: from localhost ([::1]:50793 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1erC-0004WS-EX for ged-emacs-devel@m.gmane.org; Tue, 01 Nov 2016 15:36:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56636) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1eqR-0004W2-PZ for emacs-devel@gnu.org; Tue, 01 Nov 2016 15:35:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1eqQ-0007mg-RJ for emacs-devel@gnu.org; Tue, 01 Nov 2016 15:35:39 -0400 Original-Received: from hacklheber.piermont.com ([166.84.7.14]:46267) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c1eqM-0007iV-AB; Tue, 01 Nov 2016 15:35:34 -0400 Original-Received: from snark.cb.piermont.com (localhost [127.0.0.1]) by hacklheber.piermont.com (Postfix) with ESMTP id 8B745678; Tue, 1 Nov 2016 15:35:33 -0400 (EDT) Original-Received: from jabberwock.cb.piermont.com (jabberwock.cb.piermont.com [10.160.2.107]) by snark.cb.piermont.com (Postfix) with ESMTP id 543792DE01E; Tue, 1 Nov 2016 15:35:33 -0400 (EDT) In-Reply-To: <838tt3nle1.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 166.84.7.14 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:209089 Archived-At: On Tue, 01 Nov 2016 19:46:30 +0200 Eli Zaretskii wrote: > > The standard has required that malloc be thread safe as long as > > pthreads has been around IIRC. > > Requiring is one thing; being able to implement it and weed out the > bugs is quite another. A bug in something as basic as malloc/free thread handling would start causing ported C programs to fail almost immediately. The operating system code would never get out of testing in such a state let alone be released to users. malloc is called far too often. I would not be shocked if some rare latent bugs existed in the average threaded libc, after all, bugs are common in software, and multithreading is particularly hard. However, I would be shocked if a single threaded libc did not handle this particular case in as bug free a manner as the rest of malloc itself. If one is willing to accept the use of the system malloc in the non-threaded case on the premise that it is reasonably bug free, then one should likely accept that it handles thread safety as well. Perry -- Perry E. Metzger perry@piermont.com