[Info-vax] LLVM, volatile and async VMS I/O and system calls
    Simon Clubley 
    clubley at remove_me.eisner.decus.org-Earth.UFP
       
    Fri Sep 24 23:42:36 EDT 2021
    
    
  
On 2021-09-24, chris <chris-nospam at tridac.net> wrote:
> On 09/24/21 19:36, Simon Clubley wrote:
>> You therefore have to force a re-read of the buffer when you later go
>> looking at it so the compiler doesn't think it can reuse an existing
>> (and now stale) value.
>
> All i'm saying is, read the C standard docs on the use of the volatile 
> keyword for more info, or do you think you know better ?...
>
How do you otherwise _guarantee_ that the Linux application program
is seeing the latest data that the Linux kernel might have written
into the buffer behind the scenes since the program last looked at
the buffer ?
Simon.
-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.
    
    
More information about the Info-vax
mailing list