- 13 Jun, 2018 20 commits
-
-
Daniel Clifford authored
In the process and as a test case of the module/file-handling, separate Array.p.forEach into its own Torque file. Bug: v8:7793 Change-Id: If45103a9df3bf8fade34e7bcf7c7c9c060e25966 Reviewed-on: https://chromium-review.googlesource.com/1097755Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Daniel Clifford <danno@chromium.org> Cr-Commit-Position: refs/heads/master@{#53703}
-
Michael Starzinger authored
This uses a WebAssembly runtime stub for the out-of-line {DoubleToI} computation instead of a builtin specific to a certain Isolate. It is another step towards making {WasmCode} independent of the Isolate. R=clemensh@chromium.org BUG=v8:7424 Change-Id: Ifdaa8e2511b67468d75e0e4aaf70010ced04a11a Reviewed-on: https://chromium-review.googlesource.com/1098672 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#53702}
-
Simon Zünd authored
R=tebbi@chromium.org Bug: v8:7793 Change-Id: I691b3682aec3269350ee02c29b48ce1d46a1ffcb Reviewed-on: https://chromium-review.googlesource.com/1098656Reviewed-by:
-
Ben L. Titzer authored
Previously, we sent a critical low memory pressure notification when attempting to commit WASM code when the code manager was near the limit for total amount of code allocated. https://chromium-review.googlesource.com/c/v8/v8/+/1073412 "fixed" that, but it causes OOMs on Windows. Since we no longer have the isolate on the code manager, and thus cannot send this notification on commit, send the notification upon the next module creation. This is still not optimal, but should fix OOM issues for lots of small modules on Windows. BUG=v8:7845 R=mstarzinger@chromium.org CC=clemensh@chromium.org Change-Id: I6e20d0c1ee9bc6926a83e0c2fbdc9e9e453588ec Reviewed-on: https://chromium-review.googlesource.com/1098921 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#53700}
-
Clemens Hammacher authored
No need to have a separately defined CallDescriptor. R=titzer@chromium.org Change-Id: Ic7c0ee87d458fa8e55bef4d750aa7f61a763237f Reviewed-on: https://chromium-review.googlesource.com/1098927Reviewed-by:
Ben Titzer <titzer@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#53699}
-
Clemens Hammacher authored
The {WasmSharedModuleData} struct was introduced to hold data common to all wasm instances belonging to the same module. The idea was to keep "internal state" separate from the JS-facing {WasmModuleObject}. Since this objective has no real value, and we already store some internal data on the {WasmModuleObject}, this CL merges these two objects. R=titzer@chromium.org, mstarzinger@chromium.org Bug: v8:7754 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: I04f6d07bf5d812bc4717af26f0f64231345861f9 Reviewed-on: https://chromium-review.googlesource.com/1097491 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: -
Creddy authored
and CreateAllocationSiteInFeedbackVector Change-Id: I935083f1244e62cfe9e4049c9b725db48ce4ce8f Reviewed-on: https://chromium-review.googlesource.com/1090830Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#53697}
-
Creddy authored
Use DEFINE_FIELD_OFFSET_CONSTANTS to describe AllocationSite fields Change-Id: I03ae84e1f4720da9da7e2a8a784f56fe6f155e18 Reviewed-on: https://chromium-review.googlesource.com/1095308Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
-
Georgia Kouveli authored
Replace all uses of Deoptimizer::BailoutType and CodeEventListener::DeoptKind with DeoptimizeKind from src/globals.h. Change-Id: I5b9002583a69bc43d995cacc7619b018e5a70727 Reviewed-on: https://chromium-review.googlesource.com/1097331 Commit-Queue: Georgia Kouveli <georgia.kouveli@arm.com> Reviewed-by:
-
Dominik Inführ authored
After marking ephemerons process the worklist in parallel. Bug: chromium:844008 Change-Id: Id750c19d0f564675f051cc4f9933d41fa0afb42b Reviewed-on: https://chromium-review.googlesource.com/1097490 Commit-Queue: Dominik Inführ <dinfuehr@google.com> Reviewed-by:
-
Igor Sheludko authored
Bug: v8:5269, v8:7703 Change-Id: If80923b767b6bf3533b4d53039b1b5125c670cf1 Reviewed-on: https://chromium-review.googlesource.com/1097486 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#53693}
-
Clemens Hammacher authored
The often used construct {OFStream(stdout)} does not work on Android. This CL introduces an {StdoutStream} which behaves exactly like {OFStream(stdout)} on non-android platforms, and redirects to the Android log on appropriate systems and configurations. R=mstarzinger@chromium.org Bug: v8:7820 Change-Id: Ia682fdf6d064e37c605c19b032f5a10b96ac825b Reviewed-on: https://chromium-review.googlesource.com/1088911Reviewed-by:Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
Dominik Inführ authored
Bug: chromium:844008 Change-Id: Ic736bb91c13da5d52baa53cd3630978b9819f66b Reviewed-on: https://chromium-review.googlesource.com/1097488Reviewed-by:
-
Dominik Inführ authored
Mark values if their corresponding key was already marked. Also take into account the size for backing store. Bug: chromium:844008 Change-Id: I58570f935c69fb39b686fd22dc93caba309f83b2 Reviewed-on: https://chromium-review.googlesource.com/1097400Reviewed-by:
-
Hannes Payer authored
Change-Id: I26c2ba8d22aecac0e1d6a406eb90521ff52e1ec4 Reviewed-on: https://chromium-review.googlesource.com/1097119 Commit-Queue: Hannes Payer <hpayer@chromium.org> Reviewed-by:
-
Igor Sheludko authored
Bug: v8:5269, v8:7703 Change-Id: Ib9934e1c3685f731ba588f12e253fce24c03b151 Reviewed-on: https://chromium-review.googlesource.com/1097485Reviewed-by:
-
Clemens Hammacher authored
We assumed that if the ErrorThrower is empty after instantiation, then instantiation succeeded and an instance exists which we can return. However, if the start function throws, no instance exists, which caused a crash. With this CL we handle execeptions thrown by the start function correctly. R=clemensh@chromium.org Bug: chromium:848966 Change-Id: I51dc94e6bc563aa4a4b88c44a14e831af913fbd8 Reviewed-on: https://chromium-review.googlesource.com/1092234Reviewed-by:
-
Clemens Hammacher authored
For serialization, we do not need the {WasmCompiledModule}. All we need is the {NativeModule}. R=mstarzinger@chromium.org Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: Iff7dc9cde3b1ab777028dbafcc1c870e45e28a93 Reviewed-on: https://chromium-review.googlesource.com/1097480Reviewed-by: -
Michael Starzinger authored
R=clemensh@chromium.org Change-Id: Iddce87713b09450bf069a12f0aa7aa55c7f131e1 Reviewed-on: https://chromium-review.googlesource.com/1097120Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/41d1fdd..169887d Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/09b82f4..fdacd16 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/8e6f58c..e09b684 Rolling v8/third_party/fuchsia-sdk: https://chromium.googlesource.com/chromium/src/third_party/fuchsia-sdk/+log/5131d44..8c08316 Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/145d057..9077ec7 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/7e986fd..37fc68b TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: I97b4f431dcbf67ace6dc2f1c32bafaa6b886c487 Reviewed-on: https://chromium-review.googlesource.com/1098522 Reviewed-by: <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#53684}
-
- 12 Jun, 2018 20 commits
-
-
Ben Smith authored
Mutable globals are now included in the wasm v1 spec. Bug: v8:7625 Change-Id: Ib9b92d8348102f99a3b92820d0057b2c11a1e49a Reviewed-on: https://chromium-review.googlesource.com/1095650 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by:
-
Joyee Cheung authored
This is a reland of a229e121 The original commit broke a layout test in Blink. The test in Blink has been marked to be skipped and will be updated once this patch lands. See https://chromium-review.googlesource.com/c/chromium/src/+/1097455 Original change's description: > [builtins] set DataView.length to 1 > > Refs: https://github.com/tc39/ecma262/pull/1131 > Test: test262/built-ins/DataView/length > Bug: v8:7816 > Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng > Change-Id: I66a06734bd32cd2043a8d04728b2185f6093bd69 > Reviewed-on: https://chromium-review.googlesource.com/1094980 > Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> > Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> > Cr-Commit-Position: refs/heads/master@{#53649} Bug: v8:7816 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: If63be80523a68d3a2b515fe1d55a243d2dd2a9b2 Reviewed-on: https://chromium-review.googlesource.com/1097568Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#53682}
-
Ben Smith authored
Mutable globals are stored in the instance differently, so they must be exported differently as well. Also fix a counting bug that occurred when a module contained a global and an imported mutable global (CalculateGlobalOffsets is called twice). Bug: v8:7625 Change-Id: I1cd7ef5d6ff7cb7e09239035f89d7b36d0436063 Reviewed-on: https://chromium-review.googlesource.com/1096673 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by:
-
Junliang Yan authored
Port 13fc4a1b Original Commit Message: External references located within the isolate can be loaded as a fixed offset from the root register. This avoids one load from memory over the default indirect method (which reads from the external reference table). R=jgruber@chromium.org, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I4a02973a0279517ab5247f4f9519b0e26168c444 Reviewed-on: https://chromium-review.googlesource.com/1097628Reviewed-by:
Joran Siu <joransiu@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#53680}
-
Igor Sheludko authored
This CL also introduces TailCallRuntime() with explicit arity parameter. Bug: v8:6949 Change-Id: I20266a0d3779e0336d5e9f83d3919ffc91fe0f47 Reviewed-on: https://chromium-review.googlesource.com/1097081 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
TBR=titzer@chromium.org Bug: v8:7845 Change-Id: I9670e629ffbb430addb579d55a3e07ed3c9ccbda No-Try: true Reviewed-on: https://chromium-review.googlesource.com/1097483Reviewed-by:
-
Clemens Hammacher authored
R=mstarzinger@chromium.org Change-Id: If72df4425633cac8e98f0dd6adb80512e226f251 Reviewed-on: https://chromium-review.googlesource.com/1097323 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
-
Ben L. Titzer authored
The isolate is mainly used for accounting purposes. As such, it doesn't need a field in the WasmCodeManager, and cannot have one if it is to be made isolate independent. Instead, pass the isolate explicitly in the appropriate cases. R=mstarzinger@chromium.org BUG=v8:7424 Change-Id: I539c2b33692e57605a280530bd704ef25269ad0f Reviewed-on: https://chromium-review.googlesource.com/1073412 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
-
Ben L. Titzer authored
This CL estimates the sizes of the important managed objects in WASM: the decoded module {WasmModule}, the native module that contains code {NativeModule}, and the natively-allocated indirect and import tables {WasmInstanceNativeAllocations}. Since Managed<T> updates the isolate's external allocated memory, it is no longer necessary to do so upon committing or releasing a native module's memory. R=mstarzinger@chromium.org CC=ulan@chromium.org Bug: v8:7424 Change-Id: Iff4e07d0d328383a925febd654ccbfc95f0930e9 Reviewed-on: https://chromium-review.googlesource.com/1079067 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: -
Clemens Hammacher authored
R=mstarzinger@chromium.org Change-Id: I5b062da2b4717f7247ea61d1118f0466c7b0474c Reviewed-on: https://chromium-review.googlesource.com/1097322Reviewed-by:
-
Anna Henningsen authored
As specified in https://tc39.github.io/ecma262/#sec-atomics-wait, the critical section must occur before the load and comparison. This slightly changes the `AtomicsWaitCallback` API, but in a direction that arguably makes it more consistent. As a drive-by fix, reset `node->waiting_` in case there was an exception from the first callback. Refs: https://chromium-review.googlesource.com/c/v8/v8/+/1095814 Bug: v8:7836 Cq-Include-Trybots: luci.chromium.try:linux_chromium_rel_ng Change-Id: I577cdf76cedfe39bc61f783203b543c7c68fc238 Reviewed-on: https://chromium-review.googlesource.com/1096236Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/heads/master@{#53673}
-
Sigurd Schneider authored
This CL inserts NOP instructions a little bit earlier into empty blocks; this ensures that instructions keep their initial position. Bug: v8:7327 Change-Id: Idee5269f4fd7fc15c44bda83a2be74e8cff62df8 Reviewed-on: https://chromium-review.googlesource.com/1097078 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
-
Igor Sheludko authored
This is a necessary cleanup before porting Array[No,Single,N]ArgumentsConstructor builtins to CSA. Bug: v8:5269, v8:7703 Change-Id: I40a2dd83faab1f8c3c180d461ef62fa4d8578f5e Reviewed-on: https://chromium-review.googlesource.com/1097079 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Igor Sheludko authored
Bug: v8:7754 Change-Id: I11845f84c5e837d3d7323c4a932c36af08b61a8e Reviewed-on: https://chromium-review.googlesource.com/1096940Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Michael Achenbach authored
This reverts commit a229e121. Reason for revert: Breaks a layout test: https://ci.chromium.org/buildbot/client.v8.fyi/V8-Blink%20Linux%2064/24021 fast/js/constructor-length.html See also: https://github.com/v8/v8/wiki/Blink-layout-tests Original change's description: > [builtins] set DataView.length to 1 > > Refs: https://github.com/tc39/ecma262/pull/1131 > Test: test262/built-ins/DataView/length > Bug: v8:7816 > Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng > Change-Id: I66a06734bd32cd2043a8d04728b2185f6093bd69 > Reviewed-on: https://chromium-review.googlesource.com/1094980 > Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> > Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> > Cr-Commit-Position: refs/heads/master@{#53649} TBR=gsathya@chromium.org,joyee@igalia.com Change-Id: Iaa602a40bd09dec6884f5f56b1f010b59c19b32a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7816 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Reviewed-on: https://chromium-review.googlesource.com/1097275Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#53669}
-
jgruber authored
These tests are also affected by duplicate builtin copies (on- and off-heap). TBR=yangguo@chromium.org Bug: v8:6666, v8:7718 Change-Id: I8adfe8b8b63fb5f539cdff5e709e9358a47dfc7e Reviewed-on: https://chromium-review.googlesource.com/1097088Reviewed-by:
-
Michael Starzinger authored
This makes sure debug code in WasmCode traps immediately instead of embedding a call to the Abort builtin, which would be Isolate specific. R=clemensh@chromium.org BUG=v8:7424 Change-Id: I08799d41b5e8d21b9f7af97d65f80a1594d9a613 Reviewed-on: https://chromium-review.googlesource.com/1095113 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
jgruber authored
Indirections for external references are now handled completely in macro assemblers, which can produce more efficient code. Bug: v8:6666 Change-Id: I158f2e2517e2d97a1006cec6e3b4ac3a7ef3fab6 Reviewed-on: https://chromium-review.googlesource.com/1095307 Commit-Queue: Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Michael Starzinger authored
This limits the call targets of {WasmCode} to only reference a limited set of builtins via the {RelocInfo::CODE_TARGET} relocation mode. By now most calls have been made independent of the Isolate. R=clemensh@chromium.org BUG=v8:7424 Change-Id: If4c643a7104e2ff0536ceb0f0de7fd30a923d854 Reviewed-on: https://chromium-review.googlesource.com/1092576Reviewed-by: -
Daniel Clifford authored
In the process: - Add strict ordering of Types so that name mangling is consistent and build time. Previously, the UnionType stored the union's types in a std::set<const Type*>, which did not have a consistent ordering of the types in the set. - Add a int31 type to enable consistency and correctness of handling of 'constexpr int31' values on the C++ side. - By removing the "implicit" keyword for operators, there is now one less difference between operators and calls, another incremental step in unifying operators and calls. - Enable external (i.e. C++-defined) generic specializations - Add CSA support for checking double ElementsKinds, including tests. - Clean up some constexpr/non-constexpr handling of ElementsKinds. Bug: v8:7793 Change-Id: I27699aba70b98ebf5466e5b62b045d7b1dad62c8 Reviewed-on: https://chromium-review.googlesource.com/1091155 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by:
-
