[Info-vax] LLVM, volatile and async VMS I/O and system calls

Simon Clubley clubley at remove_me.eisner.decus.org-Earth.UFP
Wed Sep 22 08:28:08 EDT 2021


Jan-Erik's questions about ASTs in COBOL have reminded me about something
I asked a while back.

VMS I/O and system calls are much more asynchronous than on other operating
systems and data can appear in buffers and variables in general can be
changed outside of the normal sequence points (such as at a function call
boundary).

With the move to LLVM, and its different optimiser, have any examples
appeared in VMS code for x86-64 where volatile attributes are now required
on variable definitions where you would have got away with not using them
before (even if technically, they should have been marked as volatile anyway) ?

Just curious if there's any places in code running on VMS x86-64 that will
need to cleaned up to do things in the correct way that you would have
got away with doing less correctly previously.

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