@jartine@justjs14@tekknolagi@v8js@googledevs That's not code of the runtime but merely Torque which translates .tq to C++ files (roughly). You can file a bug here https://t.co/usho1bVn2r
@GavinRayDev@v8js The main idea is to align the heap cage to allow using the LSB of the upper half of a true heap pointer for sign extension on decompression. This allows for differentiating pointers from nullptr/sentinel. The rest is just stripping away bits that can be recovered from a global.
@Taaanos @ulandev @PayerHannes @tverwaes https://t.co/2rntNF8oHm is somewhat up to date on the inner workings of the GC but also outdated on the spaces. 2/2
@Taaanos @ulandev @PayerHannes @tverwaes Cell space, property cell space, map space and old pointer space don't exist anymore. There's no documentation on todays model, one reason being that it's also (still) constantly changing (e.g. instruction streams are being moved out of code space). 1/2
@tekknolagi@mraleph@PayerHannes https://t.co/9rwqLMyS1G
We had a PoC but there's definitely work needed to make this fly in production. Problems are around reducing overhead (optimize away statepoints, stackmap size) and correctness (inner pointers, ptrtoint).
@dinfuehr@erikcorry @andywingo I concluded that the problems were (a) lock-step of mark-evacuate-update phases not being as efficient and (b) Cheney being a bit more cache friendly (e.g. not requiring out-of-line markbit access).
We never went all the way thought with concurrency and optimizations.
@smarr@cfbolz@v8js If you can afford a V8 checkout you can already build and use it standalone.
Standalone as in without V8: It's not yet there but there's scripts to get started checked in already https://t.co/13Cq6izOev
@erikcorry Imagine this turn-around back then... (full build; no goma)
$ time autoninja -C out/x64.debug/ cppgc_hello_world
ninja: Entering directory `out/x64.debug/'
[0/1] Regenerating ninja files
[168/168] LINK ./cppgc_hello_world
real 0m4.479s
user 2m8.169s
sys 0m9.496s
@fijall@hashseed@mraleph @tverwaes @bmeurer@PayerHannes @ulandeg If you are comfortable with sharing and have a few minutes, a chrome://tracing trace taken with the "blink_gc" and "v8.gc" categories (including disabled by default) would be equally awesome.
@fijall@hashseed@mraleph @tverwaes @bmeurer@PayerHannes @ulandeg Can you file an issue on https://t.co/5XZMx8xPp4, including the repro steps and Chrome version(s). We are aware of some problems and are actively working in that area. Would be good to double-check what's going on though.
hej @conc_at#concat18, thanks for having me! 🔥 Slides for my talk "Live and let die: Untangling the web of objects" are available here: https://t.co/oaxdS65Dv8
Next day, next talk: @mlippautz from Google's V8 and Chromium team in Munich is giving you all the insights about how JavaScript connects to the DOM.
https://t.co/qgZBb1zFP2 #concat#conference#web