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.129.124]) by sourceware.org (Postfix) with ESMTPS id D85BD3853547 for ; Fri, 21 Oct 2022 10:48:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D85BD3853547 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=1666349305; 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=ALEdWlyQxlmw6TGqz6MFHfHQXDTeltFxIUy9gOKUWbtg08RUHsDaTf/urCJtBnuMWWye2T JA70YoFCypVsTlBOywnB2T67Q0WO1XueGfttJe0AHUQjnsO5/I3M3oDmoGpd15OVXSkLaO dUqjDjq/If1PjyQSWRCX5qa5bUewYx0= Received: from mail-qt1-f197.google.com (mail-qt1-f197.google.com [209.85.160.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-499-yX8pmDIyNGONMHURf-oDtA-1; Fri, 21 Oct 2022 06:48:24 -0400 X-MC-Unique: yX8pmDIyNGONMHURf-oDtA-1 Received: by mail-qt1-f197.google.com with SMTP id ff6-20020a05622a4d8600b0039cbf66e8b5so2188442qtb.19 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=T9obh9ReTb/rmvFBUbPjFBY8Qa9duFHdPZs+hR6Dtv616Op/pZHCnbGGVQlwvkxFrG WVKcGJrvYB5cezGNYswhnPmWBsuCSqnONaB22Mmh2vpTcDOVQ4WrY8X+LxoETo26+R3W hnKwMYhncpLICM8J9LV4NeJ/ciC7W1vOrHamGaihlKs2Farcnns49/fZO5LB/OSeMuJQ o/oksxaNnY9w5zCjzHKML7V/MaCOuXgkYdgyNbz7SGxmFUT4NJAOjIYuwFsLPJax/HqG SJ9TH6WYPxqY9sOMxYlTXedYDqlXYnbKQsLoJ0LmxokCuT6tH0yfE6Fgm/N4mc9Yu6u0 pEaw== X-Gm-Message-State: ACrzQf0oFqKOmQsP9Tkr4q2Fd06/gNoWAbkgaRHnrpNUw3DlCvTYlmAf aKcAO6Qu6InCvL0W8yJ7vuM7fFnYYZzOUsaHL2+nG+cxrf0hAl/YEEQcBVBSh4k94MYvC4pgn59 oZldsuKhk49xlcn5K3Odeu8pBVAmsOUs= X-Received: by 2002:a05:620a:13f2:b0:6ec:597f:eda6 with SMTP id h18-20020a05620a13f200b006ec597feda6mr13393721qkl.287.1666349304070; 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.5 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=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: 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.