From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) by sourceware.org (Postfix) with ESMTPS id EE4F13858D37 for ; Wed, 27 Dec 2023 19:27:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org EE4F13858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org EE4F13858D37 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2a00:1450:4864:20::12d ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703705248; cv=none; b=igALtjsDfAKlZKmg4TP/1zzsVRIRPNrGMFf5pM2va5N+XewwcKxZ/F2AfsCFaQ5QEz0JLZfS4oZrb6qBGU1G0mQgjZBNUJ5hqtiud7MPjH/um3wrNKKAWqFUlMbY7lDHTNvVHCJEjnTk47MPhubUpXmgpPjiHvxF3IyZ3eMrDjw= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1703705248; c=relaxed/simple; bh=nbrHGRFz8D/uDBLzOhAli3EQd0Hbej+/p93SNlSE6/8=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=IU64V7z2DsdgzESyNGhrsRvxLRp+GNxGnLXpOhaTm2bMCiXFD4VVKfD2ZrE0nco5sDW2ZqM2rFVdrPllo8YRIty1hIF8wIU2Vaux9Jkglof8KBlScOwoHwYWWKfBGx9BPkGDHc47lVVqCHWJJmaceO7kA4vFzqha9fUUu6p3ZRU= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-lf1-x12d.google.com with SMTP id 2adb3069b0e04-50e67e37661so5016528e87.0 for ; Wed, 27 Dec 2023 11:27:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703705245; x=1704310045; darn=gcc.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nbrHGRFz8D/uDBLzOhAli3EQd0Hbej+/p93SNlSE6/8=; b=eGCZTRsDTm7Gk5aHtqeP7pgHe5+JL9KXVrUf7QUd8LZyz4LOlsciT+hZquPR/lEWDX iqPRBLgYAXJ1luF7UYSQ8AFsO3YtjPeEOq9cCzmC4Zsr9eDW2pBfVw6nf+gSFtoGEzuc Rk9JyNMCb6lBxtps3GsqTdxyLDSR4+xZbLLDlJulO+KSG3MV4X4XzCJXm0bvZvVieuFF X2HH1Ayb6RSO2UhUkkxESBT5K8RojEd81ntRcj7jHEL6fcJtxMnePPCkgkZZPFOVhv6C 4nCvgO8UoDSv+os9aad/UNvRW+SJRkPCM8bcVN54nLWp2DBRtO4JPD/NQSZCYhLmQGxy dHgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703705245; x=1704310045; 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=nbrHGRFz8D/uDBLzOhAli3EQd0Hbej+/p93SNlSE6/8=; b=hx69KyAqlBVnqVboStCMM7fdvwbOnBLDc8RVm+PexqAaBQ7TcHE0dvO0+gThMOJhEK Frgj/iec0L1UyXIxAlDCpPgJEaKRmu4PHwNDC+bRxgIOTqbCH2KbiOJbtdjVvhrEet9P GCYAOP6HDTp1NjNksN24GtkY9TSrmUqsZab9ngVlDxrj2Aqw5PSw0PMPNDhZSvxSRuAI qhDLkilRK+uR5HYs2IsdlIrKDdEt1xwhwHg82FwQVNoITxaTD+2wuvYvjhNTxZZRsuXa 4If0STKoX5ZuB4vwY+JXCnnFy+j7jrqWXi/rrgE3E7tPyxn4yx2GbKs++T8Mo+XYh9vb 3Gig== X-Gm-Message-State: AOJu0YwKTcttClFVKJU/Lpwue9P4CEJXhW9Okur0vJNGqrpF2aj2CwJA kNBHv/+yi9LWGvCF5rkDO5vwOPoQOloW5NOa8bc= X-Google-Smtp-Source: AGHT+IHigAq9NFhPwT7FruZst32FZozC3uyEotdJsNqlRzMxJHaEKv9yDxhhnNeWWvnjf+E+y7epIw5F7ln/V0Vd5YY= X-Received: by 2002:a05:6512:31ca:b0:50e:7e52:1739 with SMTP id j10-20020a05651231ca00b0050e7e521739mr2303924lfe.17.1703705245001; Wed, 27 Dec 2023 11:27:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Wed, 27 Dec 2023 19:27:13 +0000 Message-ID: Subject: Re: std::launch::async implementation To: Taras Sich Cc: gcc-help Content-Type: multipart/alternative; boundary="000000000000ee29d8060d82c919" X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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: --000000000000ee29d8060d82c919 Content-Type: text/plain; charset="UTF-8" On Wed, 27 Dec 2023, 11:33 Taras Sich via Gcc-help, wrote: > Dear GCC team, > > Could you please clarify whether the implementation of std::launch::async > uses a thread pool? > It does not, because that's not conforming. The standard says the function has to be run in a new thread, not a reused one. The difference is observable by using thread-specific variables. I'm particularly interested in the implementation for Fedora 33. > Have not found the behavior description in the documentation. > > Best regards, > Taras > --000000000000ee29d8060d82c919--