Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>
Newsgroups: comp.arch
Subject: Re: Memory ordering
Date: Fri, 15 Nov 2024 12:48:46 -0800
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <vh8c3f$3j6ql$2@dont-email.me>
References: <vfono1$14l9r$1@dont-email.me> <vgm4vj$3d2as$1@dont-email.me>
 <vgm5cb$3d2as$3@dont-email.me> <YfxXO.384093$EEm7.56154@fx16.iad>
 <vh4530$2mar5$1@dont-email.me>
 <-rKdnTO4LdoWXKj6nZ2dnZfqnPWdnZ2d@supernews.com>
 <vh5t5b$312cl$2@dont-email.me>
 <5yqdnU9eL_Y_GKv6nZ2dnZfqn_GdnZ2d@supernews.com>
 <2024Nov15.082512@mips.complang.tuwien.ac.at> <vh7rlr$3fu9i$1@dont-email.me>
 <2024Nov15.182737@mips.complang.tuwien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 15 Nov 2024 21:48:52 +0100 (CET)
Injection-Info: dont-email.me; posting-host="f78e91c2ef29d1e51cbaba76277412a0";
	logging-data="3775317"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18VJxAXbHD65eFfNPt1q0gATL4tWUdcoOY="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:XzQsYjiO6MJ0gRQe7yyGIHHf46M=
Content-Language: en-US
In-Reply-To: <2024Nov15.182737@mips.complang.tuwien.ac.at>
Bytes: 2121

On 11/15/2024 9:27 AM, Anton Ertl wrote:
> jseigh <jseigh_es00@xemaps.com> writes:
>> Anybody doing that sort of programming, i.e. lock-free or distributed
>> algorithms, who can't handle weakly consistent memory models, shouldn't
>> be doing that sort of programming in the first place.
> 
> Do you have any argument that supports this claim.

Well, if one can't handle the memory barriers, say wrt 
std::memory_order_* ala C++ . well. that is a problem wrt creating these 
"exotic" types of algorithms. Imvvho, that is.


>> Strongly consistent memory won't help incompetence.
> 
> Strong words to hide lack of arguments?

For instance, a 100% sequential memory order won't help you with, say, 
solving ABA.