Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!homxb!mtuxo!mtune!codas!usfvax2!chips
From: chips@usfvax2.UUCP
Newsgroups: comp.arch
Subject: Re: H/W Write Buffers, S/W Synchronization (long reply)
Message-ID: <915@usfvax2.UUCP>
Date: Fri, 30-Oct-87 22:13:10 EST
Article-I.D.: usfvax2.915
Posted: Fri Oct 30 22:13:10 1987
Date-Received: Sun, 1-Nov-87 09:29:32 EST
References: <2280002@hpsal2.HP.COM> <845@winchester.UUCP> <849@mips.UUCP>
Organization: AT Engineering, Tampa, FL
Lines: 12
Summary: volatile

In article <849@mips.UUCP>, hansen@mips.UUCP (Craig Hansen) writes:
} What would be useful for this sort of hardware/software environment is an
} indication, not of whether a variable is "shared," because all variables
} essentially are shared or sharable, but whether such a variable requires
} implicit synchronization, associated with reads and writes of the variable.

As, for example, the C keyword "volatile"...

-- 
Chip Salzenberg            "chip%ateng.uucp@UU.NET"  or  "uunet!ateng!chip"
A.T. Engineering, Tampa    CIS: 73717,366    Last Chance: "chips@usfvax2.UUCP"
"Use the Source, Luke!"    My opinions do not necessarily agree with anything.