From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <i.nixman@autistici.org>
Received: from devianza.investici.org (devianza.investici.org [198.167.222.108])
	by sourceware.org (Postfix) with ESMTPS id AC8453854167;
	Fri, 21 Oct 2022 10:55:57 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AC8453854167
Authentication-Results: sourceware.org; dmarc=pass (p=reject dis=none) header.from=autistici.org
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=autistici.org
Received: from 1.mail-backend.investici.org (unknown [10.0.0.11])
	by devianza.investici.org (Postfix) with ESMTP id 4Mv1bb5QCyz6vMm;
	Fri, 21 Oct 2022 10:55:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=autistici.org;
	s=stigmate; t=1666349755;
	bh=2Wll8ddqXM7CMiq+hBYVI3MynE95kmn048jKXM2rv/0=;
	h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
	b=hMZ5gQZMqIAMGm9oAxcRoxdH0pNz8+Ohc7dNlZnGTM85Y6B+uzM+FIv+exnRGpVKF
	 /yb1QviFWeSvf9iFiIscMYHsJtnCT1cUW+DhYQX6daHZZu0dwODPCiWU7t/gc8MA91
	 I7fESv9iGIdQeIQDVgOiNGHa50EZnnAIysohMRQI=
Received: from 1.webmail.investici.org (localhost [127.0.0.1])
	(Authenticated sender: i.nixman@autistici.org)
	by 1.mail-backend.investici.org (Postfix) with ESMTPA id 4Mv1bb4MmXz5sjW;
	Fri, 21 Oct 2022 10:55:55 +0000 (UTC)
MIME-Version: 1.0
Date: Fri, 21 Oct 2022 10:55:55 +0000
From: i.nixman@autistici.org
To: Jonathan Wakely <jwakely@redhat.com>
Cc: LIU Hao <lh_mouse@126.com>, libstdc++@gcc.gnu.org,
 gcc-patches@gcc.gnu.org, Eric Botcazou <ebotcazou@adacore.com>
Subject: Re: Adding a new thread model to GCC
In-Reply-To: <CACb0b4nZf+-54bFXe38neRCoDy7KMuYU+rmJLpZ5SCZake-wGg@mail.gmail.com>
References: <0f1f223a-3756-1da3-bd1d-b87edd34e1f9@126.com>
 <CACb0b4=4K5b046-hTCgMa9NE8h9Kqp3j8JwTBwww4D=PWQZmHQ@mail.gmail.com>
 <7277b1d9a835d8cc651ab112eac8c2e7@autistici.org>
 <CACb0b4nZf+-54bFXe38neRCoDy7KMuYU+rmJLpZ5SCZake-wGg@mail.gmail.com>
User-Agent: Roundcube Webmail
Message-ID: <b66933f4236686a5c6db74a79f9e4074@autistici.org>
X-Sender: i.nixman@autistici.org
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <gcc-patches.gcc.gnu.org>

On 2022-10-21 10:48, Jonathan Wakely wrote:
> On Fri, 21 Oct 2022 at 11:10, i.nixman--- via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
>> 
>> On 2022-10-21 09:58, Jonathan Wakely via Libstdc++ wrote:
>> > How does this compare with Eric B's proposal at
>> > https://gcc.gnu.org/legacy-ml/gcc-patches/2019-06/msg01840.html ?
>> >
>> > It would be good if we can accept one of them for GCC 13, but I don't
>> > know Windows well enough to determine which is better.
>> 
>> I had the same question...
>> I would like to understand what is the difference?
>> Moreover I would like to understand what is the difference with the
>> already added support for the winpthreads library?
> 
> Well that one's easy, you don't need to use winpthreads if there's a
> native thread model, so you don't need to go through two abstraction
> layers (gthreads and winpthreads), just one (gthreads).


sure!

nevertheless I would like to understand why we have two separate 
implementations (winthreads and mcfgthread)?
what is the difference?


best!