• yangguo's avatar
    [debug] introduce precise binary code coverage. · d71ef941
    yangguo authored
    With precise binary code coverage, the reported count is either 0 or 1.
    We only report 1 the first time we collect coverage data after the
    function has been executed.
    
    Since we do not care about the accurate execution count, we can optimize
    the function once it has been executed once.
    
    Also change best effort coverage to be implicitly binary.
    
    R=caseq@chromium.org, jgruber@chromium.org, pfeldman@chromium.org
    BUG=v8:5808
    
    Review-Url: https://codereview.chromium.org/2766573003
    Cr-Commit-Position: refs/heads/master@{#44074}
    d71ef941
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...