Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Terje Mathisen <terje.mathisen@tmsw.no>
Newsgroups: comp.arch
Subject: Re: Memory ordering
Date: Fri, 6 Dec 2024 10:04:29 +0100
Organization: A noiseless patient Spider
Lines: 36
Message-ID: <viuemt$2895m$1@dont-email.me>
References: <vfono1$14l9r$1@dont-email.me>
 <5yqdnU9eL_Y_GKv6nZ2dnZfqn_GdnZ2d@supernews.com>
 <2024Nov15.082512@mips.complang.tuwien.ac.at> <vh7ak1$3cm56$1@dont-email.me>
 <20241115152459.00004c86@yahoo.com> <vh8bn7$3j6ql$1@dont-email.me>
 <vhb2dc$73fe$1@dont-email.me> <vhct2q$lk1b$2@dont-email.me>
 <2024Nov17.161752@mips.complang.tuwien.ac.at> <vhh16e$1lp5h$1@dont-email.me>
 <2024Dec3.100144@mips.complang.tuwien.ac.at> <vin2rp$3ofc$1@dont-email.me>
 <3aa9f0a3d3dde86193abb1c01e52d03a@www.novabbs.org>
 <pz%3P.63771$vLg2.34039@fx17.iad> <86wmgejgxv.fsf@linuxsc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 06 Dec 2024 10:04:30 +0100 (CET)
Injection-Info: dont-email.me; posting-host="1824b994ab75921366915dc699111755";
	logging-data="2368694"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+rYlT+Qkn+bTHDbLOUG5qGxlcBnhMVeikDjq6H4Mn1yQ=="
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.19
Cancel-Lock: sha1:GlcZXA2IN/SDB3z5jJkqBAbg5SY=
In-Reply-To: <86wmgejgxv.fsf@linuxsc.com>
Bytes: 2753

Tim, did you send me a PM to check my email? I responded but then 
silence. Could someone be pretending to be you?

Terje

Tim Rentsch wrote:
> scott@slp53.sl.home (Scott Lurndal) writes:
> 
>> mitchalsup@aol.com (MitchAlsup1) writes:
>>
>>> On Tue, 3 Dec 2024 13:59:18 +0000, jseigh wrote:
>>>
>>>> The compiler is allow to reorder code as long as it knows the
>>>> reordering can't be observed or detected.
>>>
>>> With exceptions enabled, this would allow for almost no code
>>> movement at all.
>>>
>>>>                                            If there are places
>>>> in the code it doesn't know this can't happen it won't optimize
>>>> across it, more or less.
>>>
>>> The problem is HOW to TELL the COMPILER that these memory references
>>> are "more special" than normal--when languages give few mechanisms.
>>
>> C and C++ have the 'volatile' keyword for this purpose.
> 
> A problem with using volatile is that volatile doesn't do what
> most people think it does, especially with respect to what
> reordering is or is not allowed.
> 


-- 
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"