yangguo 3c1dc424d3 [ignition, debugger] correctly set position for return with elided bytecode. ... We may not emit bytecode for the evaluation of the to-be-returned expression. In that case we cannot set two return positions for a return statement (one before and one after the expression evaluation). This sets the interpreter apart from full-codegen. Make sure that we always have the second of the two return positions. Note that we end up with separate test cases for ignition and FCG. R=rmcilroy@chromium.org, vogelheim@chromium.org BUG=v8:4690 LOG=N Review URL: https://codereview.chromium.org/1801473003 Cr-Commit-Position: refs/heads/master@{#34771}		2016-03-15 08:28:03 +00:00
..
dead-code-source-position.js	[interpreter] source positions should not be emitted for dead code.	2016-02-05 13:29:45 +00:00
debug-break-on-stack.js	[interpreter, debugger] replace bytecode on-stack for debugging.	2016-02-23 13:11:27 +00:00
debug-break.js	[interpreter, debugger] support debug breaks via bytecode array copy	2016-02-22 13:17:52 +00:00
debugger-statement.js	[interpreter, debugger] implement debugger statement.	2016-02-04 15:07:06 +00:00
elided-instruction-no-ignition.js	[ignition, debugger] correctly set position for return with elided bytecode.	2016-03-15 08:28:03 +00:00
elided-instruction.js	[ignition, debugger] correctly set position for return with elided bytecode.	2016-03-15 08:28:03 +00:00
optimized-debug-frame.js	[interpreter] Add tests for translating PC from optimized frame.	2016-03-02 14:54:55 +00:00
optimized-stack-trace.js	[interpreter] Add tests for translating PC from optimized frame.	2016-03-02 14:54:55 +00:00
stack-trace-source-position.js	[interpreter] temporarily remove --ignition from test.	2016-02-04 11:47:00 +00:00