v8/test/cctest/interpreter/bytecode_expectations/NewTarget.golden
Santiago Aboy Solanes 9d3dc6f219 [interpreter] Make FunctionEntry StackCheck bytecodes implicit
FunctionEntry StackChecks is one of the two cases where we generate a
StackCheck bytecode. In these cases, we do stack check against the js
limit (not to be confused with the real js limit). Their purpose is to
be able to interrupt the running code.

We can omit the FunctionEntry StackCheck by embedding its code into
the InterpreterEntryTrampoline builtin. We save one bytecode per
interpreted function.

This change has rippling effects for optimized code, as well as the
deoptimizer.

Bug: v8:10149, v8:9977, v8:9960
Change-Id: I6156de48b3bc0b519dd21190a8e6214fbe96c78d
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1914218
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#66206}
2020-02-10 17:05:23 +00:00

40 lines
472 B
Plaintext

#
# Autogenerated by generate-bytecode-expectations.
#
---
wrap: yes
---
snippet: "
return new.target;
"
frame size: 1
parameter count: 1
bytecode array length: 3
bytecodes: [
/* 34 S> */ B(Ldar), R(0),
/* 52 S> */ B(Return),
]
constant pool: [
]
handlers: [
]
---
snippet: "
new.target;
"
frame size: 1
parameter count: 1
bytecode array length: 2
bytecodes: [
/* 34 S> */ B(LdaUndefined),
/* 46 S> */ B(Return),
]
constant pool: [
]
handlers: [
]