Re: [PATCH] C undefined behavior fix

'jtv'
2002-01-08T11:45:33Z

On Tue, Jan 08, 2002 at 10:44:59AM +0100, Bernard Dautrevaux wrote:
>
> NO; the standard here is clear: any access to a volatile object is a side
> effect (see , and optimization is NOT allowed to eliminate side effects, and
> must do them respecting sequence points, even if it determines that the code
> will in fact do nothing

Thank you. That makes it absolutely clear.

Jeroen