b28b7e1328
For historical reasons, the interpreter's bytecode expectations tests
required a type for the constant pool. This had two disadvantages:
1. Strings and numbers were not visible in mixed pools, and
2. Mismatches of pool types (e.g. when rebaselining) would cause parser
errors
This removes the pool types, making everything 'mixed', but appending
the values to string and number valued constants. Specifying a pool type
in the *.golden header now prints a warning (for backwards compatibility).
BUG=v8:5350
Review-Url: https://codereview.chromium.org/2310103002
Cr-Commit-Position: refs/heads/master@{#39216}
36 lines
717 B
Plaintext
36 lines
717 B
Plaintext
#
|
|
# Autogenerated by generate-bytecode-expectations.
|
|
#
|
|
|
|
---
|
|
execute: yes
|
|
wrap: yes
|
|
|
|
---
|
|
snippet: "
|
|
with ({x:42}) { return x; }
|
|
"
|
|
frame size: 3
|
|
parameter count: 1
|
|
bytecode array length: 22
|
|
bytecodes: [
|
|
/* 30 E> */ B(StackCheck),
|
|
/* 34 S> */ B(CreateObjectLiteral), U8(0), U8(0), U8(1), R(1),
|
|
B(Ldar), R(1),
|
|
B(ToObject), R(2),
|
|
B(Ldar), R(closure),
|
|
B(CreateWithContext), R(2), 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: [
|
|
]
|
|
|