Issue 16848020: Always reset allowed OSR nesting level when reverting interrupt code patches.

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 16848020: Always reset allowed OSR nesting level when reverting interrupt code patches. (Closed)

Created:
7 years, 6 months ago by Jakob Kummerow

Modified:
7 years, 6 months ago

Reviewers:
Yang

CC:
v8-dev

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

Visibility:
Public.

Always reset allowed OSR nesting level when reverting interrupt code patches. Also, --trap-on-deopt should only affect optimized functions, not hydrogen stubs. R=yangguo@chromium.org Committed: http://code.google.com/p/v8/source/detail?r=15204

Created: 7 years, 6 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+5 lines, -7 lines)			Patch
M	src/arm/lithium-codegen-arm.cc	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/deoptimizer.cc	View	1 chunk	+1 line, -0 lines	0 comments	Download
M	src/ia32/lithium-codegen-ia32.cc	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/mips/lithium-codegen-mips.cc	View	1 chunk	+1 line, -1 line	0 comments	Download
M	src/runtime.cc	View	1 chunk	+0 lines, -3 lines	0 comments	Download
M	src/x64/lithium-codegen-x64.cc	View	1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 3 (0 generated)

Jakob Kummerow

7 years, 6 months ago (2013-06-19 09:38:36 UTC) #3

Message was sent while issue was closed.

Committed patchset #1 manually as r15204 (presubmit successful).