Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Dereferencing Typecast Integer Literals
Message-ID: <15157@smoke.brl.mil>
Date: 11 Feb 91 08:26:07 GMT
References: <22700@netcom.UUCP> <15067@smoke.brl.mil> <2309@tuvie.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 7

In article <2309@tuvie.UUCP> hp@vmars.tuwien.ac.at (Peter Holzer) writes:
>We solved the problem by declaring value volatile, which is extremely
>non-obvious and misleading, but does its job.

In fact that's a good use for "volatile".  It forces the compiler to
try to use the variable in the generated code in a one-to-one
correspondence with the explicit accesses in the C source code.