path: root/doc
diff options
authorBruce Mitchener <>2011-11-23 07:59:04 +0100
committerIvan Maidanski <>2011-11-23 12:30:42 +0100
commitc7da478bb25c17e4da0cea583c95c1f2175de21d (patch)
tree7b116cab1b41fda701371b7a1fccb9b1804ca151 /doc
parenta7d295afa96029f89698c69f7ff4bead19e03b91 (diff)
Typo fixes in README, doc/README.cmake, doc/README.darwin
(Apply commit 72f0c9f)
Diffstat (limited to 'doc')
3 files changed, 9 insertions, 9 deletions
diff --git a/doc/README b/doc/README
index 8ca035b..bf2ea50 100644
--- a/doc/README
+++ b/doc/README
@@ -33,7 +33,7 @@ at the notice in config.guess or
The atomic_ops library contains some code that is covered by the GNU General
Public License, but is not needed by, nor linked into the collector library.
-It is included here only becuase the atomic_ops distribution is, for
+It is included here only because the atomic_ops distribution is, for
simplicity, included in its entirety.
This is version 7.2alpha7 of a conservative garbage collector for C and C++.
@@ -100,7 +100,7 @@ collector. (See doc/README.cords and H.-J. Boehm, R. Atkinson, and M. Plass,
(December 1995), pp. 1315-1330. This is very similar to the "rope" package
in Xerox Cedar, or the "rope" package in the SGI STL or the g++ distribution.)
-Further collector documantation can be found at
+Further collector documentation can be found at
@@ -138,7 +138,7 @@ There are a number of routines which modify the pointer recognition
algorithm. GC_register_displacement allows certain interior pointers
to be recognized even if ALL_INTERIOR_POINTERS is nor defined.
GC_malloc_ignore_off_page allows some pointers into the middle of large objects
-to be disregarded, greatly reducing the probablility of accidental
+to be disregarded, greatly reducing the probability of accidental
retention of large objects. For most purposes it seems best to compile
with ALL_INTERIOR_POINTERS and to use GC_malloc_ignore_off_page if
you get collector warnings from allocations of very large objects.
@@ -334,7 +334,7 @@ good way for the collector to compute this value.) Client code may include
6) GC_malloc_ignore_off_page(bytes)
- identical to GC_malloc, but the client promises to keep a pointer to
the somewhere within the first 256 bytes of the object while it is
- live. (This pointer should nortmally be declared volatile to prevent
+ live. (This pointer should normally be declared volatile to prevent
interference from compiler optimizations.) This is the recommended
way to allocate anything that is likely to be larger than 100Kbytes
or so. (GC_malloc may result in failure to reclaim such objects.)
@@ -398,7 +398,7 @@ proposal without compiler changes.
Very often it will also be necessary to use gc_allocator.h and the
allocator declared there to construct STL data structures. Otherwise
-subobjects of STL data structures wil be allcoated using a system
+subobjects of STL data structures will be allocated using a system
allocator, and objects they refer to may be prematurely collected.
@@ -414,7 +414,7 @@ also be automatically reclaimed.
the default version of report_leak will report at least the source file and
line number at which the leaked object was allocated. This may sometimes be
sufficient. (On a few machines, it will also report a cryptic stack trace.
-If this is not symbolic, it can somethimes be called into a sympolic stack
+If this is not symbolic, it can sometimes be called into a sympolic stack
trace by invoking program "foo" with "callprocs foo". Callprocs is a short
shell script that invokes adb to expand program counter values to symbolic
addresses. It was largely supplied by Scott Schwartz.)
@@ -452,7 +452,7 @@ the debugger.
or GC_free, and conversely. It is however acceptable to allocate only
some objects with GC_debug_malloc, and to use GC_malloc for other objects,
provided the two pools are kept distinct. In this case, there is a very
-low probablility that GC_malloc allocated objects may be misidentified as
+low probability that GC_malloc allocated objects may be misidentified as
having been overwritten. This should happen with probability at most
one in 2**32. This probability is zero if GC_debug_malloc is never called.
diff --git a/doc/README.cmake b/doc/README.cmake
index 4f78b61..3eb347c 100644
--- a/doc/README.cmake
+++ b/doc/README.cmake
@@ -34,7 +34,7 @@ BUILD PROCESS
. run cmake from the gc root directory, passing the target with -G:
> cmake -G "Visual Studio 8 2005"
- use the gc.sln file genereated by cmake to build gc
+ use the gc.sln file generated by cmake to build gc
. you can also run cmake from a build directory to build outside of
the source tree. Just specify the path to the source tree:
diff --git a/doc/README.darwin b/doc/README.darwin
index ca4be89..a38178a 100644
--- a/doc/README.darwin
+++ b/doc/README.darwin
@@ -79,7 +79,7 @@ programs that use JNI. If you run code that does not follow the stack
layout or stack pointer conventions laid out in the PPC Mach-O ABI,
then this will likely crash the garbage collector.
-The original incremental collector support unfortunatelly no longer works
+The original incremental collector support unfortunately no longer works
on recent Darwin versions. It also relied on some undocumented kernel
structures. Mach, however, does have a very clean interface to exception
handing. The current implementation uses Mach's exception handling.