From patchwork Thu Aug 23 08:35:22 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Mingjie Xing X-Patchwork-Id: 179565 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id DB1A22C0094 for ; Thu, 23 Aug 2012 18:36:05 +1000 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1346315766; h=Comment: DomainKey-Signature:Received:Received:Received:Received: MIME-Version:Received:Received:Date:Message-ID:Subject:From:To: Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:Sender:Delivered-To; bh=01TlNra FH4476yskdT4oJh4YqY0=; b=iR3Yq5twBQbhIPyYV4asdV4r2RzELb7sHpPPKmS yTsE18FyjPQmOLZttMEC7thDhnQElQC68OFBIYcVgDpjftJWGlVheEr/3kw8fgrw kXqHQgWMVrwzIPCCEQFwLUAQUQjjnCA0QnUYzJedzcSOPL+aa+UM/3iy0yop320N nlTo= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:MIME-Version:Received:Received:Date:Message-ID:Subject:From:To:Content-Type:X-IsSubscribed:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=R/tu1mOq0L257STJ1ieDwzbqZCq56CQaV99bhFJ0jXh1d5JXrpCdyYyEJo4UhI qySzQmWcMgIVLR5hMbI/v7Ry54tiUclaec8LyiqsujEG7bPc7K9tm3HtVuzBlVIZ PYJncHy5jUZwOu5oofZkClssgADEpMOPp1T/9/VwAvAB4=; Received: (qmail 24108 invoked by alias); 23 Aug 2012 08:35:59 -0000 Received: (qmail 23999 invoked by uid 22791); 23 Aug 2012 08:35:58 -0000 X-SWARE-Spam-Status: No, hits=-4.1 required=5.0 tests=AWL, BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, KHOP_RCVD_TRUST, RCVD_IN_DNSWL_LOW, RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Aug 2012 08:35:23 +0000 Received: by wgbds1 with SMTP id ds1so216124wgb.2 for ; Thu, 23 Aug 2012 01:35:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.97.135 with SMTP id ea7mr13019041wib.11.1345710922137; Thu, 23 Aug 2012 01:35:22 -0700 (PDT) Received: by 10.194.92.99 with HTTP; Thu, 23 Aug 2012 01:35:22 -0700 (PDT) Date: Thu, 23 Aug 2012 16:35:22 +0800 Message-ID: Subject: [doc] Fix typo in gty.texi From: Mingjie Xing To: gcc-patches X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org Hi, A very small patch. OK? 2012-08-23 Mingjie Xing * doc/gty.texi: Fix typo. Regards, Mingjie 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