93f05b64ae
They have the same lifetime. It's a match! Both structures are native context dependent and dealt with (creation, clearing, gathering feedback) at the same time. By treating the spaces used for literal boilerplates as feedback vector slots, we no longer have to keep track of the materialized literal count elsewhere. A follow-on CL removes even more parser infrastructure related to this count. BUG=v8:5456 Review-Url: https://codereview.chromium.org/2655853010 Cr-Commit-Position: refs/heads/master@{#42771}
35 lines
704 B
Plaintext
35 lines
704 B
Plaintext
#
|
|
# Autogenerated by generate-bytecode-expectations.
|
|
#
|
|
|
|
---
|
|
wrap: yes
|
|
|
|
---
|
|
snippet: "
|
|
with ({x:42}) { return x; }
|
|
"
|
|
frame size: 2
|
|
parameter count: 1
|
|
bytecode array length: 22
|
|
bytecodes: [
|
|
/* 30 E> */ B(StackCheck),
|
|
/* 34 S> */ B(CreateObjectLiteral), U8(0), U8(2), U8(1), R(1),
|
|
B(Ldar), R(1),
|
|
B(ToObject), R(1),
|
|
B(Ldar), R(closure),
|
|
B(CreateWithContext), R(1), U8(1),
|
|
B(PushContext), R(0),
|
|
/* 50 S> */ B(LdaLookupSlot), U8(2),
|
|
B(PopContext), R(0),
|
|
/* 62 S> */ B(Return),
|
|
]
|
|
constant pool: [
|
|
FIXED_ARRAY_TYPE,
|
|
FIXED_ARRAY_TYPE,
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["x"],
|
|
]
|
|
handlers: [
|
|
]
|
|
|