Xref: utzoo comp.lang.c:9839 comp.arch:4566
Path: utzoo!utgpu!water!watmath!clyde!skep2!wcs
From: wcs@skep2.ATT.COM (Bill.Stewart.<ho95c>)
Newsgroups: comp.lang.c,comp.arch
Subject: Re: volatile (in comp.lang.c)
Message-ID: <96@skep2.ATT.COM>
Date: 2 May 88 04:12:17 GMT
References: <20345@pyramid.pyramid.com> <833@mcdsun.UUCP> <9916@tekecs.TEK.COM> <2642@geac.UUCP> <2082@winchester.mips.COM> <2674@geac.UUCP> <51437@sun.uucp>
Reply-To: wcs@skep2.UUCP (46323-Bill.Stewart.<ho95c>,2G218,x0705,)
Organization: AT&T Bell Labs Center 4632, Holmdel, NJ
Lines: 16

In article <51437@sun.uucp> limes@sun.UUCP (Greg Limes) writes:
:In article <2674@geac.UUCP> daveb@geac.UUCP (David Collier-Brown) writes:
:>	1) what architectures currently use asynchronously-changing
:>memory locations for program notification of events? DEC Vax,
:>various CDC boxes, MIPS(tm),...
:... and any program with a signal handler that modifies a global
:variable, which is pretty inclusive if you ask me, .....

	Any program with a signal handler that *reads* global variables
needs the moral equivalent of volatile, if you're going to allow
optimizing compilers to avoid "redundant" writes to memory.
-- 
#				Thanks;
# Bill Stewart, AT&T Bell Labs 2G218, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs
# skep2 is a local machine I'm trying to turn into a server.  Please send
# mail to ho95c or ho95e instead.  Thanks.