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 2E95A3858C78 for ; Tue, 1 Feb 2022 17:17:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2E95A3858C78 Received: from mail-ot1-f72.google.com (mail-ot1-f72.google.com [209.85.210.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-22-KnvlXyLkNQWxU7sMvlu1rA-1; Tue, 01 Feb 2022 12:17:54 -0500 X-MC-Unique: KnvlXyLkNQWxU7sMvlu1rA-1 Received: by mail-ot1-f72.google.com with SMTP id j2-20020a9d7d82000000b005a12a0fb4b0so9767642otn.5 for ; Tue, 01 Feb 2022 09:17:54 -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=g3uGe44VoHoW2XUBOwzFPmyNfum4jm4nAwtNYiInOCc=; b=DMTM6FLcLHT4d/6wlwjcV2PPEdPB/bTGiJBCIr+PArRVEzTxYviRsnUU0+GPJqBFKZ XqjENTdA3EBq9tV87WxbYSU7xKRqQa7n0MfalWN4trP9BW8gbyzZqLsrqWEDrAfKAWR7 DQYKs3wVnDxZIEy3ZfwNdf6ARHwX7KNWN4WdnDdBMLL0XZoK1rlaF10iqsWPj95BNAEs EYdGzMI5mSA6F8GY4RziZYoiDHqCMDYOOlWIiNf4t5jFUueW97CiQypZ4R5AMUdFHwOh 7RQHZ9YQIjmyhH4r+ss5sjP8DQN7t1RdjgSulDky3KR433bRyW6DBswIpY7iQRumhjm2 8xmw== X-Gm-Message-State: AOAM533A3iiXsJWUF5Cx2Zv9JLBez6fv0Wz0NK4JJgPtGmORgLuTMDKd TeKVfIPrw3M/7ixpaz09etgtEeZEnIkBN+z3ig/CNb3EHMctSJhRLqPDfGYYXGmeepzsIAEUu8+ MtYi1eF+SDUv+a09bXm2D++ayCXeIK6yYOA== X-Received: by 2002:a05:6808:1181:: with SMTP id j1mr1772718oil.182.1643735874246; Tue, 01 Feb 2022 09:17:54 -0800 (PST) X-Google-Smtp-Source: ABdhPJywCdztZRlui+q/yhIl1Z08DTjvPRsCMj4/Xz/XxSV/I4+Q/vnOmElsCce38sVZfGGtji//KhXP9GyAhSdgTi0= X-Received: by 2002:a05:6808:1181:: with SMTP id j1mr1772703oil.182.1643735874019; Tue, 01 Feb 2022 09:17:54 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Thomas Rodgers Date: Tue, 1 Feb 2022 09:17:43 -0800 Message-ID: Subject: Re: [PATCH] Strengthen memory memory order for atomic::wait/notify To: Jonathan Wakely Cc: "libstdc++" , gcc Patches X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com 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, HTML_MESSAGE, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=unavailable 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: Tue, 01 Feb 2022 17:18:00 -0000 Tested x86_64-pc-linux-gnu, committed to master. Backported to GCC-11. On Sun, Jan 16, 2022 at 12:31 PM Jonathan Wakely wrote: > > > 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. >> >