f88fe51a00
The scavenger should never consider mark bits for promotion/copy as this creates weird livetimes at the start of incremental marking. E.g. consider an object marked black by the marker at the start of incremental marking. A scavenge would promote it to the old generation although it could --and for short-living objects actually does-- become unreachable during marking Also, keeping this invariant significantly simplifies young generation mark compacting as we can compare against the scavenging decision without keeping different sets of markbits. BUG=chromium:651354 R=hpayer@chromium.org Review-Url: https://codereview.chromium.org/2397713002 Cr-Commit-Position: refs/heads/master@{#40026} |
||
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
common | ||
fuzzer | ||
inspector | ||
inspector_protocol_parser_test | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mozilla | ||
preparser | ||
promises-aplus | ||
simdjs | ||
test262 | ||
unittests | ||
webkit | ||
bot_default.gyp | ||
bot_default.isolate | ||
BUILD.gn | ||
default.gyp | ||
default.isolate | ||
optimize_for_size.gyp | ||
optimize_for_size.isolate | ||
perf.gyp | ||
perf.isolate |