Re:GCC 8.1 Released
by pavanky on Wednesday May 02, 2018 @10:03AM
(#16976947)
Looks like they solved those issues in 8.1
[ Parent
| on HN ]
Re:GCC 8.1 Released
by smitherfield on Wednesday May 02, 2018 @10:32AM
(#16977209)
"As before, values stored on the stack are scanned conservatively"
Why would values on the stack be garbage-collected at all? Do they mean scanning the stack for live references?
I read this as "if it is on the stack and looks like a reference when you squint your eyes, then we treat it as a reference" compared to objects on the heap where the GC seems to know the exact location of all references.
Re:GCC 8.1 Released
by FullyFunctional on Wednesday May 02, 2018 @01:20PM
(#16979108)
Right that's the standard conservative garbage collection. However, new results show that it's significantly worse than a precise collector (reference pending).
Re:GCC 8.1 Released
by BlackFingolfin on Wednesday May 02, 2018 @03:49PM
(#16980544)
I'd love to see that reference, as I've not yet seen an example where this was true in practicd, but know several examples where it is definitely false (e.g. we use a modification of the Julia GC which uses consevative stack scanning to allow interop with another system, and it seems to perform very well).
Re:GCC 8.1 Released
by FullyFunctional on Sunday May 06, 2018 @11:55PM
(#17010302)
Sorry for the late follow up. Hopefully you're still around to notice. Apparently there was previous HN discussion on this, but I haven't seen it (or looked for it):
https://www.excelsiorjet.com/blog/articles/conservative-gc-i...
I think that only scanning the stack conservatively should not change much from a completely precise GC. The chances of misidentifying a potential reference to an enormous data structure that is collectable are pretty slim in a memory region as small as a typical stack.
Scanning the entire heap is different because of its generally much bigger size. It's far more likely then to see references where there are none.