- 19 Feb, 2018 28 commits
-
-
Caitlin Potter authored
Previously, eval caching was only disabled if the root eval body code contained a tagged template. Per discussion on https://github.com/tc39/ecma262/pull/890, this is incorrect. This change tracks if eval caching is allowed during parsing, and uses this information to decide to insert new entries into the cache, or not. This change also removes the TemplateObject feedback kind, as it's no longer needed (behaves the same as Literal feedback). BUG=v8:3230, v8:2891 R=littledan@chromium.org, yangguo@chromium.org, bmeurer@chromium.org, rmcilroy@chromium.org Change-Id: Ib75abe9159baf4d8ad10f8de99d2152714bd0094 Reviewed-on: https://chromium-review.googlesource.com/916945 Commit-Queue: Caitlin Potter <caitp@igalia.com> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#51373}
-
Gabriel Charette authored
Reland reason : not the culprit. This will let us identify in traces whether unwinding after receiving the preemption event is slower than desired and should be optimized. Adding it to pausing while working on removing it in https://chromium-review.googlesource.com/c/v8/v8/+/922103 will allow gathering traces that highlight the issue. R=ulan@chromium.org Bug: chromium:812178 Change-Id: I0dc0f6754980157674968ba4a868f12c779e69bc Reviewed-on: https://chromium-review.googlesource.com/923989Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#51372}
-
Gabriel Charette authored
This is a reland of f4b41099. Not expected to be the culprit of the 4 CL revert. Original change's description: > Introduce ConcurrentMarking::StopRequest API. > > This was extracted from https://chromium-review.googlesource.com/c/v8/v8/+/924073/10 > after it became clear that using COMPLETE_TASKS/PREEMPT_TASKS where > it should make sense to doesn't work in practice for now. > > Experimental CLs which led to the above conclusion: > - https://chromium-review.googlesource.com/c/v8/v8/+/924865 > (COMPLETE or CANCEL -- still broken) > - https://chromium-review.googlesource.com/c/v8/v8/+/924866 > (CANCEL only, as before, works) > - https://chromium-review.googlesource.com/c/v8/v8/+/924028 > (CANCEL and PREEMPT -- broken as well) > > Introducing this unittested API allows to reduce the size > of the CLs causing hard-to-diagnose bots-only failures > and fix them individually follow-ups @ > > 1) https://chromium-review.googlesource.com/c/v8/v8/+/924029 > 2) https://chromium-review.googlesource.com/c/v8/v8/+/924031 > 3) https://chromium-review.googlesource.com/c/v8/v8/+/924030 > > Bug: chromium:812178 > Change-Id: Icdac456e9f7874b0c4b321ccdb8898297dad7d73 > Reviewed-on: https://chromium-review.googlesource.com/924867 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51353} Bug: chromium:812178 Change-Id: Iaa32f9cc6b2fa7004c7fae1f79aa4b00f5f8f34c Reviewed-on: https://chromium-review.googlesource.com/924006Reviewed-by:
-
Clemens Hammacher authored
There is a debug check to check that an embedded code object is patched correctly. This check only makes sense if the code object was indeed pushed to the stack, otherwise we are checking the type marker. This CL fixes this check and adds a line of documentation. R=mstarzinger@chromium.org Change-Id: I5bc1454232cdbf2e9fef6eb41f7c7a20f31a5250 Reviewed-on: https://chromium-review.googlesource.com/924154 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#51370}
-
Michael Starzinger authored
R=clemensh@chromium.org BUG=v8:7456 Change-Id: I5b7c151d375267a6a8a24c611b8a13fe38619656 Reviewed-on: https://chromium-review.googlesource.com/924036Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#51369}
-
Clemens Hammacher authored
This implements the br_table instruction in LiftoffCompiler by emitting a binary search tree. R=titzer@chromium.org Bug: v8:6600 Change-Id: I89c11501dd3a41556d2fab68af1afbe8c4855d36 Reviewed-on: https://chromium-review.googlesource.com/921641 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#51368}
-
Stephan Herhut authored
Set the VMA address for jitted code to the address of the code. This should be the correct value, as the code got loaded to that address at runtime. Change-Id: I6ce9181d940dd4568d93a92e98d206f3c6546ebc Reviewed-on: https://chromium-review.googlesource.com/915923Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Stephan Herhut <herhut@chromium.org> Cr-Commit-Position: refs/heads/master@{#51367}
-
sreten.kovacevic authored
Since these instructions will be used in liftoff as well as they are used in code generator, they are transfered to macro assembler. Change-Id: I48e60ccc7586252374bc66b7b72bbe23c2d0c0a6 Reviewed-on: https://chromium-review.googlesource.com/924194Reviewed-by:
Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Commit-Queue: Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Cr-Commit-Position: refs/heads/master@{#51366}
-
Clemens Hammacher authored
This reverts commit f4b41099. Reason for revert: Several GC failures, e.g. https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/23236, https://build.chromium.org/p/client.v8/builders/V8%20Mac/builds/18390 Original change's description: > Introduce ConcurrentMarking::StopRequest API. > > This was extracted from https://chromium-review.googlesource.com/c/v8/v8/+/924073/10 > after it became clear that using COMPLETE_TASKS/PREEMPT_TASKS where > it should make sense to doesn't work in practice for now. > > Experimental CLs which led to the above conclusion: > - https://chromium-review.googlesource.com/c/v8/v8/+/924865 > (COMPLETE or CANCEL -- still broken) > - https://chromium-review.googlesource.com/c/v8/v8/+/924866 > (CANCEL only, as before, works) > - https://chromium-review.googlesource.com/c/v8/v8/+/924028 > (CANCEL and PREEMPT -- broken as well) > > Introducing this unittested API allows to reduce the size > of the CLs causing hard-to-diagnose bots-only failures > and fix them individually follow-ups @ > > 1) https://chromium-review.googlesource.com/c/v8/v8/+/924029 > 2) https://chromium-review.googlesource.com/c/v8/v8/+/924031 > 3) https://chromium-review.googlesource.com/c/v8/v8/+/924030 > > Bug: chromium:812178 > Change-Id: Icdac456e9f7874b0c4b321ccdb8898297dad7d73 > Reviewed-on: https://chromium-review.googlesource.com/924867 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51353} TBR=gab@chromium.org,ulan@chromium.org,mlippautz@chromium.org Change-Id: Ia001cc81c6a7bc030b54d3aa9b9bcecc833300e6 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:812178 Reviewed-on: https://chromium-review.googlesource.com/925302Reviewed-by:
-
Clemens Hammacher authored
This reverts commit 4b49f844. Reason for revert: Several GC failures, e.g. https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/23236, https://build.chromium.org/p/client.v8/builders/V8%20Mac/builds/18390 Original change's description: > Add a trace event when pausing/preempting concurrent marking. > > This will let us identify in traces whether unwinding after receiving > the preemption event is slower than desired and should be optimized. > > Adding it to pausing while working on removing it in > https://chromium-review.googlesource.com/c/v8/v8/+/922103 > will allow gathering traces that highlight the issue. > > R=mlippautz@chromium.org > > Bug: chromium:812178 > Change-Id: I0555c6825e0792769c9ae2d748d7cc35df4f6fed > Reviewed-on: https://chromium-review.googlesource.com/924122 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51354} TBR=gab@chromium.org,mlippautz@chromium.org Change-Id: I37a82e488de51d5ae4d7ed795b82ea9649c4a5f9 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:812178 Reviewed-on: https://chromium-review.googlesource.com/924426Reviewed-by:
-
Clemens Hammacher authored
This reverts commit e9750cb8. Reason for revert: Several GC failures, e.g. https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/23236, https://build.chromium.org/p/client.v8/builders/V8%20Mac/builds/18390 Original change's description: > Preempt ConcurrentMarking tasks instead of merely pausing in PauseScope. > > Follow-up to https://chromium-review.googlesource.com/c/v8/v8/+/924867 > > This is the core goal of the initial CL @ > https://chromium-review.googlesource.com/c/v8/v8/+/922103 > which was since split into multiple to diagnose a bots-only failure. > > Bug: chromium:812178 > Change-Id: I4c4e0b517737e020862917bd89fa6ce38244e597 > Reviewed-on: https://chromium-review.googlesource.com/924031 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Reviewed-by: Michael Lippautz <mlippautz@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51356} TBR=gab@chromium.org,ulan@chromium.org,mlippautz@chromium.org Change-Id: Ic095e32708e58acbe5955bf29e65af34c59d321e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:812178 Reviewed-on: https://chromium-review.googlesource.com/925301Reviewed-by:
-
Clemens Hammacher authored
This reverts commit 8b53b9d9. Reason for revert: Several GC failures, e.g. https://build.chromium.org/p/client.v8/builders/V8%20Linux/builds/23236, https://build.chromium.org/p/client.v8/builders/V8%20Mac/builds/18390 Original change's description: > Preempt ConcurrentMarking tasks ASAP when cancelling marking. > > Follow-up to https://chromium-review.googlesource.com/c/v8/v8/+/924867 > > Bug: chromium:812178 > Change-Id: I2abe28c6e953df42cffdcbd7ea35df9d29849905 > Reviewed-on: https://chromium-review.googlesource.com/924030 > Commit-Queue: Gabriel Charette <gab@chromium.org> > Reviewed-by: Ulan Degenbaev <ulan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51357} TBR=gab@chromium.org,ulan@chromium.org,mlippautz@chromium.org Change-Id: Ic4e226fdd02d8259244cef46e9923c95e6606cc4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:812178 Reviewed-on: https://chromium-review.googlesource.com/924425Reviewed-by:
-
Benedikt Meurer authored
This extends the previously introduced logic for implementing await without having to allocate the throwaway promise and the additional closures and context, to also cover await and yield inside of async generators. Bug: v8:7253 Change-Id: I011583a7714bbd148c54e5f204e2076630008db0 Reviewed-on: https://chromium-review.googlesource.com/924003 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#51361}
-
Ulan Degenbaev authored
Bug: chromium:811842 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: I72163abf0b20b123fb541fe0a1b168e036ef044e Reviewed-on: https://chromium-review.googlesource.com/919063 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#51360}
-
Peter Marshall authored
Change-Id: Id616646bbeebe91e3e575d40799f01611a57643f Reviewed-on: https://chromium-review.googlesource.com/924281Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#51359}
-
Ulan Degenbaev authored
This adds PersistentBase::AnnotateStrongRetainer(const char*) function. The annotation is used by the heap snapshot generator to show the edges from the (Global handles) root to the global handles. Bug: chromium:811842 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I1a9e3e53a53aeaf2b590709fab8dd4ecf7e8f252 Reviewed-on: https://chromium-review.googlesource.com/916788 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Gabriel Charette authored
Follow-up to https://chromium-review.googlesource.com/c/v8/v8/+/924867 Bug: chromium:812178 Change-Id: I2abe28c6e953df42cffdcbd7ea35df9d29849905 Reviewed-on: https://chromium-review.googlesource.com/924030 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
-
Gabriel Charette authored
Follow-up to https://chromium-review.googlesource.com/c/v8/v8/+/924867 This is the core goal of the initial CL @ https://chromium-review.googlesource.com/c/v8/v8/+/922103 which was since split into multiple to diagnose a bots-only failure. Bug: chromium:812178 Change-Id: I4c4e0b517737e020862917bd89fa6ce38244e597 Reviewed-on: https://chromium-review.googlesource.com/924031 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#51356}
-
Predrag Rudic authored
Change-Id: I101cd4eea87f17a1454c3e2b39c421e304509e61 Reviewed-on: https://chromium-review.googlesource.com/919085 Commit-Queue: Ivica Bogosavljevic <ivica.bogosavljevic@mips.com> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#51355}
-
Gabriel Charette authored
This will let us identify in traces whether unwinding after receiving the preemption event is slower than desired and should be optimized. Adding it to pausing while working on removing it in https://chromium-review.googlesource.com/c/v8/v8/+/922103 will allow gathering traces that highlight the issue. R=mlippautz@chromium.org Bug: chromium:812178 Change-Id: I0555c6825e0792769c9ae2d748d7cc35df4f6fed Reviewed-on: https://chromium-review.googlesource.com/924122 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
-
Gabriel Charette authored
This was extracted from https://chromium-review.googlesource.com/c/v8/v8/+/924073/10 after it became clear that using COMPLETE_TASKS/PREEMPT_TASKS where it should make sense to doesn't work in practice for now. Experimental CLs which led to the above conclusion: - https://chromium-review.googlesource.com/c/v8/v8/+/924865 (COMPLETE or CANCEL -- still broken) - https://chromium-review.googlesource.com/c/v8/v8/+/924866 (CANCEL only, as before, works) - https://chromium-review.googlesource.com/c/v8/v8/+/924028 (CANCEL and PREEMPT -- broken as well) Introducing this unittested API allows to reduce the size of the CLs causing hard-to-diagnose bots-only failures and fix them individually follow-ups @ 1) https://chromium-review.googlesource.com/c/v8/v8/+/924029 2) https://chromium-review.googlesource.com/c/v8/v8/+/924031 3) https://chromium-review.googlesource.com/c/v8/v8/+/924030 Bug: chromium:812178 Change-Id: Icdac456e9f7874b0c4b321ccdb8898297dad7d73 Reviewed-on: https://chromium-review.googlesource.com/924867 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
This is a reland of dda0419e. Originally reviewed-on: https://chromium-review.googlesource.com/914513 and landed as refs/heads/master@{#51342}. Bug: v8:6791 Change-Id: I3b3a069da7a0e64c38a81b3110dc5ece4887cb19 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Reviewed-on: https://chromium-review.googlesource.com/924665Reviewed-by:
-
Yang Guo authored
Use tools/node/update_node.py instead. TBR=machenbach@chromium.org Change-Id: Ib6f7b93e92b27e967627517a0afe2fedd533f6c4 Reviewed-on: https://chromium-review.googlesource.com/924153Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#51351}
-
Ulan Degenbaev authored
This replaces three passes over the roots with a single pass. This also removes root synchronization logic. The GC subroot index is computed from the |root| parameter of the visit method. The new |description| parameter is used as an edge name. Bug: chromium:811842 Change-Id: I03a9215d56b54b3eb5f7bc8b32d5b22ad091c68b Reviewed-on: https://chromium-review.googlesource.com/916781Reviewed-by:
-
Gabriel Charette authored
This was extracted from https://chromium-review.googlesource.com/c/v8/v8/+/924073/7 in an attempt to isolate hard-to-diagnose bots-only failures there. Bug: chromium:812178 Change-Id: I980b25ec7d775b74ade75e9166806740b93eea8e Reviewed-on: https://chromium-review.googlesource.com/924026Reviewed-by:
-
https://chromium-review.googlesource.com/c/v8/v8/+/924073/10Gabriel Charette authored
This is an attempt to isolate what's causing the hard-to-diagnose bots only failures with that CL. Bug: chromium:812178 Change-Id: I50ffe8953bebbbc6b5a5e2f689718662a537acb4 Reviewed-on: https://chromium-review.googlesource.com/924864Reviewed-by:
-
Erik Luo authored
Bug: chromium:810176 Change-Id: I089a1678dfbe0c3bb664e54818a6853f66d364b2 Reviewed-on: https://chromium-review.googlesource.com/923387 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by:
-
Marja Hölttä authored
Change-Id: I4f1d3bd609c48a8deed04e3e59ef326c0e4735c3 Reviewed-on: https://chromium-review.googlesource.com/923985Reviewed-by:
-
- 17 Feb, 2018 4 commits
-
-
Sergiy Byelozyorov authored
TBR=sergiyb@chromium.org No-Try: true Bug: chromium:616879 Change-Id: I5023040d3ce7753d39345033f91848e4f0ed36d9 Reviewed-on: https://chromium-review.googlesource.com/921101 Commit-Queue: Sergiy Byelozyorov <sergiyb@chromium.org> Reviewed-by:
Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#51345}
-
Michael Achenbach authored
This reverts commit dda0419e. Reason for revert: msvc unhappy: https://build.chromium.org/p/client.v8/builders/V8%20Win64%20-%20msvc/builds/1434 Original change's description: > [bigint] Add BigInt64Array, BigUint64Array > > Bug: v8:6791 > Tbr: hpayer@chromium.org > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng > Change-Id: I637e9084d2fe4869ad0be2fb996149ab9940f346 > Reviewed-on: https://chromium-review.googlesource.com/914513 > Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> > Reviewed-by: Georg Neis <neis@chromium.org> > Cr-Commit-Position: refs/heads/master@{#51342} TBR=jkummerow@chromium.org,neis@chromium.org,hpayer@chromium.org Change-Id: I49237fa323f0d3ea70e744d92d5cbdd4d5c4b39f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:6791 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Reviewed-on: https://chromium-review.googlesource.com/924663Reviewed-by:
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/c5c828a..e2c6aae Rolling v8/buildtools: https://chromium.googlesource.com/chromium/buildtools/+log/a09e064..2888931 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/e7298f3..4aa92ef TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Id6e6a5be6a6c2480a83489b2c5f82d8f7139c4b3 Reviewed-on: https://chromium-review.googlesource.com/924357Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#51343}
-
Jakob Kummerow authored
Bug: v8:6791 Tbr: hpayer@chromium.org Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: I637e9084d2fe4869ad0be2fb996149ab9940f346 Reviewed-on: https://chromium-review.googlesource.com/914513 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
-
- 16 Feb, 2018 8 commits
-
-
Michael Achenbach authored
Depends on: https://crrev.com/c/924114 TBR=yangguo@chromium.org Bug: chromium:756691 Change-Id: Ibbc3bd35e8727296c1539edc961e3184830575ff Reviewed-on: https://chromium-review.googlesource.com/924609Reviewed-by:
-
Bill Budge authored
- Replaces calls to Allocator Reserve, Free, and SetPermissions with equivalent page allocator calls (allocation.h). - Un-implements these methods to catch usage, in preparation for removing these. Bug: chromium:799573 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Change-Id: Id233b7a9cfc8e332c64e514f6359e8b670c2d75e Reviewed-on: https://chromium-review.googlesource.com/911883 Commit-Queue: Bill Budge <bbudge@chromium.org> Reviewed-by:
Eric Holk <eholk@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#51340}
-
Mathias Bynens authored
Intent to ship: https://groups.google.com/d/msg/v8-users/YZnlGa8ZMoc/_w7H3x_BAgAJ Bug: v8:7418 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: I9e80dd98fa7b04fee3be591282e455f5576eeed2 Reviewed-on: https://chromium-review.googlesource.com/923728Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Mathias Bynens <mathias@chromium.org> Cr-Commit-Position: refs/heads/master@{#51339}
-
Bill Budge authored
Bug: chromium:799573 Change-Id: I467c74b5b26bc6f1e1a35c1104df12b77f072bac Reviewed-on: https://chromium-review.googlesource.com/923430Reviewed-by:
-
Alexey Kozyatinskiy authored
We already cleanup these scripts on frontend side. It is crucial to cleanup them on backend side as well, since some web applications use following logic: get some data from network, add this data to buffer, try to parse buffer using JSON.parse. On each unsuccessfull JSON.parse we get another scriptFailedToParse event. Frontend logic of discarding scripts: https://goo.gl/FDtaWK Some idea of smarter logic here: track what script ids are reported using protocol and cleanup only script ids which reported not only as part of scriptFailedToParse event. R=alph@chromium.org Bug: chromium:810812 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel Change-Id: Ifd67764c232e4abc7dc6e8e69a651bf9ac0e381b Reviewed-on: https://chromium-review.googlesource.com/919834 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by:
-
Michael Achenbach authored
NOTRY=true Bug: v8:7455 Change-Id: Icb82e8196bc16b4c8b0eebb3c5820e6b3d581735 Reviewed-on: https://chromium-review.googlesource.com/924309Reviewed-by:
-
Michael Achenbach authored
This will enable some fuzzers to alter the thread-pool size. Bug: v8:7455 Change-Id: Ic9c9600cdb3dc50e860dbda8432a23bb20f1dd44 Reviewed-on: https://chromium-review.googlesource.com/924273Reviewed-by:
-
Benedikt Meurer authored
The ES2017 specification contains a so-called "throwaway" promise that is used to specify the behavior of await in terms of PerformPromiseThen, but it's actually not necessary and never exposed to user code. In addition to that, hooking up the promise in await required a context (to refer to the generator object) and two closures for the reject/fulfill handling, which would resume the generator corresponding to the async function. That meant, we had to allocate 4 additional objects for every await. Instead of using a JSPromise plus the callbacks, this CL adds logic to allow PromiseReaction and PromiseReactionJobTask to carry arbitrary payloads and Code handlers. We use this for await to avoid the additional 4 objects mentioned above, and instead just have simple Code handlers that resume the generator (for the async function), either by throwing (in case of a rejection) or by resuming normally (in case of fulfillment). For this to work properly the JSGeneratorObject has to have a link to the outer promise returned by the async function, so that the catch prediction can still figure out what to do in case of promise rejection. This is done by adding a new generator_outer_promise_symbol when the debugger is active, which refers from the generator to the outer promise. With this change the doxbee-async-es2017-native test goes from around 100.54ms to around 82.45ms, which corresponds to a ~18% reduction in execution time. Bug: v8:7253 Change-Id: Iae25b3300bac351c3417be5ae687eff469b0e61f Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng Reviewed-on: https://chromium-review.googlesource.com/924069Reviewed-by:
-
