undefined | Better HN

0 pointsconvolvatron2y ago0 comments

I did this once - a compacting collector for C. it was a really trivial mark/sweep - and as I recall you had to write functions for each type to perform the object graph traversal. for artificial memory-intensive workloads it was around 8x the performance of boehm.

0 comments

2 comments · 1 top-level

antiviral2y ago· 1 in thread

Is this anything you'd be willing to share publicly?

How did you determine the scope of a chunk of memory? I believe you need this to run any of the GC algorithms.

I checked the hboehm documentation (1) and in the section on "Locating roots" it says "you don't want to know":

-Runtime stack(s): you don't really want to know.Need consistent caller-save reg. snapshot

-Static data segments: you don't want to know that either.

-Very platform dependent But you only have to do it once per platform.

(1) https://www.hboehm.info/gc/04tutorial.pdf

convolvatronOP2y ago

yeah, of course. its old crap that I'd have to find if I can. I will look.

roots in boehm means globals and the stack. this little thing had explicitly declared roots.

edit: I found it, mail me at yuri@tenuki.org. be prepared to be unimpressed.

j / k navigate · click thread line to collapse