Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!bbn!uwmcsd1!ig!agate!ucbvax!decwrl!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!urbsdc!aglew
From: aglew@urbsdc.Urbana.Gould.COM
Newsgroups: comp.arch
Subject: Re: volatile (in comp.lang.c)
Message-ID: <28200144@urbsdc>
Date: 12 May 88 14:55:00 GMT
References: <1030@micomvax.UUCP>
Lines: 10
Nf-ID: #R:micomvax.UUCP:1030:urbsdc:28200144:000:444
Nf-From: urbsdc.Urbana.Gould.COM!aglew    May 12 09:55:00 1988


>I have never seen any suggestion that a program containing
>"volatile" would be portable except perhaps to other processors which happen
>to have similar memory, I/O, and hardware architectures.
>
>John R. Levine, IECC, PO Box 349, Cambridge MA 02238-0349, +1 617 492 3869

Then I suppose that I'd better tell my friend who is writing
a massive astronomical simulation using System V shared memory
in as portable a way as possible to give up?