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: Sun, 17 Nov 2024 15:34:08 -0800
Organization: A noiseless patient Spider
Lines: 34
Message-ID: <vhduhg$sga5$1@dont-email.me>
References: <vfono1$14l9r$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> <vh8c3f$3j6ql$2@dont-email.me>
 <2024Nov16.083744@mips.complang.tuwien.ac.at> <vhb587$6hbv$7@dont-email.me>
 <2024Nov17.161508@mips.complang.tuwien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 18 Nov 2024 00:34:08 +0100 (CET)
Injection-Info: dont-email.me; posting-host="89130e7bcd97b4a24063f6426d51eb57";
	logging-data="934213"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Q7K0We5ZJgXJXDeCzZsyxe1pVANJF1ys="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:r4b3XhOxhH5sNkK6C8uNsjxt1Og=
In-Reply-To: <2024Nov17.161508@mips.complang.tuwien.ac.at>
Content-Language: en-US
Bytes: 3086

On 11/17/2024 7:15 AM, Anton Ertl wrote:
> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:
>> On 11/15/2024 11:37 PM, Anton Ertl wrote:
>>> "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:
>>>> 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.
>>>>>>
>>>>>> 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.
>>>
>>> Sure, not all problems are solved by sequential consistency, and yes,
>>> it won't solve race conditions like the ABA problem.  But jseigh
>>> implied that finding it easier to write correct and efficient code for
>>> sequential consistency than for a weakly-consistent memory model
>>> (e.g., Alphas memory model) is incompetent.
>>
>> What if you had to write code for a weakly ordered system, and the
>> performance guidelines said to only use a membar when you absolutely
>> have to. If you say something akin to "I do everything using
>> std::memory_order_seq_cst", well, that is a violation right off the bat.
>>
>> Fair enough?
> 
> Are you trying to support my point?

I am trying to say you might not be hired if you only knew how to handle 
std::memory_order_seq_cst wrt C++... ?