OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* extend.texi (Volatiles): Fix typos. 

From-SVN: r35632
This commit is contained in:
Nathan Sidwell 2000-08-11 13:42:32 +00:00 committed by Nathan Sidwell
parent c9bacfdb84
commit 8117da65db
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gcc/ChangeLog
View File

@ -1,3 +1,7 @@
2000-08-11 Nathan Sidwell <nathan@codesourcery.com>
* extend.texi (Volatiles): Fix typos.
2000-08-11 Kazu Hirata <kazu@hxi.com>
* flow.c: Fix formatting.

4
gcc/extend.texi
View File

@ -3558,13 +3558,13 @@ works correctly.
Both the C and C++ standard have the concept of volatile objects. These
are normally accessed by pointers and used for accessing hardware. The
standards encourage compilers to refrain from optimizations on
standards encourage compilers to refrain from optimizations
concerning accesses to volatile objects that it might perform on
non-volatile objects. The C standard leaves it implementation defined
as to what constitutes a volatile access. The C++ standard omits to
specify this, except to say that C++ should behave in a similar manner
to C with respect to volatiles, where possible. The minimum either
standard specifies is that at a sequence point all previous access to
standard specifies is that at a sequence point all previous accesses to
volatile objects have stabilized and no subsequent accesses have
occurred. Thus an implementation is free to reorder and combine
volatile accesses which occur between sequence points, but cannot do so