Skip to content

Commit

Permalink
Release 1.02
Browse files Browse the repository at this point in the history
  • Loading branch information
knizhnik committed Mar 31, 2014
1 parent 1a48526 commit f125cff
Show file tree
Hide file tree
Showing 4 changed files with 10 additions and 2 deletions.
7 changes: 7 additions & 0 deletions CHANGES
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
--- Release version 1.01 (22.03.2014) -------------------------------------

Initial version

--- Release version 1.02 (01.04.2014) -------------------------------------

Multisegment implementation of copying garbage collector
2 changes: 1 addition & 1 deletion copygc/gc.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ namespace GC
for (Pin* pin = pinnedObjects; pin != NULL; pin = pin->next) {
(void)_copy(pin->obj);
}
// And finally copy and andject all roots
// And finally copy and adjust all roots
for (Root* root = roots; root != NULL; root = root->next) {
root->copy(this);
}
Expand Down
2 changes: 1 addition & 1 deletion makefile
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ clean:
rm -f *.o *.a *.so *.so.* $(GC_EXAMPLES)

tgz: clean
cd ..; tar --exclude=.svn -chvzf cppgc-1.01.tar.gz cppgc
cd ..; tar --exclude=.svn -chvzf cppgc-1.02.tar.gz cppgc

zip: clean
cd ..; zip -r cppgc.zip cppgc
Expand Down
1 change: 1 addition & 0 deletions mark_n_sweep_gc.txt
Original file line number Diff line number Diff line change
Expand Up @@ -460,6 +460,7 @@ of cloned object:

Copying garbage collector is really fast, because it is not using standard malloc/free. Testgc example shows about 8 times
better results with copying garbage collector than with mark&sweep garbage collector.
But lack of finalization and necessity to pin object are also significant drawbacks.


Let's now compare performance.
Expand Down

0 comments on commit f125cff

Please sign in to comment.