Message ID | CADNgcExW1--6aLQ7KjdU5fYyvnxobht74_ufEw7HqYyra+OO5w@mail.gmail.com |
---|---|
State | New |
Headers | show |
On Thu, Aug 23, 2012 at 10:35 AM, Mingjie Xing <mingjie.xing@gmail.com> wrote: > Hi, > > A very small patch. OK? Ok. Thanks, Richard. > 2012-08-23 Mingjie Xing <mingjie.xing@gmail.com> > > * doc/gty.texi: Fix typo. > > Index: doc/gty.texi > =================================================================== > --- doc/gty.texi (revision 190611) > +++ doc/gty.texi (working copy) > @@ -666,7 +666,7 @@ The GCC build tree is needed to be prese > The GCC garbage collector GGC is only invoked explicitly. In contrast > with many other garbage collectors, it is not implicitly invoked by > allocation routines when a lot of memory has been consumed. So the > -only way to have GGC reclaim storage it to call the @code{ggc_collect} > +only way to have GGC reclaim storage is to call the @code{ggc_collect} > function explicitly. This call is an expensive operation, as it may > have to scan the entire heap. Beware that local variables (on the GCC > call stack) are not followed by such an invocation (as many othe > > Regards, > Mingjie
On Thu, 23 Aug 2012, Mingjie Xing wrote: > A very small patch. OK? > > 2012-08-23 Mingjie Xing <mingjie.xing@gmail.com> > > * doc/gty.texi: Fix typo. By the way, changes of this kind, you can just commit and post the patch; they do not require approval. (When in doubt feel free to ask, of course.) Gerald
Index: doc/gty.texi =================================================================== --- doc/gty.texi (revision 190611) +++ doc/gty.texi (working copy) @@ -666,7 +666,7 @@ The GCC build tree is needed to be prese The GCC garbage collector GGC is only invoked explicitly. In contrast with many other garbage collectors, it is not implicitly invoked by allocation routines when a lot of memory has been consumed. So the -only way to have GGC reclaim storage it to call the @code{ggc_collect} +only way to have GGC reclaim storage is to call the @code{ggc_collect} function explicitly. This call is an expensive operation, as it may have to scan the entire heap. Beware that local variables (on the GCC call stack) are not followed by such an invocation (as many othe