Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>
Newsgroups: comp.lang.c++
Subject: Re: P1202 (asymmetric memory barriers) going into C++26
Date: Tue, 24 Jun 2025 13:12:23 -0700
Organization: A noiseless patient Spider
Lines: 10
Message-ID: <103f0r7$27r68$1@dont-email.me>
References: <1031r7q$3l8f$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 24 Jun 2025 22:12:23 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="b650f5ce277f3eafe7126216cc4b3f0a";
	logging-data="2354376"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+5dDh/LMde9Uq0SaWUqMLVyMrH2TRiVOw="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:Ev0HWxM4He+ah4Tajbg1mYmy76s=
Content-Language: en-US
In-Reply-To: <1031r7q$3l8f$1@dont-email.me>

On 6/19/2025 1:16 PM, jseigh wrote:
> They're used by hazard pointers and RCU both of which are going in.
> Only 20 years from POC to a C++ standard.  Time flies.
> 

:^) Nice.

Now what about data-dependent load barriers, ala consume? Well, a 
consume that falls back to an acquire is a no go right off the bat 
unless its on an Alpha?