From d3129ab8e744b69ae38ec7fe347a80ad62e078a3 Mon Sep 17 00:00:00 2001 From: Bruce Mitchener Date: Fri, 9 Dec 2011 11:23:00 +0700 Subject: [PATCH] Fix some typos. --- doc/README.win32 | 2 +- doc/gcdescr.html | 4 ++-- doc/gcinterface.html | 2 +- doc/scale.html | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/README.win32 b/doc/README.win32 index 4131529d..3ffb3b6f 100644 --- a/doc/README.win32 +++ b/doc/README.win32 @@ -153,7 +153,7 @@ http://bugzilla.openwatcom.org/show_bug.cgi?id=664), so You are warned. Incremental Collection ---------------------- There is some support for incremental collection. By default, the -collector chooses between explicit page protection, anf GetWriteWatch-based +collector chooses between explicit page protection, and GetWriteWatch-based write tracking automatically, depending on the platform. The former is slow and interacts poorly with a debugger. diff --git a/doc/gcdescr.html b/doc/gcdescr.html index 68448e61..be83c1d1 100644 --- a/doc/gcdescr.html +++ b/doc/gcdescr.html @@ -558,7 +558,7 @@ accomplished with # define's in gc.h (really gc_pthread_redirects.h), or optionally by using ld's function call wrapping mechanism under Linux.

-Recent versions of the collector support several facilites to enhance +Recent versions of the collector support several facilities to enhance the processor-scalability and thread performance of the collector. These are discussed in more detail here. We briefly outline the data approach to thread-local allocation in the @@ -572,7 +572,7 @@ The free list arrays associated with each thread are only used to satisfy requests for objects that are both very small, and belong to one of a small number of well-known kinds. These currently include "normal" and pointer-free objects. -Depending onthe configuration, "gcj" objects may also be included. +Depending on the configuration, "gcj" objects may also be included.

Thread-local free list entries contain either a pointer to the first element of a free list, or they contain a counter of the number of diff --git a/doc/gcinterface.html b/doc/gcinterface.html index c78f6a9e..ea6dfc5e 100644 --- a/doc/gcinterface.html +++ b/doc/gcinterface.html @@ -133,7 +133,7 @@ that write to the garbage collected heap.

Replace the default procedure used by the collector to print warnings. The collector -may otherwise write to sterr, most commonly because GC_malloc was used +may otherwise write to stderr, most commonly because GC_malloc was used in a situation in which GC_malloc_ignore_off_page would have been more appropriate. See gc.h for details.
void GC_REGISTER_FINALIZER(...) diff --git a/doc/scale.html b/doc/scale.html index 3d976ea4..b9de2e40 100644 --- a/doc/scale.html +++ b/doc/scale.html @@ -158,7 +158,7 @@ the client using either one or two marker threads, and running one or two client threads. Note that the client uses thread local allocation exclusively. With -DTHREAD_LOCAL_ALLOC the collector switches to a locking strategy that is better tuned to less frequent -lock acquisition. The standard allocation primitives thus peform +lock acquisition. The standard allocation primitives thus perform slightly worse than without -DTHREAD_LOCAL_ALLOC, and should be avoided in time-critical code.

-- 2.40.0