X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20210112;
	h=message-id:date:mime-version:user-agent:subject:content-language:to
	:references:from:in-reply-to:content-transfer-encoding;
	bh=sXWFUVXV6l6PjWb3r8zNuyeRLuKHxR9VkcsUz3fr2f4=;
	b=GsmFtiwOPCrFh/iqfM6LS2nJWQB8MpXskwb7cZ+RYwklfGI0lZOKjAmym1p8HvPQ1G
	j3Azfrszg5ooAJMeH7/ST0GxTLGYEQeqjtqoVpnswQVvs+0oRN+hfr3TYsLz6hIrN523
	5Sbjk2H1SDfa1A2RHUUP30m0/ymOxhcqGaw3J4mA93nQXfrbKSLGsJKP9FSbn/lsjczN
	LdEu5rG12OA1sbKsB3O4lQoZnRLdpD04iAIixx5MD42K5HvMXs0D/cSC8kGF5TpMgGAZ
	47BUczhKUqAZXtW/sbcTkPl7bEoNVRJlkEWi3KDBGga5oiHIVfS9H2GTaLqueHeAkPAO
	A99w==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20210112;
	h=x-gm-message-state:message-id:date:mime-version:user-agent:subject
	:content-language:to:references:from:in-reply-to
	:content-transfer-encoding;
	bh=sXWFUVXV6l6PjWb3r8zNuyeRLuKHxR9VkcsUz3fr2f4=;
	b=RfuQbQq+JS4b7o59fXcXLcrap6ewXpSWXt5JTu5ETd87TfD1bGBtlvPUKUzIHy7OfW
	/x1lXh3LeDZeC6BuyudXm7uTC2pD8fzwhhjuW/m6ohPI6dFF5Ja66X6fm1G4SwKyw1AU
	Jrr5zN0pN8BbNtaX1eZ4ANKJEY++54nqIoAHcI32rXk/rfViaau7sPvbiOjp/3Vwv2tW
	/JpWo0I/0ZQoHNVMaq9Vn24UGg+Z+khn7Jbq6XsztIlsYJ7PzWRRT/D8lFQlncjmkHmS
	3UGojb1jvlQ37BM0qQJ+I6Ff/TzvOx/Y45XqpIUgHAzyxQF2ZFv7QKpqC7ns6OZC4Lz0
	okRg==
X-Gm-Message-State:	AOAM5335sLBKNy3eGEmEqUYVI8hWz3gw9WzG9ap3TYm9b/9c660n7zE5
	Hsg58e512/1FjV4lGGjQYVAX6hbzb+8=
X-Google-Smtp-Source:	ABdhPJwYLSlcSs11WHlDQgR1IPt1eRqSwJ+UXcl925Z+/qtpAapGxQDKf2Fa3VuY0jiXJbMo+uqt6A==
X-Received:	by 2002:a05:6402:2694:b0:42b:251d:185 with SMTP id w20-20020a056402269400b0042b251d0185mr43072396edd.44.1653747874786;
	Sat, 28 May 2022 07:24:34 -0700 (PDT)
Message-ID:	<a7cb87a5-a7a6-d44f-506c-dd575a3df476@gmail.com>
Date:	Sat, 28 May 2022 16:24:33 +0200
MIME-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101
	Thunderbird/91.9.1
Subject:	Re: GNU pth during djgpp build time?
To:	djgpp AT delorie DOT com
References:	<a52c077b-55b2-4a1f-877e-ebdcef7c1e01n AT googlegroups DOT com>
	<224eb9dc-337e-f78f-ea4e-58bb15eb580b AT gmail DOT com>
	<7466fdea-7958-467e-aa06-f051df1bf3fen AT googlegroups DOT com>
	<13904ce4-1b5c-c82f-7939-d0cc40c61d3b AT gmail DOT com>
	<13cd46e4-48a2-4cbf-804a-07c637ee1f37n AT googlegroups DOT com>
From:	"J.W. Jagersma (jwjagersma AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
In-Reply-To:	<13cd46e4-48a2-4cbf-804a-07c637ee1f37n@googlegroups.com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 2022-05-25 23:04, janezz55 (janezz55 AT gmail DOT com) [via djgpp AT delorie DOT com] wrote:
>> whenever an exception is thrown. So it makes sense to use a mutex here, but 
>> in our case it's just not necessary to do so on startup.
> 
> Yeah, I have a feeling you're already working on a patch :) So, we will have std::thread under dos, amazing.

I haven't looked further into it yet.  Should be trivial to remove the mutex
access and see if any other issues pop up.  But I don't like the idea of
requiring a custom patched gcc for this.  Plus the whole thing seems far less
efficient than what I already have, and I think gcc will also generate overall
worse code with --enable-threads.

- Raw text -