- 04 Mar, 2020 12 commits
-
-
Ng Zhi An authored
Bug: v8:9561 Change-Id: I5fbf69aaacccfe588f95edf1208176e3a7de62bb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2071397Reviewed-by:
Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Zhi An Ng <zhin@chromium.org> Cr-Commit-Position: refs/heads/master@{#66588}
-
Ng Zhi An authored
Bug: v8:9561 Change-Id: I4a2c6217dea540b81256dcc833412da573f54795 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2069403Reviewed-by:
-
Timothy Gu authored
This is a reland of 93253978 Original change's description: > Use context of then function for PromiseResolveThenableJob > > When a microtask is executed, we need to use an appropriate, > non-detached Context for its execution. Currently with > PromiseResolveThenableJobs [1], the Context used is always drawn from > the realm of the Promise constructor being used. This may cause > non-intuitive behavior, such as in the following case: > > const DeadPromise = iframe.contentWindow.Promise; > const p = DeadPromise.resolve({ > then() { > return { success: true }; > } > }); > p.then(result => { console.log(result); }); > > // Some time later, but synchronously... > iframe.src = "http://example.com"; // navigate away. > // DeadPromise's Context is detached state now. > // p never gets resolved, and its reaction handler never gets called. > > To fix this behavior, when PromiseResolveThenableJob is being queued up, > the `then` method of the thenable should be used to determine the > context of the resultant microtask. Doing so aligns with Firefox, and > also with the latest HTML spec [2][3]. > > This change is analogous to CL 1465902, which uses the realm of the > reaction handlers to determine the Context PromiseReactionJobs run in. > > [1]: https://tc39.es/ecma262/#sec-promiseresolvethenablejob > [2]: https://html.spec.whatwg.org/C/#enqueuejob(queuename,-job,-arguments) > [3]: https://github.com/whatwg/html/pull/5212 > > Bug: v8:10200 > Change-Id: I2312788eeea0f9e870c13cf3cb5730a87d15609e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2071624 > Commit-Queue: Timothy Gu <timothygu@chromium.org> > Reviewed-by: Toon Verwaest <verwaest@chromium.org> > Reviewed-by: Shu-yu Guo <syg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#66507} Bug: v8:10200 Change-Id: I5af003a06c60b0c8cd19de47f847a947d40d046c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2082109Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Timothy Gu <timothygu@chromium.org> Cr-Commit-Position: refs/heads/master@{#66586}
-
Igor Sheludko authored
This CL simplifies IC code since we no longer need to keep feedback slot indices in both Smi and IntPtr form and as a result it should improve overall performance of --no-opt mode on Octane by ~1%. Bug: v8:10047 Change-Id: Ib717697cdb805c9f93286e9c62ee8a63361d3560 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1965586 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#66585}
-
Milad Farazmand authored
Change-Id: I84d53282278d12c2e47b8e9a07b69ecf89dba237 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2087692 Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66584}
-
Sami Kyostila authored
This patch rolls v8 to the latest Perfetto revision. Since Perfetto has changed the way the GN protobuf integration works, we need to make some corresponding changes in V8. Bug: chromium:639003 Change-Id: I263c591560503c9779bbab3ec266cfb2708fc51f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2085175Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Auto-Submit: Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#66583}
-
Camillo Bruni authored
Drive-by-fix: Add V8_WARN_UNUSED_RESULT to MaybeHandle::ToHandle Bug: chromium:1057653 Change-Id: I2834806ca498a2fa43a64f5391606cdbfb4af4fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2084814Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#66582}
-
Ulan Degenbaev authored
This reverts part of f3babafb that removed the scope in the test function Bug: v8:10298 Change-Id: I3c515307b9ea4d03e0d7427422d46302e78d8b38 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2087395Reviewed-by:
Dominik Inführ <dinfuehr@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#66581}
-
Leszek Swirski authored
Add off-thread support for class boilerplate allocation, removing a previously "unreachable" overload. Notably, this requires support for off-thread allocation of Dictionaries and DescriptorArrays. Due to template fun, the off-thread allocation of Dictionaries in particular requires some amount of boilerplate (no pun intended). Bug: chromium:1011762 Change-Id: I37139d924858e31e45d369742329826784a8f614 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2080370 Commit-Queue: Igor Sheludko <ishell@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Andreas Haas authored
There was an issue in the register allocation in the original CL. The register of the new_value did not get pinned, so it was used for the expected value as well. Bug: v8:10108 Change-Id: I2589fc31f8fbfda39c94ea5801f63ed370a3b7ce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2084815 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by:
-
Michael Achenbach authored
TBR=santa Change-Id: Ie0479e25f90176bfef0df0d628353de8a61c8f47 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2086094Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/c6ac51f..fa4450f Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/03a5e99..f6edc90 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/4576851..fe6f752 TBR=machenbach@chromium.org,tmrts@chromium.org Change-Id: If5981229cb900326e4e78980aab94cc0fd24a909 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2086831Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#66577}
-
- 03 Mar, 2020 28 commits
-
-
Milad Farazmand authored
Change-Id: Ia0b4da412e9bb37e2991ffc51738ff248e5c691f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2085354Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Commit-Queue: Milad Farazmand <miladfar@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#66576}
-
Joyee Cheung authored
When an empty class is nested inside a class with private instance methods, like this: class Outer { constructor() {} #method() {} factory() { class Inner { constructor() { } } return Inner; } run(obj) { obj.#method(); } } The bytecode generator previously generate private brand initialization for the constructor of Inner by mistake, because during scope chain serialization/deserialization, the outer scopes of Inner and factory() are not allocated or serialized (as they are empty). In the eyes of the bytecode generator, it then appeared as if Outer is the direct outer scope of Inner's constructor. In order to work around this information loss, in this patch we rely on SharedFunctionInfo instead of the Context/ScopeInfo chain to maintain the information about private brand initialization. This is done by shrinking expected_nof_properties to 8 bits and freeing 8 bits for a second bitfield on the SFI. Design doc: https://docs.google.com/document/d/14maU596YbHcWR7XR-_iXM_ANhAAmiuRlJZysM61lqaE/edit# Bug: v8:9839, v8:8330, v8:10098 Change-Id: I4370a0459bfc0da388052ad5a91aac59582d811d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2056889 Commit-Queue: Joyee Cheung <joyee@igalia.com> Reviewed-by:Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Leszek Swirski authored
Remove Isolate parameters from some dictionary methods, and change others to use ReadOnlyRoots instead, to prepare for Isolate templatization in a future patch. One small side-effect is that the global dictionary's property cell's dependent code deoptimization has to dynamically get the Isolate when it needs to actually mark code for deoptimization, for method signature consistency. Given that this is the slow path anyway, it shouldn't matter. Bug: chromium:1011762 Change-Id: I707de9a74ca3b30423a1e5830a10729d6a404786 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2080369 Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Z Nguyen-Huu authored
Add tier up to existing recompilation logic. This is a part of Tier up to Turbofan on Debugger.disable Bug: v8:10290 Change-Id: I44731df520201ac254f2d1bfbfb5c49d8bb50117 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2080658 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
-
Z Nguyen-Huu authored
Example can be inspector tests. Bug: v8:10264 Change-Id: I996bb68d0f36920568a04f93cd8c1256a4f41a96 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2070912 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
-
Leszek Swirski authored
Rather than walking SharedFunctionInfos recursively via bytecode constant pools to ensure they have source positions, walk the script's shared function info list. Bug: chromium:1011762 Change-Id: I19ab0f3355dc8169f7a0170b4198075bd3823c04 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2084816 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Victor Gomes authored
Bug: v8:10201 Change-Id: I5cae5d5c30f42427995c2380d906ade0f117fcd9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083011 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
Leszek Swirski authored
Make Hashtable Shapes return Map Handles (from the read-only roots) instead of the root index of the Map, so that they can be used off the main thread. Bug: chromium:1011762 Change-Id: I4c0a8518dc1c6d490b5c04da05b5319081a6fae5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083298 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Jakob Kummerow authored
Move the recently introduced extra check for 32-bit platforms so that it covers all code paths that would be hit by custom/future memory limit settings. Bug: chromium:1057094 Change-Id: I5e2217a24578ee82c7bfa753b7d5dcd3d00e1b7c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083300Reviewed-by:
Andreas Haas <ahaas@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#66568}
-
Ambroise Vincent authored
Vectors are being sorted multiple times in EmitBinarySearchSwitch(). Change-Id: I8c1053b8a5371904475a3f8c909041835e441d9e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2077683Reviewed-by:
Martyn Capewell <martyn.capewell@arm.com> Reviewed-by:
Michael Stanton <mvstanton@chromium.org> Commit-Queue: Martyn Capewell <martyn.capewell@arm.com> Cr-Commit-Position: refs/heads/master@{#66567}
-
Leszek Swirski authored
Add the remaining missing templatizations to allow an initial wiring in of the off-thread factory into streaming compilation finalization. The off-thread finalization is behind a flag, disabled by default: --finalize-streaming-on-background When the flag is enabled, background tasks will perform perform the finalization during their background execution, and will release the parser and compilation jobs once they are no longer needed. The implementation is complete enough for performance testing, but not enough for launch. Notably, there is no support for: * Class boilerplates (the code is marked unreachable), * Exceptions during finalization, i.e. parse/compile warnings/errors, * Allocation sampling, * Logging, * Asm.js, * Parallel complication tasks * Forced source positions (for "NeedsDetailedOptimizedCodeLineInfo()") This patch also adds some tracing events for the various stages of the off-thread finalization (including the main-thread merge) for further performance improvements. Bug: chromium:1011762 Change-Id: Ia44fa56975dd689f0d92c1543b294cdb063eb199 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2066965 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Reviewed-by: -
Milad Farazmand authored
Port 34f9bcdb Original Commit Message: Implements i8x16.abs, i16x8.abs, and i32x4.abs. R=zhin@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: Ib32356532965a2187a8e8d9ec2cff44585020f0f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2084641Reviewed-by:
-
Milad Farazmand authored
Port 9245e3b4 R=zhiguo.zhou@intel.com, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I9a6358dfd2bfd69e421c85fe3bbf343e7aee3b8c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2081575Reviewed-by:
-
Leszek Swirski authored
Although AccessorInfos are technically mutable, in practice they are not mutated after initialization, and they are guaranteed to be immortal and immovable. So, we can safely make them accessible from the off-thread factory, as long as the user promises to not try to mutate them. This is necessary for off-thread class boilerplate creation. Bug: v8:10218 Bug: chromium:1011762 Change-Id: Id3108a2324a000ea0616b472dd77aed65b1f908e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2080351 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Dan Elphick <delphick@chromium.org> Cr-Commit-Position: refs/heads/master@{#66563}
-
Dominik Inführ authored
Report the total size of global handles in GetHeapStatistics as well. This size includes used and free global handles. Change-Id: I08c0647d993a810a37ae9f332732de9551b5ea8d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083020 Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by:
-
Camillo Bruni authored
Change-Id: Iecfa43f02287d8a540663ed65ad26cdf31e0a19a No-Try: true No-Presubmit: true No-Tree-Checks: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2082567Reviewed-by:
-
Victor Gomes authored
Bug: v8:10201 Change-Id: Ia7e964df89ac134c01a3fd94ce4b15f1afd0cbff Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083295Reviewed-by:
-
Camillo Bruni authored
Change-Id: I213587414aaa4d159dc0c6fd9b5986d7bfcaa3ea Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2082562Reviewed-by:
-
Camillo Bruni authored
Call the @@hasInstance trap only when required by the spec. Bug: chromium:1052647 Change-Id: I7a0a3133c7b6280c6a3215e379bf02e9c22ffe55 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2082560 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#66558}
-
Ulan Degenbaev authored
The scope disables garbage collection and should be only used in heap, deserializer, isolate bootstrap, and testing. Change-Id: Ide95926ef32fd9362cd9134e883e1bd626cc3b11 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083292Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#66557}
-
Michael Achenbach authored
TBR=santa Change-Id: Ie318314abb2384df22deee4e3e33e2a7139e8d7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083482Reviewed-by:
-
Shu-yu Guo authored
Bug: v8:10293 Change-Id: If585e7860721cb2de37a0de5bf135e7a4e226190 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2081338 Auto-Submit: Shu-yu Guo <syg@chromium.org> Reviewed-by:
Ben Smith <binji@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#66555}
-
Camillo Bruni authored
Newer gdb versions require the return type to be specified. Change-Id: Ia9c160858036e9cbbe1ced123bbcc79d9efb78b4 No-Try: true No-Presubmit: true No-Tree-Checks: true Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2082561Reviewed-by:
-
Clemens Backes authored
The histograms were removed from chrome. This CL cleans up the V8 code to stop reporting samples. R=ahaas@chromium.org Bug: chromium:1053285 Change-Id: I7c6ff36ac9bb5d86e81e5f36849903a95a8ed618 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083478Reviewed-by:
-
Zhou, Zhiguo authored
Bug: v8:9909 Change-Id: Id89ddb429c90f3f454a581d75b783ff56775b01e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2049247 Commit-Queue: Zhiguo Zhou <zhiguo.zhou@intel.com> Reviewed-by:
Zhi An Ng <zhin@chromium.org> Reviewed-by:
-
Matheus Marchini authored
Improve postmortem metadata generated by gen-postmortem-metadata by also including weak and synchronous accessors, as well as CHECKED and CHECKED2 variants of all accessors currently considered by gen-postmortem-metadata. Also improve type collection by parsing TORQUE_INSTANCE_CHECKERS_SINGLE_FULLY_DEFINED, as we were missing several types with the previous heuristic (like StackTraceFrame, PromiseReaction, and many others). This will include 96 new v8dbg constants which can be used by debuggers like llnode. R=hpayer@google.com, verwaest@google.com, victorgomes@google.com Change-Id: Ia9bea21eec38b92d255c3636c6a284eb27e9ed9b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2056126Reviewed-by:
-
Jakob Gruber authored
This is a reland of c6c9d4bf Original change's description: > Update unicode-regexp-ignore-case-noi18n expectations > > There appear to be one or several bugs in noi18n mode such that > expectations in this test are no longer met. This CL updates > expectations to the current behavior and re-enables the test so we at > least preserve coverage in the other cases. > > The behavior in question should be investigated in the future > (low priority). > > Bug: v8:10120 > Change-Id: Ib7c9a18133a386e6e39ee54d68ce4106d9b28c84 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2081815 > Commit-Queue: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> > Cr-Commit-Position: refs/heads/master@{#66524} Bug: v8:10120 Change-Id: Ib2ee68e26c2aebe2eeab3ec9f7bc263fd79f3773 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2083291 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Zhao Jiazhong authored
Port d303f4fb https://crrev.com/c/2081816 Original Commit Message: In the past we've used the isolate argument to signal whether we were in unicode mode (nullptr) or not (the real isolate). This is no longer needed, and in fact breaks no-i18n mode which always expects to have a real isolate. Change-Id: I90a69a38cb4e74da46b3030843bc84d6d53571c5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2082932 Auto-Submit: Zhao Jiazhong <zhaojiazhong-hf@loongson.cn> Reviewed-by:
-
