It’s a big pain, though. Signed integer overflow, float<->int casting UB, etc. are all things people often don’t want in their language and makes the generated C really ugly. And you can’t do *good* GC. :) You need stack and register maps, which are impossible in C.
It can’t be a moving GC, which means it can’t have bump allocating TLABs in the nursery. So malloc will be slower than it needs to be.
-
-
The JSC GC is conservative and non-moving, seems to be doing fine. Agreed malloc when you can't just bump a pointer isn't as fast, but you have other costs that this, no?
-
Well, to be honest I don’t really have the motivation for a Twitter debate about GC strategies right now :) Suffice it to say that if you’re targeting C you’re limited in your choice of GC algorithms.
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.