summaryrefslogtreecommitdiff
path: root/blacklst.c
diff options
context:
space:
mode:
authorIvan Maidanski <ivmai@mail.ru>2023-05-13 11:56:36 +0300
committerIvan Maidanski <ivmai@mail.ru>2023-05-13 11:56:36 +0300
commitffc64167e4d0eccbee19794d7eac6b6946cddb63 (patch)
treea3b96622e540a40cd664a285de5abde9a42c50cd /blacklst.c
parent1c2d6cf5439a052e06369c36746d3c1f07900e22 (diff)
downloadbdwgc-ffc64167e4d0eccbee19794d7eac6b6946cddb63.tar.gz
Fix old name (typo) of gc_priv.h
* blacklst.c: Fix old file name in comment ("gc_priv.h"). * include/private/gcconfig.h: Likewise. * tools/setjmp_t.c (main): Fix old file name in message ("gc_priv.h").
Diffstat (limited to 'blacklst.c')
-rw-r--r--blacklst.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/blacklst.c b/blacklst.c
index 5d083ff9..faf05da3 100644
--- a/blacklst.c
+++ b/blacklst.c
@@ -18,7 +18,7 @@
* We maintain several hash tables of hblks that have had false hits.
* Each contains one bit per hash bucket; If any page in the bucket
* has had a false hit, we assume that all of them have.
- * See the definition of page_hash_table in gc_private.h.
+ * See the definition of page_hash_table in gc_priv.h.
* False hits from the stack(s) are much more dangerous than false hits
* from elsewhere, since the former can pin a large object that spans the
* block, even though it does not start on the dangerous block.
@@ -233,7 +233,7 @@ GC_INNER void GC_unpromote_black_lists(void)
}
/*
- * Is the block starting at h of size len bytes black listed? If so,
+ * Is the block starting at h of size len bytes black listed? If so,
* return the address of the next plausible r such that (r, len) might not
* be black listed. (R may not actually be in the heap. We guarantee only
* that every smaller value of r after h is also black listed.)