2017-02-24 17:48:49 +00:00
|
|
|
#
|
|
|
|
|
# Autogenerated by generate-bytecode-expectations.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
wrap: no
|
|
|
|
|
test function name: f
|
|
|
|
|
async iteration: yes
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
snippet: "
|
|
|
|
|
async function f() {
|
|
|
|
|
for await (let x of [1, 2, 3]) {}
|
|
|
|
|
}
|
|
|
|
|
f();
|
|
|
|
|
"
|
2019-08-23 14:23:52 +00:00
|
|
|
frame size: 19
|
2017-02-24 17:48:49 +00:00
|
|
|
parameter count: 1
|
2020-03-20 11:13:04 +00:00
|
|
|
bytecode array length: 319
|
2017-02-24 17:48:49 +00:00
|
|
|
bytecodes: [
|
2019-01-31 15:36:58 +00:00
|
|
|
B(SwitchOnGeneratorState), R(0), U8(0), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(closure), R(4),
|
|
|
|
|
B(Mov), R(this), R(5),
|
2020-02-10 16:09:27 +00:00
|
|
|
/* 16 E> */ B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionEnter), R(4), U8(2),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Star), R(0),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(context), R(4),
|
|
|
|
|
/* 43 S> */ B(CreateArrayLiteral), U8(2), U8(0), U8(37),
|
2018-10-11 08:35:56 +00:00
|
|
|
B(Star), R(7),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaNamedProperty), R(7), U8(3), U8(1),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfUndefinedOrNull), U8(15),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
|
|
|
|
B(CallProperty0), R(8), R(7), U8(3),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(JumpIfJSReceiver), U8(23),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(CallRuntime), U16(Runtime::kThrowSymbolAsyncIteratorInvalid), R(0), U8(0),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(7), U8(4), U8(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
|
|
|
|
B(CallProperty0), R(8), R(7), U8(7),
|
|
|
|
|
B(Star), R(8),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_CreateAsyncFromSyncIterator), R(8), U8(1),
|
|
|
|
|
B(Star), R(6),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(6), U8(5), U8(9),
|
2018-01-11 17:24:11 +00:00
|
|
|
B(Star), R(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
|
|
|
|
B(Mov), R(context), R(10),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaTrue),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
2019-01-14 14:15:52 +00:00
|
|
|
/* 38 S> */ B(CallProperty0), R(5), R(6), U8(11),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
|
|
|
|
B(Mov), R(0), R(12),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionAwaitUncaught), R(12), U8(2),
|
|
|
|
|
B(SuspendGenerator), R(0), R(0), U8(12), U8(0),
|
|
|
|
|
B(ResumeGenerator), R(0), R(0), U8(12),
|
|
|
|
|
B(Star), R(12),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_GeneratorGetResumeMode), R(0), U8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
2017-05-24 15:48:27 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(13),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(12),
|
Reland "[async-iteration] implement spec-change to `yield` in async generators"
Per https://github.com/tc39/proposal-async-iteration/pull/102/files:
AsyncGeneratorResolve no longer unwraps a value component. Instead, the value is
unwrapped before the builtin call via Await, allowing Promise rejections to
affect the generator control flow.
Thus, all `yield <expr>` implicitly become `yield await <expr>`.
Additionally, `return <expr>` becomes `return await <expr>`. Finally, when the
generator is resumed with `.return()`, the parameter passed to .return() is
awaited before generator execution properly continues).
BUG=v8:6187, v8:5855
R=littledan@chromium.org, neis@chromium.org, adamk@chromium.org
TBR=rmcilroy@chromium.org, neis@chromium.org
Cq-Include-Trybots: master.tryserver.v8:v8_linux_noi18n_rel_ng
Change-Id: Id7718028fd555481f9f4ca0dbecfa788e3057c48
Reviewed-on: https://chromium-review.googlesource.com/594500
Reviewed-by: Caitlin Potter <caitp@igalia.com>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Caitlin Potter <caitp@igalia.com>
Cr-Commit-Position: refs/heads/master@{#47058}
2017-08-01 14:45:03 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(12),
|
|
|
|
|
B(Mov), R(12), R(11),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(11), U8(1),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(11), U8(6), U8(13),
|
2020-03-20 11:13:04 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(22),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(11), U8(7), U8(15),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(11),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
|
|
|
|
B(Mov), R(11), R(1),
|
2019-01-31 15:36:58 +00:00
|
|
|
/* 38 S> */ B(Mov), R(1), R(3),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(11),
|
2020-03-20 11:13:04 +00:00
|
|
|
/* 23 E> */ B(JumpLoop), U8(76), I8(0),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaSmi), I8(-1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(9),
|
|
|
|
|
B(Star), R(8),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(Jump), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(9),
|
2018-10-11 08:35:56 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(8),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
2020-03-11 15:07:16 +00:00
|
|
|
B(SetPendingMessage),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(10),
|
|
|
|
|
B(Ldar), R(7),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(94),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(6), U8(8), U8(17),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(14),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfUndefinedOrNull), U8(86),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Mov), R(context), R(15),
|
2017-11-07 09:26:56 +00:00
|
|
|
B(TestTypeOf), U8(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfTrue), U8(18),
|
2020-04-24 18:21:45 +00:00
|
|
|
B(Wide), B(LdaSmi), I16(159),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(16),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaConstant), U8(9),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(17),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kNewTypeError), R(16), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Throw),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallProperty0), R(14), R(6), U8(19),
|
|
|
|
|
B(Star), R(17),
|
|
|
|
|
B(Mov), R(0), R(16),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionAwaitUncaught), R(16), U8(2),
|
|
|
|
|
B(SuspendGenerator), R(0), R(0), U8(16), U8(1),
|
|
|
|
|
B(ResumeGenerator), R(0), R(0), U8(16),
|
|
|
|
|
B(Star), R(16),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_GeneratorGetResumeMode), R(0), U8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(17),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(17),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(16),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(16),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(21),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(18),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(18), U8(1),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Jump), U8(12),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(15),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(8),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(15),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(10),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(SetPendingMessage),
|
2017-05-16 15:20:09 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(8),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfFalse), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(9),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(ReThrow),
|
|
|
|
|
B(LdaUndefined),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(6),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
B(LdaTrue),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(7),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Mov), R(0), R(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionResolve), R(5), U8(3),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
/* 57 S> */ B(Return),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(5),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(CreateCatchContext), R(5), U8(10),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(4),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
|
|
|
|
B(SetPendingMessage),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Ldar), R(4),
|
|
|
|
|
B(PushContext), R(5),
|
Reland x3 "[runtime] Remove extension slots from context objects"
Original change's description:
> [runtime] Remove extension slots from context objects
>
> Context objects have an extension slot, which contains further
> additional data that depends on the type of the context.
>
> This CL removes the extension slot from contexts that don't need
> them, hence reducing memory.
>
> The following contexts will still have an extension slot: native,
> module, await, block and with contexts. See objects/contexts.h for
> what the slot is used for.
> The following contexts will not have an extension slot anymore (they
> were not used before): script, catch and builtin contexts.
> Eval and function contexts only have the extension slot if they
> contain a sloppy eval.
>
> Bug: v8:9744
> Change-Id: I8ca56c22fa02437bbac392ea72174ebfca80e030
> Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1863191
> Commit-Queue: Victor Gomes <victorgomes@google.com>
> Reviewed-by: Toon Verwaest <verwaest@chromium.org>
> Reviewed-by: Jakob Gruber <jgruber@chromium.org>
> Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
> Reviewed-by: Leszek Swirski <leszeks@chromium.org>
> Reviewed-by: Peter Marshall <petermarshall@chromium.org>
> Auto-Submit: Victor Gomes <victorgomes@google.com>
> Cr-Commit-Position: refs/heads/master@{#64372}
TBR=verwaest@chromium.org,jgruber@chromium.org,ulan@chromium.org,leszeks@chromium.org,petermarshall@chromium.org
Bug: v8:9744
Change-Id: I8700ed2fa62c89e86c39bb16ac3167f38ea8d63f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1873695
Commit-Queue: Victor Gomes <victorgomes@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64477}
2019-10-22 12:59:24 +00:00
|
|
|
B(LdaImmutableCurrentContextSlot), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(7),
|
2018-05-30 14:21:39 +00:00
|
|
|
B(LdaTrue),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Mov), R(0), R(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionReject), R(6), U8(3),
|
2017-02-24 17:48:49 +00:00
|
|
|
/* 57 S> */ B(Return),
|
|
|
|
|
]
|
|
|
|
|
constant pool: [
|
[interpreter] Move function-entry stack check to start of bytecode array
The function-entry stack check should dominate all other
instructions in a function. Prior to this CL it was possible to create
paths not including a stack check due to SwitchOnGeneratorState: the
generator-creation branch had a stack check, while generator-resume
branches did not.
0 : af fb 00 01 SwitchOnGeneratorState r0, [0], [1] { 0: @22 }
4 : 27 fe fa Mov <closure>, r1
7 : 27 02 f9 Mov <this>, r2
10 : 64 0a fa 02 InvokeIntrinsic [_CreateJSGeneratorObject], r1-r2
14 : 26 fb Star r0
16 : a7 StackCheck
17 : b0 fb fb 01 00 SuspendGenerator r0, r0-r0, [0]
22 : b1 fb fb 01 ResumeGenerator r0, r0-r0
[... no stack check here ...]
This CL moves the stack check to the beginning of the bytecode array,
i.e. before SwitchOnGeneratorState.
Bug: chromium:1020031
Change-Id: I8ba8cba99611ddbe50c76023129d926cc84b1d5e
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1903440
Reviewed-by: Georg Neis <neis@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64888}
2019-11-11 13:34:07 +00:00
|
|
|
Smi [95],
|
2020-03-20 11:13:04 +00:00
|
|
|
Smi [223],
|
2018-07-05 18:34:09 +00:00
|
|
|
ARRAY_BOILERPLATE_DESCRIPTION_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
SYMBOL_TYPE,
|
2019-09-06 12:41:00 +00:00
|
|
|
SYMBOL_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["next"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["done"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["value"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["return"],
|
2019-04-18 09:29:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE [""],
|
2018-02-16 12:36:47 +00:00
|
|
|
SCOPE_INFO_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
handlers: [
|
2020-03-20 11:13:04 +00:00
|
|
|
[19, 291, 291],
|
|
|
|
|
[74, 153, 161],
|
|
|
|
|
[185, 254, 256],
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
snippet: "
|
|
|
|
|
async function f() {
|
|
|
|
|
for await (let x of [1, 2, 3]) { return x; }
|
|
|
|
|
}
|
|
|
|
|
f();
|
|
|
|
|
"
|
2019-08-23 14:23:52 +00:00
|
|
|
frame size: 19
|
2017-02-24 17:48:49 +00:00
|
|
|
parameter count: 1
|
2020-03-11 15:07:16 +00:00
|
|
|
bytecode array length: 340
|
2017-02-24 17:48:49 +00:00
|
|
|
bytecodes: [
|
2019-01-31 15:36:58 +00:00
|
|
|
B(SwitchOnGeneratorState), R(0), U8(0), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(closure), R(4),
|
|
|
|
|
B(Mov), R(this), R(5),
|
2020-02-10 16:09:27 +00:00
|
|
|
/* 16 E> */ B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionEnter), R(4), U8(2),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Star), R(0),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(context), R(4),
|
|
|
|
|
/* 43 S> */ B(CreateArrayLiteral), U8(2), U8(0), U8(37),
|
2018-10-11 08:35:56 +00:00
|
|
|
B(Star), R(7),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaNamedProperty), R(7), U8(3), U8(1),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfUndefinedOrNull), U8(15),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
|
|
|
|
B(CallProperty0), R(8), R(7), U8(3),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(JumpIfJSReceiver), U8(23),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(CallRuntime), U16(Runtime::kThrowSymbolAsyncIteratorInvalid), R(0), U8(0),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(7), U8(4), U8(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
|
|
|
|
B(CallProperty0), R(8), R(7), U8(7),
|
|
|
|
|
B(Star), R(8),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_CreateAsyncFromSyncIterator), R(8), U8(1),
|
|
|
|
|
B(Star), R(6),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(6), U8(5), U8(9),
|
2018-01-11 17:24:11 +00:00
|
|
|
B(Star), R(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
|
|
|
|
B(Mov), R(context), R(10),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaTrue),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
2019-01-14 14:15:52 +00:00
|
|
|
/* 38 S> */ B(CallProperty0), R(5), R(6), U8(11),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
|
|
|
|
B(Mov), R(0), R(12),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionAwaitUncaught), R(12), U8(2),
|
|
|
|
|
B(SuspendGenerator), R(0), R(0), U8(12), U8(0),
|
|
|
|
|
B(ResumeGenerator), R(0), R(0), U8(12),
|
|
|
|
|
B(Star), R(12),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_GeneratorGetResumeMode), R(0), U8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
2017-05-24 15:48:27 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(13),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(12),
|
Reland "[async-iteration] implement spec-change to `yield` in async generators"
Per https://github.com/tc39/proposal-async-iteration/pull/102/files:
AsyncGeneratorResolve no longer unwraps a value component. Instead, the value is
unwrapped before the builtin call via Await, allowing Promise rejections to
affect the generator control flow.
Thus, all `yield <expr>` implicitly become `yield await <expr>`.
Additionally, `return <expr>` becomes `return await <expr>`. Finally, when the
generator is resumed with `.return()`, the parameter passed to .return() is
awaited before generator execution properly continues).
BUG=v8:6187, v8:5855
R=littledan@chromium.org, neis@chromium.org, adamk@chromium.org
TBR=rmcilroy@chromium.org, neis@chromium.org
Cq-Include-Trybots: master.tryserver.v8:v8_linux_noi18n_rel_ng
Change-Id: Id7718028fd555481f9f4ca0dbecfa788e3057c48
Reviewed-on: https://chromium-review.googlesource.com/594500
Reviewed-by: Caitlin Potter <caitp@igalia.com>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Caitlin Potter <caitp@igalia.com>
Cr-Commit-Position: refs/heads/master@{#47058}
2017-08-01 14:45:03 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(12),
|
|
|
|
|
B(Mov), R(12), R(11),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(11), U8(1),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(11), U8(6), U8(13),
|
2020-03-11 15:07:16 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(26),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(11), U8(7), U8(15),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(11),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
|
|
|
|
B(Mov), R(11), R(1),
|
2019-01-31 15:36:58 +00:00
|
|
|
/* 38 S> */ B(Mov), R(1), R(3),
|
2019-01-02 16:12:54 +00:00
|
|
|
/* 56 S> */ B(LdaSmi), I8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Mov), R(11), R(9),
|
|
|
|
|
B(Star), R(8),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Jump), U8(15),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaSmi), I8(-1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(9),
|
|
|
|
|
B(Star), R(8),
|
2019-01-02 16:12:54 +00:00
|
|
|
B(Jump), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(9),
|
2019-01-02 16:12:54 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(8),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
|
|
|
|
B(SetPendingMessage),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(10),
|
|
|
|
|
B(Ldar), R(7),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(94),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(6), U8(8), U8(17),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(14),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfUndefinedOrNull), U8(86),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Mov), R(context), R(15),
|
2017-11-07 09:26:56 +00:00
|
|
|
B(TestTypeOf), U8(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfTrue), U8(18),
|
2020-04-24 18:21:45 +00:00
|
|
|
B(Wide), B(LdaSmi), I16(159),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(16),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaConstant), U8(9),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(17),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kNewTypeError), R(16), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Throw),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallProperty0), R(14), R(6), U8(19),
|
|
|
|
|
B(Star), R(17),
|
|
|
|
|
B(Mov), R(0), R(16),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionAwaitUncaught), R(16), U8(2),
|
|
|
|
|
B(SuspendGenerator), R(0), R(0), U8(16), U8(1),
|
|
|
|
|
B(ResumeGenerator), R(0), R(0), U8(16),
|
|
|
|
|
B(Star), R(16),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_GeneratorGetResumeMode), R(0), U8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(17),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(17),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(16),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(16),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(21),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(18),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(18), U8(1),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Jump), U8(12),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(15),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(8),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(15),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(ReThrow),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Ldar), R(10),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(SetPendingMessage),
|
|
|
|
|
B(Ldar), R(8),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(SwitchOnSmiNoFeedback), U8(10), U8(2), I8(0),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
B(Jump), U8(19),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(9),
|
2019-01-02 16:12:54 +00:00
|
|
|
B(ReThrow),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
B(LdaTrue),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(16),
|
|
|
|
|
B(Mov), R(0), R(14),
|
|
|
|
|
B(Mov), R(9), R(15),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionResolve), R(14), U8(3),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
/* 68 S> */ B(Return),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaUndefined),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(6),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
B(LdaTrue),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(7),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Mov), R(0), R(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionResolve), R(5), U8(3),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
/* 68 S> */ B(Return),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(5),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(CreateCatchContext), R(5), U8(12),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(4),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
|
|
|
|
B(SetPendingMessage),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Ldar), R(4),
|
|
|
|
|
B(PushContext), R(5),
|
Reland x3 "[runtime] Remove extension slots from context objects"
Original change's description:
> [runtime] Remove extension slots from context objects
>
> Context objects have an extension slot, which contains further
> additional data that depends on the type of the context.
>
> This CL removes the extension slot from contexts that don't need
> them, hence reducing memory.
>
> The following contexts will still have an extension slot: native,
> module, await, block and with contexts. See objects/contexts.h for
> what the slot is used for.
> The following contexts will not have an extension slot anymore (they
> were not used before): script, catch and builtin contexts.
> Eval and function contexts only have the extension slot if they
> contain a sloppy eval.
>
> Bug: v8:9744
> Change-Id: I8ca56c22fa02437bbac392ea72174ebfca80e030
> Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1863191
> Commit-Queue: Victor Gomes <victorgomes@google.com>
> Reviewed-by: Toon Verwaest <verwaest@chromium.org>
> Reviewed-by: Jakob Gruber <jgruber@chromium.org>
> Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
> Reviewed-by: Leszek Swirski <leszeks@chromium.org>
> Reviewed-by: Peter Marshall <petermarshall@chromium.org>
> Auto-Submit: Victor Gomes <victorgomes@google.com>
> Cr-Commit-Position: refs/heads/master@{#64372}
TBR=verwaest@chromium.org,jgruber@chromium.org,ulan@chromium.org,leszeks@chromium.org,petermarshall@chromium.org
Bug: v8:9744
Change-Id: I8700ed2fa62c89e86c39bb16ac3167f38ea8d63f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1873695
Commit-Queue: Victor Gomes <victorgomes@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64477}
2019-10-22 12:59:24 +00:00
|
|
|
B(LdaImmutableCurrentContextSlot), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(7),
|
2018-05-30 14:21:39 +00:00
|
|
|
B(LdaTrue),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Mov), R(0), R(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionReject), R(6), U8(3),
|
2017-02-24 17:48:49 +00:00
|
|
|
/* 68 S> */ B(Return),
|
|
|
|
|
]
|
|
|
|
|
constant pool: [
|
[interpreter] Move function-entry stack check to start of bytecode array
The function-entry stack check should dominate all other
instructions in a function. Prior to this CL it was possible to create
paths not including a stack check due to SwitchOnGeneratorState: the
generator-creation branch had a stack check, while generator-resume
branches did not.
0 : af fb 00 01 SwitchOnGeneratorState r0, [0], [1] { 0: @22 }
4 : 27 fe fa Mov <closure>, r1
7 : 27 02 f9 Mov <this>, r2
10 : 64 0a fa 02 InvokeIntrinsic [_CreateJSGeneratorObject], r1-r2
14 : 26 fb Star r0
16 : a7 StackCheck
17 : b0 fb fb 01 00 SuspendGenerator r0, r0-r0, [0]
22 : b1 fb fb 01 ResumeGenerator r0, r0-r0
[... no stack check here ...]
This CL moves the stack check to the beginning of the bytecode array,
i.e. before SwitchOnGeneratorState.
Bug: chromium:1020031
Change-Id: I8ba8cba99611ddbe50c76023129d926cc84b1d5e
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1903440
Reviewed-by: Georg Neis <neis@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64888}
2019-11-11 13:34:07 +00:00
|
|
|
Smi [95],
|
2020-03-11 15:07:16 +00:00
|
|
|
Smi [227],
|
2018-07-05 18:34:09 +00:00
|
|
|
ARRAY_BOILERPLATE_DESCRIPTION_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
SYMBOL_TYPE,
|
2019-09-06 12:41:00 +00:00
|
|
|
SYMBOL_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["next"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["done"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["value"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["return"],
|
2019-04-18 09:29:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE [""],
|
2017-05-16 11:36:04 +00:00
|
|
|
Smi [6],
|
2019-01-02 16:12:54 +00:00
|
|
|
Smi [9],
|
2018-02-16 12:36:47 +00:00
|
|
|
SCOPE_INFO_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
handlers: [
|
2020-03-11 15:07:16 +00:00
|
|
|
[19, 312, 312],
|
|
|
|
|
[74, 157, 165],
|
|
|
|
|
[189, 258, 260],
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
snippet: "
|
|
|
|
|
async function f() {
|
|
|
|
|
for await (let x of [10, 20, 30]) {
|
|
|
|
|
if (x == 10) continue;
|
|
|
|
|
if (x == 20) break;
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
f();
|
|
|
|
|
"
|
2019-08-23 14:23:52 +00:00
|
|
|
frame size: 19
|
2017-02-24 17:48:49 +00:00
|
|
|
parameter count: 1
|
2020-03-20 11:13:04 +00:00
|
|
|
bytecode array length: 335
|
2017-02-24 17:48:49 +00:00
|
|
|
bytecodes: [
|
2019-01-31 15:36:58 +00:00
|
|
|
B(SwitchOnGeneratorState), R(0), U8(0), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(closure), R(4),
|
|
|
|
|
B(Mov), R(this), R(5),
|
2020-02-10 16:09:27 +00:00
|
|
|
/* 16 E> */ B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionEnter), R(4), U8(2),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Star), R(0),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(context), R(4),
|
|
|
|
|
/* 43 S> */ B(CreateArrayLiteral), U8(2), U8(0), U8(37),
|
2018-10-11 08:35:56 +00:00
|
|
|
B(Star), R(7),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaNamedProperty), R(7), U8(3), U8(1),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfUndefinedOrNull), U8(15),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
|
|
|
|
B(CallProperty0), R(8), R(7), U8(3),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(JumpIfJSReceiver), U8(23),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(CallRuntime), U16(Runtime::kThrowSymbolAsyncIteratorInvalid), R(0), U8(0),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(7), U8(4), U8(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
|
|
|
|
B(CallProperty0), R(8), R(7), U8(7),
|
|
|
|
|
B(Star), R(8),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_CreateAsyncFromSyncIterator), R(8), U8(1),
|
|
|
|
|
B(Star), R(6),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(6), U8(5), U8(9),
|
2018-01-11 17:24:11 +00:00
|
|
|
B(Star), R(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
|
|
|
|
B(Mov), R(context), R(10),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaTrue),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
2019-01-14 14:15:52 +00:00
|
|
|
/* 38 S> */ B(CallProperty0), R(5), R(6), U8(11),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
|
|
|
|
B(Mov), R(0), R(12),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionAwaitUncaught), R(12), U8(2),
|
|
|
|
|
B(SuspendGenerator), R(0), R(0), U8(12), U8(0),
|
|
|
|
|
B(ResumeGenerator), R(0), R(0), U8(12),
|
|
|
|
|
B(Star), R(12),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_GeneratorGetResumeMode), R(0), U8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
2017-05-24 15:48:27 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(13),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(12),
|
Reland "[async-iteration] implement spec-change to `yield` in async generators"
Per https://github.com/tc39/proposal-async-iteration/pull/102/files:
AsyncGeneratorResolve no longer unwraps a value component. Instead, the value is
unwrapped before the builtin call via Await, allowing Promise rejections to
affect the generator control flow.
Thus, all `yield <expr>` implicitly become `yield await <expr>`.
Additionally, `return <expr>` becomes `return await <expr>`. Finally, when the
generator is resumed with `.return()`, the parameter passed to .return() is
awaited before generator execution properly continues).
BUG=v8:6187, v8:5855
R=littledan@chromium.org, neis@chromium.org, adamk@chromium.org
TBR=rmcilroy@chromium.org, neis@chromium.org
Cq-Include-Trybots: master.tryserver.v8:v8_linux_noi18n_rel_ng
Change-Id: Id7718028fd555481f9f4ca0dbecfa788e3057c48
Reviewed-on: https://chromium-review.googlesource.com/594500
Reviewed-by: Caitlin Potter <caitp@igalia.com>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Commit-Queue: Caitlin Potter <caitp@igalia.com>
Cr-Commit-Position: refs/heads/master@{#47058}
2017-08-01 14:45:03 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(12),
|
|
|
|
|
B(Mov), R(12), R(11),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(11), U8(1),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(11), U8(6), U8(13),
|
2020-03-20 11:13:04 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(38),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(11), U8(7), U8(15),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(11),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
|
|
|
|
B(Mov), R(11), R(1),
|
2019-01-31 15:36:58 +00:00
|
|
|
/* 38 S> */ B(Mov), R(1), R(3),
|
2017-05-24 13:54:57 +00:00
|
|
|
/* 63 S> */ B(LdaSmi), I8(10),
|
2019-01-31 15:36:58 +00:00
|
|
|
/* 69 E> */ B(TestEqual), R(3), U8(17),
|
2017-05-24 13:54:57 +00:00
|
|
|
B(JumpIfFalse), U8(4),
|
2019-01-14 14:15:52 +00:00
|
|
|
/* 76 S> */ B(Jump), U8(11),
|
2017-05-24 13:54:57 +00:00
|
|
|
/* 90 S> */ B(LdaSmi), I8(20),
|
2019-01-31 15:36:58 +00:00
|
|
|
/* 96 E> */ B(TestEqual), R(3), U8(18),
|
2017-05-24 13:54:57 +00:00
|
|
|
B(JumpIfFalse), U8(4),
|
2020-03-20 11:13:04 +00:00
|
|
|
/* 103 S> */ B(Jump), U8(5),
|
|
|
|
|
/* 23 E> */ B(JumpLoop), U8(92), I8(0),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaSmi), I8(-1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(9),
|
|
|
|
|
B(Star), R(8),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(Jump), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(9),
|
2018-10-11 08:35:56 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(8),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
|
|
|
|
B(SetPendingMessage),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(10),
|
|
|
|
|
B(Ldar), R(7),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(94),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaNamedProperty), R(6), U8(8), U8(19),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(14),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfUndefinedOrNull), U8(86),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Mov), R(context), R(15),
|
2017-11-07 09:26:56 +00:00
|
|
|
B(TestTypeOf), U8(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfTrue), U8(18),
|
2020-04-24 18:21:45 +00:00
|
|
|
B(Wide), B(LdaSmi), I16(159),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(16),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(LdaConstant), U8(9),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(17),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kNewTypeError), R(16), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Throw),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallProperty0), R(14), R(6), U8(21),
|
|
|
|
|
B(Star), R(17),
|
|
|
|
|
B(Mov), R(0), R(16),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionAwaitUncaught), R(16), U8(2),
|
|
|
|
|
B(SuspendGenerator), R(0), R(0), U8(16), U8(1),
|
|
|
|
|
B(ResumeGenerator), R(0), R(0), U8(16),
|
|
|
|
|
B(Star), R(16),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_GeneratorGetResumeMode), R(0), U8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(17),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(17),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(16),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(16),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(21),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(18),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(18), U8(1),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Jump), U8(12),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(15),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(8),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(15),
|
2018-01-23 13:51:38 +00:00
|
|
|
B(ReThrow),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(10),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(SetPendingMessage),
|
2017-05-16 15:20:09 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(8),
|
2017-07-13 13:53:13 +00:00
|
|
|
B(JumpIfFalse), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(9),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(ReThrow),
|
|
|
|
|
B(LdaUndefined),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(6),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
B(LdaTrue),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(7),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Mov), R(0), R(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionResolve), R(5), U8(3),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
/* 114 S> */ B(Return),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(5),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(CreateCatchContext), R(5), U8(10),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(4),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
|
|
|
|
B(SetPendingMessage),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Ldar), R(4),
|
|
|
|
|
B(PushContext), R(5),
|
Reland x3 "[runtime] Remove extension slots from context objects"
Original change's description:
> [runtime] Remove extension slots from context objects
>
> Context objects have an extension slot, which contains further
> additional data that depends on the type of the context.
>
> This CL removes the extension slot from contexts that don't need
> them, hence reducing memory.
>
> The following contexts will still have an extension slot: native,
> module, await, block and with contexts. See objects/contexts.h for
> what the slot is used for.
> The following contexts will not have an extension slot anymore (they
> were not used before): script, catch and builtin contexts.
> Eval and function contexts only have the extension slot if they
> contain a sloppy eval.
>
> Bug: v8:9744
> Change-Id: I8ca56c22fa02437bbac392ea72174ebfca80e030
> Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1863191
> Commit-Queue: Victor Gomes <victorgomes@google.com>
> Reviewed-by: Toon Verwaest <verwaest@chromium.org>
> Reviewed-by: Jakob Gruber <jgruber@chromium.org>
> Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
> Reviewed-by: Leszek Swirski <leszeks@chromium.org>
> Reviewed-by: Peter Marshall <petermarshall@chromium.org>
> Auto-Submit: Victor Gomes <victorgomes@google.com>
> Cr-Commit-Position: refs/heads/master@{#64372}
TBR=verwaest@chromium.org,jgruber@chromium.org,ulan@chromium.org,leszeks@chromium.org,petermarshall@chromium.org
Bug: v8:9744
Change-Id: I8700ed2fa62c89e86c39bb16ac3167f38ea8d63f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1873695
Commit-Queue: Victor Gomes <victorgomes@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64477}
2019-10-22 12:59:24 +00:00
|
|
|
B(LdaImmutableCurrentContextSlot), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(7),
|
2018-05-30 14:21:39 +00:00
|
|
|
B(LdaTrue),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(8),
|
2019-01-31 15:36:58 +00:00
|
|
|
B(Mov), R(0), R(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionReject), R(6), U8(3),
|
2017-02-24 17:48:49 +00:00
|
|
|
/* 114 S> */ B(Return),
|
|
|
|
|
]
|
|
|
|
|
constant pool: [
|
[interpreter] Move function-entry stack check to start of bytecode array
The function-entry stack check should dominate all other
instructions in a function. Prior to this CL it was possible to create
paths not including a stack check due to SwitchOnGeneratorState: the
generator-creation branch had a stack check, while generator-resume
branches did not.
0 : af fb 00 01 SwitchOnGeneratorState r0, [0], [1] { 0: @22 }
4 : 27 fe fa Mov <closure>, r1
7 : 27 02 f9 Mov <this>, r2
10 : 64 0a fa 02 InvokeIntrinsic [_CreateJSGeneratorObject], r1-r2
14 : 26 fb Star r0
16 : a7 StackCheck
17 : b0 fb fb 01 00 SuspendGenerator r0, r0-r0, [0]
22 : b1 fb fb 01 ResumeGenerator r0, r0-r0
[... no stack check here ...]
This CL moves the stack check to the beginning of the bytecode array,
i.e. before SwitchOnGeneratorState.
Bug: chromium:1020031
Change-Id: I8ba8cba99611ddbe50c76023129d926cc84b1d5e
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1903440
Reviewed-by: Georg Neis <neis@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64888}
2019-11-11 13:34:07 +00:00
|
|
|
Smi [95],
|
2020-03-20 11:13:04 +00:00
|
|
|
Smi [239],
|
2018-07-05 18:34:09 +00:00
|
|
|
ARRAY_BOILERPLATE_DESCRIPTION_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
SYMBOL_TYPE,
|
2019-09-06 12:41:00 +00:00
|
|
|
SYMBOL_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["next"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["done"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["value"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["return"],
|
2019-04-18 09:29:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE [""],
|
2018-02-16 12:36:47 +00:00
|
|
|
SCOPE_INFO_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
handlers: [
|
2020-03-20 11:13:04 +00:00
|
|
|
[19, 307, 307],
|
|
|
|
|
[74, 169, 177],
|
|
|
|
|
[201, 270, 272],
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
snippet: "
|
|
|
|
|
async function f() {
|
|
|
|
|
var x = { 'a': 1, 'b': 2 };
|
|
|
|
|
for (x['a'] of [1,2,3]) { return x['a']; }
|
|
|
|
|
}
|
|
|
|
|
f();
|
|
|
|
|
"
|
2019-08-23 14:23:52 +00:00
|
|
|
frame size: 15
|
2017-02-24 17:48:49 +00:00
|
|
|
parameter count: 1
|
2020-03-11 15:07:16 +00:00
|
|
|
bytecode array length: 251
|
2017-02-24 17:48:49 +00:00
|
|
|
bytecodes: [
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(closure), R(2),
|
|
|
|
|
B(Mov), R(this), R(3),
|
2020-02-10 16:09:27 +00:00
|
|
|
/* 16 E> */ B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionEnter), R(2), U8(2),
|
2018-10-04 07:19:45 +00:00
|
|
|
B(Star), R(0),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Mov), R(context), R(2),
|
2018-11-08 08:55:43 +00:00
|
|
|
/* 31 S> */ B(CreateObjectLiteral), U8(0), U8(0), U8(41),
|
|
|
|
|
B(Star), R(1),
|
2017-07-27 12:45:00 +00:00
|
|
|
/* 68 S> */ B(CreateArrayLiteral), U8(1), U8(1), U8(37),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(5),
|
2019-09-06 12:41:00 +00:00
|
|
|
B(GetIterator), R(5), U8(2), U8(4),
|
2019-12-20 14:06:40 +00:00
|
|
|
B(JumpIfJSReceiver), U8(7),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kThrowSymbolIteratorInvalid), R(0), U8(0),
|
2018-01-11 17:24:11 +00:00
|
|
|
B(Star), R(4),
|
2019-08-08 20:43:41 +00:00
|
|
|
B(LdaNamedProperty), R(4), U8(2), U8(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(3),
|
|
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(5),
|
|
|
|
|
B(Mov), R(context), R(8),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaTrue),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(5),
|
2019-01-14 14:15:52 +00:00
|
|
|
/* 59 S> */ B(CallProperty0), R(3), R(4), U8(8),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(9),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(9), U8(1),
|
|
|
|
|
B(LdaNamedProperty), R(9), U8(3), U8(10),
|
2020-03-11 15:07:16 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(32),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(LdaNamedProperty), R(9), U8(4), U8(12),
|
|
|
|
|
B(Star), R(9),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(5),
|
|
|
|
|
B(Ldar), R(9),
|
2019-08-08 20:43:41 +00:00
|
|
|
/* 58 E> */ B(StaNamedProperty), R(1), U8(5), U8(14),
|
|
|
|
|
/* 87 S> */ B(LdaNamedProperty), R(1), U8(5), U8(16),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaSmi), I8(1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(6),
|
|
|
|
|
B(Mov), R(1), R(10),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Jump), U8(15),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaSmi), I8(-1),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
|
|
|
|
B(Star), R(6),
|
2019-01-02 16:12:54 +00:00
|
|
|
B(Jump), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(7),
|
2019-01-02 16:12:54 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(6),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
|
|
|
|
B(SetPendingMessage),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(8),
|
|
|
|
|
B(Ldar), R(5),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfToBooleanTrue), U8(58),
|
2019-08-08 20:43:41 +00:00
|
|
|
B(LdaNamedProperty), R(4), U8(6), U8(18),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(11),
|
2019-08-08 15:56:48 +00:00
|
|
|
B(JumpIfUndefinedOrNull), U8(50),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Mov), R(context), R(12),
|
2017-11-07 09:26:56 +00:00
|
|
|
B(TestTypeOf), U8(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfTrue), U8(18),
|
2020-04-24 18:21:45 +00:00
|
|
|
B(Wide), B(LdaSmi), I16(159),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
2019-08-08 20:43:41 +00:00
|
|
|
B(LdaConstant), U8(7),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(14),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kNewTypeError), R(13), U8(2),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(Throw),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(CallProperty0), R(11), R(4), U8(20),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfJSReceiver), U8(21),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
|
|
|
|
B(CallRuntime), U16(Runtime::kThrowIteratorResultNotAnObject), R(13), U8(1),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Jump), U8(12),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(12),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(LdaZero),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(TestReferenceEqual), R(6),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(JumpIfTrue), U8(5),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(12),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(ReThrow),
|
|
|
|
|
B(Ldar), R(8),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(SetPendingMessage),
|
|
|
|
|
B(Ldar), R(6),
|
2019-08-08 20:43:41 +00:00
|
|
|
B(SwitchOnSmiNoFeedback), U8(8), U8(2), I8(0),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
B(Jump), U8(19),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Ldar), R(7),
|
2019-01-02 16:12:54 +00:00
|
|
|
B(ReThrow),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
B(LdaFalse),
|
2019-08-23 14:23:52 +00:00
|
|
|
B(Star), R(13),
|
|
|
|
|
B(Mov), R(0), R(11),
|
|
|
|
|
B(Mov), R(7), R(12),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionResolve), R(11), U8(3),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
/* 96 S> */ B(Return),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaUndefined),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(4),
|
2018-01-11 17:24:11 +00:00
|
|
|
B(LdaFalse),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(5),
|
|
|
|
|
B(Mov), R(0), R(3),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionResolve), R(3), U8(3),
|
[async] Improve async function handling.
This change introduces new intrinsics used to desugar async functions
in the Parser and the BytecodeGenerator, namely we introduce a new
%_AsyncFunctionEnter intrinsic that constructs the generator object
for the async function (and in the future will also create the outer
promise for the async function). This generator object is internal
and never escapes to user code, plus since async functions don't have
a "prototype" property, we can just a single map here instead of tracking
the prototype/initial_map on every async function. This saves one word
per async function plus one initial_map per async function that was
invoked at least once.
We also introduce two new intrinsics %_AsyncFunctionReject, which
rejects the outer promise with the caught exception, and another
%_AsyncFunctionResolve, which resolves the outer promise with the
right hand side of the `return` statement. These functions also perform
the DevTools part of the job (aka popping from the promise stack and
sending the debug event). This allows us to get rid of the implicit
try-finally from async functions completely; because the finally
block only called to the %AsyncFunctionPromiseRelease builtin, which
was used to inform DevTools.
In essence we now turn an async function like
```js
async function f(x) { return await bar(x); }
```
into something like this (in Parser and BytecodeGenerator respectively):
```
function f(x) {
.generator_object = %_AsyncFunctionEnter(.closure, this);
.promise = %AsyncFunctionCreatePromise();
try {
.tmp = await bar(x);
return %_AsyncFunctionResolve(.promise, .tmp);
} catch (e) {
return %_AsyncFunctionReject(.promise, e);
}
}
```
Overall the bytecode for async functions gets significantly shorter
already (and will get even shorter once we put the outer promise into
the async function generator object). For example the bytecode for a
simple async function
```js
async function f(x) { return await x; }
```
goes from 175 bytes to 110 bytes (a ~38% reduction in size), which
is in particular due to the simplification around the try-finally
removal.
Overall this seems to improve the doxbee-async-es2017-native test by
around 2-3%. On the test case mentioned in v8:8276 we go from
1124ms to 441ms, which corresponds to a 60% reduction in total
execution time!
Tbr: marja@chromium.org
Bug: v8:7253, v8:7522, v8:8276
Cq-Include-Trybots: luci.chromium.try:linux_chromium_headless_rel;luci.chromium.try:linux_chromium_rel_ng;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id29dc92de7490b387ff697860c900cee44c9a7a4
Reviewed-on: https://chromium-review.googlesource.com/c/1269041
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org>
Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Reviewed-by: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56502}
2018-10-10 05:54:39 +00:00
|
|
|
/* 96 S> */ B(Return),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(3),
|
2019-08-08 20:43:41 +00:00
|
|
|
B(CreateCatchContext), R(3), U8(10),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(2),
|
2017-02-24 17:48:49 +00:00
|
|
|
B(LdaTheHole),
|
|
|
|
|
B(SetPendingMessage),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Ldar), R(2),
|
|
|
|
|
B(PushContext), R(3),
|
Reland x3 "[runtime] Remove extension slots from context objects"
Original change's description:
> [runtime] Remove extension slots from context objects
>
> Context objects have an extension slot, which contains further
> additional data that depends on the type of the context.
>
> This CL removes the extension slot from contexts that don't need
> them, hence reducing memory.
>
> The following contexts will still have an extension slot: native,
> module, await, block and with contexts. See objects/contexts.h for
> what the slot is used for.
> The following contexts will not have an extension slot anymore (they
> were not used before): script, catch and builtin contexts.
> Eval and function contexts only have the extension slot if they
> contain a sloppy eval.
>
> Bug: v8:9744
> Change-Id: I8ca56c22fa02437bbac392ea72174ebfca80e030
> Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1863191
> Commit-Queue: Victor Gomes <victorgomes@google.com>
> Reviewed-by: Toon Verwaest <verwaest@chromium.org>
> Reviewed-by: Jakob Gruber <jgruber@chromium.org>
> Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
> Reviewed-by: Leszek Swirski <leszeks@chromium.org>
> Reviewed-by: Peter Marshall <petermarshall@chromium.org>
> Auto-Submit: Victor Gomes <victorgomes@google.com>
> Cr-Commit-Position: refs/heads/master@{#64372}
TBR=verwaest@chromium.org,jgruber@chromium.org,ulan@chromium.org,leszeks@chromium.org,petermarshall@chromium.org
Bug: v8:9744
Change-Id: I8700ed2fa62c89e86c39bb16ac3167f38ea8d63f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1873695
Commit-Queue: Victor Gomes <victorgomes@chromium.org>
Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64477}
2019-10-22 12:59:24 +00:00
|
|
|
B(LdaImmutableCurrentContextSlot), U8(2),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(5),
|
2018-05-30 14:21:39 +00:00
|
|
|
B(LdaFalse),
|
2019-01-14 14:15:52 +00:00
|
|
|
B(Star), R(6),
|
|
|
|
|
B(Mov), R(0), R(4),
|
|
|
|
|
B(InvokeIntrinsic), U8(Runtime::k_AsyncFunctionReject), R(4), U8(3),
|
2017-02-24 17:48:49 +00:00
|
|
|
/* 96 S> */ B(Return),
|
|
|
|
|
]
|
|
|
|
|
constant pool: [
|
2018-07-05 18:34:09 +00:00
|
|
|
OBJECT_BOILERPLATE_DESCRIPTION_TYPE,
|
|
|
|
|
ARRAY_BOILERPLATE_DESCRIPTION_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["next"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["done"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["value"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["a"],
|
|
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE ["return"],
|
2019-04-18 09:29:49 +00:00
|
|
|
ONE_BYTE_INTERNALIZED_STRING_TYPE [""],
|
2017-05-16 11:36:04 +00:00
|
|
|
Smi [6],
|
2019-01-02 16:12:54 +00:00
|
|
|
Smi [9],
|
2018-02-16 12:36:47 +00:00
|
|
|
SCOPE_INFO_TYPE,
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
handlers: [
|
2020-03-11 15:07:16 +00:00
|
|
|
[15, 223, 223],
|
|
|
|
|
[52, 104, 112],
|
|
|
|
|
[136, 169, 171],
|
2017-02-24 17:48:49 +00:00
|
|
|
]
|
|
|
|
|
|
