> > This is the precise optimization that 'volatile' inhibits. 'volatile' > > requires that the value not be cached in "cheap-to-access" locations > > like registers, instead being re-loaded from "expensive-to-access" > > locations like the original memory -- because it may be changed from > > outside the control flow that the compiler knows about. > > Agreed with the sorts of things volatile inhibits.
You are both wrong. The C standard is *silent* on the concept of underlying hardware. It only talks about the flow of control as defined in the module being translated. It created a new term, sequence point, to talk about control flow in an abstract way. The ISO C web site seems to be: http://www.open-std.org/jtc1/sc22/wg14/ and if you go there you can find copies of the standard and the committee mailings, e.g. /r$ -- STSM Senior Security Architect DataPower SOA Appliances ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
