From: Mikko Levanto <mikko.levanto@iki.fi>
Subject: Re: Handling Addressing Errors
Date: 1999/03/19
Date: 1999-03-19T00:00:00+00:00 [thread overview]
Message-ID: <36F21863.7D71@iki.fi> (raw)
In-Reply-To: 36F17DAC.E80F01DD@averstar.com
Tucker Taft wrote:
> This is made explicit in RM95 C.6(20) and 1.1.3(13), which indicates
> that the "external effect" of a program includes *each*
> read and update of a volatile or atomic object.
> It is illegal to optimize away an external effect (RM95 1.1.3(15)).
Can optimization affect the number of accesses ?
E.g., if A is volatile, does
A := A + A;
always cause two reads and one write?
--
Mikko J. Levanto
mailto:mikko.levanto@vtt.fi
next prev parent reply other threads:[~1999-03-19 0:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-03 0:00 Handling Addressing Errors Charles H. Sampson
1999-03-04 0:00 ` Nick Roberts
1999-03-04 0:00 ` robert_dewar
1999-03-18 0:00 ` Charles H. Sampson
1999-03-18 0:00 ` Nick Roberts
1999-03-21 0:00 ` robert_dewar
1999-03-18 0:00 ` Tucker Taft
1999-03-19 0:00 ` Mikko Levanto [this message]
1999-03-19 0:00 ` Nick Roberts
1999-03-20 0:00 ` Tucker Taft
1999-04-02 0:00 ` Charles H. Sampson
1999-03-19 0:00 ` robert_dewar
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox