Mythri A b086cb7b9a Check that function was prepared before optimizing using manually ... With lazy feedback allocation and bytecode flushing we need to call %PrepareFunctionForOptimize before we call %OptimizeFunctionOnNextCall/ %OptimizeOsr. This cl: 1. Adds an additional state in pending optimized table to check if the optimization was triggered manually. 2. Changes the compilation pipeline to delete the entry from pending optimized table only if the optimization was triggered through %OptimizeFunctionOnNextCall / %OptimizeOsr. 3. Adds a check to enforce %PrepareFunctionForOptimize was called. 4. Adds a new run-time flag to only check in the d8 test runner. We don't want this check enabled in other cases like clusterfuzz that doesn't ensure %PrepareFunctionForOptimize is called. Bug: v8:8394, v8:8801, v8:9183 Change-Id: I9ae2b2da812e313c746b6df0b2da864c2ed5de51 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1664810 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#62653}		2019-07-11 14:57:49 +00:00
..
testdata	Check that function was prepared before optimizing using manually	2019-07-11 14:57:49 +00:00
__init__.py	[test] make python recognize tools and tools/unittests as packages	2018-12-17 12:12:43 +00:00
predictable_wrapper_test.py
run_perf_test.py	[tools] Implement confidence-based number of runs	2019-05-09 09:42:28 +00:00
run_tests_test.py	[cleanup] Replace underscore by minus in d8 flags	2019-04-03 12:32:08 +00:00
v8_presubmit_test.py	[test] add an option for disabling linter cache in the pre_submit check	2018-12-18 15:37:09 +00:00