From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id B161C3853543 for ; Fri, 21 Oct 2022 10:48:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B161C3853543 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1666349307; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=SlHxxzR9RIvsWss2F9udcZrQloF9ogWZrtbgSIifbPk=; b=a5qP6Pxzd8XzBqI3hOuwnKkE0jGZabVnowfCEc5szvxd8cgN0gjIMfZTQezuUK5hipgaCc AHckt9qipEC6rlcXZQK9HOzwVm/9FyX3N+/nkAbJwY2hYBnMrOqq5+Dbxk77hM1ieb465A vILcrSPifYxiWv5HQ143DFyQhO77c7I= Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-62-4n89mQ5ZPm-NI0_11xXYYg-1; Fri, 21 Oct 2022 06:48:24 -0400 X-MC-Unique: 4n89mQ5ZPm-NI0_11xXYYg-1 Received: by mail-qv1-f72.google.com with SMTP id h1-20020a0ceda1000000b004b899df67a4so2057909qvr.1 for ; Fri, 21 Oct 2022 03:48:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=SlHxxzR9RIvsWss2F9udcZrQloF9ogWZrtbgSIifbPk=; b=XYNTOrgNMII7znLWarjHYw8Prh6IvGKrLYzKX3Ma1OAF2usP+m3lFg0yIcgT0kt7iU IsBmxy2I1XIj9bxcHQCKd/xzI5FjzLa0VXhSPIk7wsXjop3X+KZ+FgjVuuzixKXofjLX B5Ov2vycMrgH8XX9we+0J2OrKpa+b/+V5fBqduWVkOk3BFgS3Mo0cYNycg5KjWJS/p82 FIrJdPAq7MpcGnrfkQqW9cMxI+pJE69XJ+QAb8aF2JVpqgF/vpQTHuHKeRJIbUqGpJPS ldB/pOAp4JpHsQ4oswACZPe+1IiUZaZQDqK5lO7NBi2IWPsj2Rqj4vO1YAc2tXnHzyO8 B8Nw== X-Gm-Message-State: ACrzQf3DiA9qilfRwaaxJIJL9MxsuiSgf+I01LFnwjHpvteIcjGZS/R8 fp8lNzupFPzPCJa9Odk4O7JQuij/DLUxQ2aVVaswppwQIIAwJz6006Nf4cXJ/Bqp727lv3xhlJa LjbVPtcJC5/UI4QhBN/sKAX6V+ncwM4NImA== X-Received: by 2002:a05:620a:13f2:b0:6ec:597f:eda6 with SMTP id h18-20020a05620a13f200b006ec597feda6mr13393725qkl.287.1666349304094; Fri, 21 Oct 2022 03:48:24 -0700 (PDT) X-Google-Smtp-Source: AMsMyM53VNS3dNJOq/6f+jAFFd+Ux/d43R//UYX/u1UjbEhxNhOgC9ni87be0yZRtJxjSgoM7NPHa7kmJIlligv9Yp8= X-Received: by 2002:a05:620a:13f2:b0:6ec:597f:eda6 with SMTP id h18-20020a05620a13f200b006ec597feda6mr13393707qkl.287.1666349303896; Fri, 21 Oct 2022 03:48:23 -0700 (PDT) MIME-Version: 1.0 References: <0f1f223a-3756-1da3-bd1d-b87edd34e1f9@126.com> <7277b1d9a835d8cc651ab112eac8c2e7@autistici.org> In-Reply-To: <7277b1d9a835d8cc651ab112eac8c2e7@autistici.org> From: Jonathan Wakely Date: Fri, 21 Oct 2022 11:48:13 +0100 Message-ID: Subject: Re: Adding a new thread model to GCC To: i.nixman@autistici.org Cc: LIU Hao , libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org, Eric Botcazou X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Fri, 21 Oct 2022 at 11:10, i.nixman--- via Libstdc++ 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). The benefits of using the native thread model for the OS seems obvious. The question is which patch to do that should we use.