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 BBF8C3858402 for ; Sun, 16 Jan 2022 20:31:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org BBF8C3858402 Received: from mail-yb1-f200.google.com (mail-yb1-f200.google.com [209.85.219.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-258-FgbU8rx0O660OV_bMerqSw-1; Sun, 16 Jan 2022 15:31:04 -0500 X-MC-Unique: FgbU8rx0O660OV_bMerqSw-1 Received: by mail-yb1-f200.google.com with SMTP id x74-20020a25e04d000000b006120ffdd59cso6134500ybg.15 for ; Sun, 16 Jan 2022 12:31:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4Hqavq870vVvwd5WaZ9rkeRkLZwztA8N08dZXUxUONg=; b=sC5vV21I4I2E46eAGWFht1LlNW2DHdeo3Kzb0rsHbFXVIou4wycZjJmObdqsxhNFic HaOaA8HgHio0WjfimTcDPnkEOQsIM6TO7wcEyqEtn4IwDKRTPJB7VZwiY6nhn59hEbL3 KnkU4VqJK755xVh5Yq/Q39jUSG2sx4sTpohUr89LDqCphpUfL3c3FUQbSLx1khJB0LC+ aIKP4Vv49yiYeYtsYGpeWvgOw7HOwfDwcJ5FBDzA8R87bMObxQkFw3TFhJ27fFv3ArhG C68QNFyHROXv/W1fK7y3reA0BC2s132BrWKe3jaRK3J8R3hl8U2K2BXYolGo4BwCw4nd /C7g== X-Gm-Message-State: AOAM531nBoDgQNeTmIp6qKBbpUAZnKEzQ2zgEx8UfbFFYOD1qcKFEfRs RgCCC1v8KAuvgyCDzQQZG07+1BCRQo1V/cCNa4n33KABv/+8cEWTtLGxhHEnV9Ec6MDHVbQ4ufb FDc0SfVzvdJRt7/LYIgf+ChklcKt+AjbVfw== X-Received: by 2002:a25:4dd4:: with SMTP id a203mr26594639ybb.580.1642365063470; Sun, 16 Jan 2022 12:31:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJxMZt3rvRzgFt/g4Nx49cceIJrhcm7UHa4XUN7b0HX0wD50w0MNRH2jvu4H4VLCmkfNTEhY7GHuQM8EKuvLffg= X-Received: by 2002:a25:4dd4:: with SMTP id a203mr26594622ybb.580.1642365063220; Sun, 16 Jan 2022 12:31:03 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Sun, 16 Jan 2022 20:30:52 +0000 Message-ID: Subject: Re: [PATCH] Strengthen memory memory order for atomic::wait/notify To: Thomas Rodgers Cc: "libstdc++" , gcc Patches X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com X-Spam-Status: No, score=-7.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, HTML_MESSAGE, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2022 20:31:06 -0000 On Sun, 16 Jan 2022 at 01:48, Thomas Rodgers via Libstdc++ < libstdc++@gcc.gnu.org> wrote: > This patch updates the memory order of atomic accesses to the waiter's > count to match libc++'s usage. It should be backported to GCC11. > The commit subject line says "memory memory order", OK for trunk and gcc-11 with that fixed. > Tested x86_64-pc-linux-gnu. >