• mstarzinger's avatar
    [turbofan] Disable usage of {maybe_assigned} variable flag. · b02e7fb8
    mstarzinger authored
    This disables the usage of the {maybe_assigned} flag that the variable
    resolution computes for each variable on non-asm.js code. Note that the
    analysis is fundamentally broken for destructuring and top-level lexical
    variables. Also note that this still uses the analysis for asm.js code
    even though it is not validated. One can still trigger the bug by using
    invalid constructs within a function marked with "use asm". The fix is
    intentionally minimal so that it can be merged to release branches.
    
    R=bmeurer@chromium.org
    TEST=mjsunit/regress/regress-crbug-659915
    BUG=chromium:659915
    
    Review-Url: https://codereview.chromium.org/2471523005
    Cr-Commit-Position: refs/heads/master@{#40716}
    b02e7fb8
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...