v8/test/cctest/interpreter/bytecode_expectations/NewTarget.golden
adamk 6768456db5 Use Variable::binding_needs_init() to determine hole initialization
The old code was using VariableMode, but that signal is both
over-pessimistic (some CONST and LET variables need no hole-initialization)
and inconsistent with other uses of the InitializationFlag enum (such
as %LoadLookupSlot).

This changes no observable behavior, but removes unnecessary hole
initialization and hole checks in a few places, including
block-scoped function declarations, super property lookups,
and new.target.

R=bmeurer@chromium.org, neis@chromium.org

Review-Url: https://codereview.chromium.org/2201193004
Cr-Commit-Position: refs/heads/master@{#38395}
2016-08-05 17:51:17 +00:00

46 lines
654 B
Plaintext

#
# Autogenerated by generate-bytecode-expectations.
#
---
pool type: mixed
execute: yes
wrap: yes
---
snippet: "
return new.target;
"
frame size: 1
parameter count: 1
bytecode array length: 7
bytecodes: [
B(Mov), R(new_target), R(0),
/* 30 E> */ B(StackCheck),
/* 34 S> */ B(Ldar), R(0),
/* 53 S> */ B(Return),
]
constant pool: [
]
handlers: [
]
---
snippet: "
new.target;
"
frame size: 1
parameter count: 1
bytecode array length: 6
bytecodes: [
B(Mov), R(new_target), R(0),
/* 30 E> */ B(StackCheck),
/* 34 S> */ B(LdaUndefined),
/* 46 S> */ B(Return),
]
constant pool: [
]
handlers: [
]