diff options
-rw-r--r-- | ChangeLog | 2 | ||||
-rw-r--r-- | doc/platforms/README.amiga | 2 | ||||
-rw-r--r-- | extra/AmigaOS.c | 2 | ||||
-rw-r--r-- | malloc.c | 2 | ||||
-rw-r--r-- | new_hblk.c | 2 | ||||
-rw-r--r-- | os_dep.c | 2 | ||||
-rw-r--r-- | reclaim.c | 2 |
7 files changed, 7 insertions, 7 deletions
@@ -10527,7 +10527,7 @@ being collected or finalized. the change in the definition of accessibility (by John Ellis). * Added support for operator new[] (by John Ellis). Since most compilers don't yet support operator new[], it is conditionalized on --DOPERATOR_NEW_ARRAY. The code is untested, but its trivial and looks +-DOPERATOR_NEW_ARRAY. The code is untested, but it's trivial and looks correct. * The test program test_gc_c++ (later renamed test_cpp.cc) tries to test for the C++-specific functionality not tested by the diff --git a/doc/platforms/README.amiga b/doc/platforms/README.amiga index 6dc6378c..fc9c72ab 100644 --- a/doc/platforms/README.amiga +++ b/doc/platforms/README.amiga @@ -49,7 +49,7 @@ WHATS NEW: GC from returning chip-mem. Beware that it slows down a lot when a program is rapidly allocating/deallocating when there's either very little fast-memory left or very little - chip-memory left. Its not a very common situation, but gctest + chip-memory left. It's not a very common situation, but gctest sometimes (very rare) use many minutes because of this. GC_AMIGA_RETRY - If gc succeed allocating memory, but it is chip-mem, diff --git a/extra/AmigaOS.c b/extra/AmigaOS.c index c55b985d..7db7eab6 100644 --- a/extra/AmigaOS.c +++ b/extra/AmigaOS.c @@ -356,7 +356,7 @@ void *GC_amiga_rec_alloc(size_t size,void *(*AllocFunction)(size_t size2),const void *GC_amiga_allocwrapper_any(size_t size,void *(*AllocFunction)(size_t size2)){ void *ret; - GC_amiga_dontalloc=TRUE; /* Pretty tough thing to do, but its indeed necessary. */ + GC_amiga_dontalloc=TRUE; /* Pretty tough thing to do, but it's indeed necessary. */ latestsize=size; ret=(*AllocFunction)(size); @@ -607,7 +607,7 @@ GC_API void GC_CALL GC_free(void * p) LOCK(); GC_bytes_freed += sz; if (IS_UNCOLLECTABLE(knd)) GC_non_gc_bytes -= sz; - /* Its unnecessary to clear the mark bit. If the */ + /* It's unnecessary to clear the mark bit. If the */ /* object is reallocated, it doesn't matter. O.w. the */ /* collector will do it, since it's on a free list. */ if (ok -> ok_init && EXPECT(sz > sizeof(word), TRUE)) { @@ -110,7 +110,7 @@ GC_INNER ptr_t GC_build_fl(struct hblk *h, size_t sz, GC_bool clear, word *p, *prev; word *last_object; /* points to last object in new hblk */ - /* Do a few prefetches here, just because its cheap. */ + /* Do a few prefetches here, just because it's cheap. */ /* If we were more serious about it, these should go inside */ /* the loops. But write prefetches usually don't seem to */ /* matter much. */ @@ -1990,7 +1990,7 @@ void GC_register_data_segments(void) # endif #ifdef DATASTART_USES_BSDGETDATASTART -/* Its unclear whether this should be identical to the above, or */ +/* It's unclear whether this should be identical to the above, or */ /* whether it should apply to non-x86 architectures. */ /* For now we don't assume that there is always an empty page after */ /* etext. But in some cases there actually seems to be slightly more. */ @@ -666,7 +666,7 @@ GC_INNER void GC_start_reclaim(GC_bool report_if_found) } } } /* otherwise free list objects are marked, */ - /* and its safe to leave them */ + /* and it's safe to leave them. */ BZERO(rlist, (MAXOBJGRANULES + 1) * sizeof(void *)); } |