From fb489f55b58e5725bf04fbd26181c3c196fb5f32 Mon Sep 17 00:00:00 2001 From: Mingjie Xing Date: Thu, 23 Aug 2012 09:30:24 +0000 Subject: [PATCH] Fix typo in gty.texi. From-SVN: r190617 --- gcc/ChangeLog | 4 ++++ gcc/doc/gty.texi | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index ef1b5ca3dac..214b40e7abf 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2012-08-23 Mingjie Xing + + * doc/gty.texi: Fix typo. + 2012-08-23 Richard Guenther * tree-ssa-loop-manip.c (add_exit_phis_var): Allow virtual operands. diff --git a/gcc/doc/gty.texi b/gcc/doc/gty.texi index cc46a61e4ea..b2214b8053b 100644 --- a/gcc/doc/gty.texi +++ b/gcc/doc/gty.texi @@ -666,7 +666,7 @@ The GCC build tree is needed to be present in that mode. 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 other -- 2.30.2