Ignore:
Timestamp:
Jun 25, 2012, 7:53:39 PM (13 years ago)
Author:
[email protected]
Message:

JSC should try to make profiling deterministic because otherwise reproducing failures is
nearly impossible
https://bugs.webkit.org/show_bug.cgi?id=89940

Rubber stamped by Gavin Barraclough.

This rolls out the part of http://trac.webkit.org/changeset/121215 that introduced randomness
into the system. Now, instead of randomizing the tier-up threshold, we always set it to an
artificially low (and statically predetermined!) value. This gives most of the benefit of
threshold randomization without actually making the system behave completely differently on
each invocation.

  • bytecode/ExecutionCounter.cpp:

(JSC::ExecutionCounter::setThreshold):

  • runtime/Options.cpp:

(Options):
(JSC::Options::initializeOptions):

  • runtime/Options.h:

(Options):

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/runtime/Options.cpp

    r121215 r121218  
    6868int32_t executionCounterIncrementForReturn;
    6969
     70bool randomizeExecutionCountsBetweenCheckpoints;
    7071int32_t maximumExecutionCountsBetweenCheckpoints;
    7172
     
    191192    SET(executionCounterIncrementForReturn, 15);
    192193   
     194    SET(randomizeExecutionCountsBetweenCheckpoints, false);
    193195    SET(maximumExecutionCountsBetweenCheckpoints, 1000);
    194196
Note: See TracChangeset for help on using the changeset viewer.