Issue 21221003: Fix many tests that try to force an OSR by checking OptimizationStatus() to instead check Optimizat…

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 21221003: Fix many tests that try to force an OSR by checking OptimizationStatus() to instead check Optimizat… (Closed)

Created:
7 years, 4 months ago by titzer

Modified:
7 years, 4 months ago

Reviewers:
Michael Starzinger

CC:
v8-dev

Base URL:
https://v8.googlecode.com/svn/branches/bleeding_edge

Visibility:
Public.

Fix many tests that try to force an OSR by checking OptimizationStatus() to instead check OptimizationCount(). BUG= R=mstarzinger@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=15951

Created: 7 years, 4 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+17 lines, -12 lines)			Patch
M	test/mjsunit/array-literal-transitions.js	View	1	1 chunk	+4 lines, -2 lines	0 comments	Download
M	test/mjsunit/count-based-osr.js	View		1 chunk	+3 lines, -3 lines	0 comments	Download
M	test/mjsunit/regress/regress-1118.js	View	1	1 chunk	+4 lines, -2 lines	0 comments	Download
M	test/mjsunit/regress/regress-2618.js	View		2 chunks	+2 lines, -3 lines	0 comments	Download
M	test/mjsunit/regress/regress-crbug-150545.js	View		1 chunk	+4 lines, -2 lines	0 comments	Download

Total messages: 3 (0 generated)

titzer

7 years, 4 months ago (2013-07-30 09:29:09 UTC) #3

Message was sent while issue was closed.

Committed patchset #2 manually as r15951 (presubmit successful).