From c3af645c4ca4ed88db366564d3144ae509247ebf Mon Sep 17 00:00:00 2001
From: Trevor Saunders <tsaunders@mozilla.com>
Date: Sat, 17 May 2014 23:15:55 +0000
Subject: [PATCH] comment ggc_handle_finalizers

	* ggc-page.c (ggc_handle_finalizers): Add comment.

From-SVN: r210569
---
 gcc/ChangeLog  | 4 ++++
 gcc/ggc-page.c | 5 +++++
 2 files changed, 9 insertions(+)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 53dc3e16797..c26bf6ea6a0 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2014-05-17  Trevor Saunders  <tsaunders@mozilla.com>
+
+	* ggc-page.c (ggc_handle_finalizers): Add comment.
+
 2014-05-17  Trevor Saunders  <tsaunders@mozilla.com>
 
 	* ggc-common.c (ggc_internal_cleared_alloc): Adjust.
diff --git a/gcc/ggc-page.c b/gcc/ggc-page.c
index b3a1a2a103f..a8d8d0ee859 100644
--- a/gcc/ggc-page.c
+++ b/gcc/ggc-page.c
@@ -1859,6 +1859,11 @@ clear_marks (void)
     }
 }
 
+/* Check if any blocks with a registered finalizer have become unmarked. If so
+   run the finalizer and unregister it because the block is about to be freed.
+   Note that no garantee is made about what order finalizers will run in so
+   touching other objects in gc memory is extremely unwise.  */
+
 static void
 ggc_handle_finalizers ()
 {