Skip to main content
9 events
when toggle format what by license comment
Jun 16, 2017 at 10:51 comment added Jules ... a problem, because the environment can arrange for GC to take place at "safe points" where the interpreter knows that all data is safely stored in the interpreted stacks.
Jun 16, 2017 at 10:49 comment added Jules One additional complexity that you need to be aware of in compiled vs interpreted runtimes relates to this sentence in your answer: "(Tracing) garbage collection usually starts by walking the call stacks of all threads that are currently running." My experience of implementing GC in a compiled environment is that tracing the stacks is not enough. The starting point is usually suspending the threads for long enough to trace from their registers, because they may have references in those registers that haven't yet been stored in the stack. For an interpreter, this isn't usually ...
Jun 16, 2017 at 9:54 comment added Kroltan @corsiKa Or rather, the line is much more distinct. Now we see that those are different unrelated concepts, and not antonyms of eachother.
Jun 15, 2017 at 12:24 comment added Matti Virkkunen Just to add a bit about languages that don't come with GC support: It's true that C and other such languages don't provide information about call stacks, but if you're OK with some platform-specific code (usually including a bit of assembly code) it's still possible to implement "conservative garbage collection". The Boehm GC is an example of this used in real life programs.
Jun 15, 2017 at 2:15 comment added corsiKa Between utility libraries and JIT compiling, the lines between "compiled to native" and "runs in a runtime environment" are becoming more and more blurred.
Jun 14, 2017 at 19:42 vote accept Chris
Jun 14, 2017 at 11:06 history edited avdgrinten CC BY-SA 3.0
added 136 characters in body
Jun 14, 2017 at 10:57 review First posts
Jul 7, 2017 at 21:53
Jun 14, 2017 at 10:53 history answered avdgrinten CC BY-SA 3.0