- 05 Apr, 2019 16 commits
-
-
Michael Starzinger authored
This makes sure that the implicit operand stack slot used for passing an exception from the throw-site to the catch-site is counted against the maximum stack height. R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-rethrow-interpreter BUG=v8:8091 Change-Id: I7e8f47ba4662eb273792e7508207f67588264a2f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554683 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60658}
-
Georg Neis authored
Bug: v8:9087 Change-Id: Ibc21d7e5619e4e6a0edc98cb0bd12e67ab2f6643 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554690Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#60657}
-
Michael Achenbach authored
For standard test failures, the variant name is enough to deduce the full command line of the test. This is used to create the flako command line on the infra side. Test failures from numfuzz have additional variant_flags, calculated by the fuzzer, which don't match a variant name. Exposing those in the test results will enable printing a proper flako command line on infra side for numfuzz cases. Bug: v8:8971 Change-Id: Ie47d42a0b34037da458b474f2a9ab38f1a5d238a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554689Reviewed-by:
Sergiy Belozorov <sergiyb@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60656}
-
Michael Starzinger authored
R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-simd-interpreter BUG=v8:8091 Change-Id: Id0b5da98bbfb91c7a5a878681d7fffe81233284f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552794 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
Benedikt Meurer authored
This introduces a new PROTOTYPE_DESCRIPTOR_ARRAY_TYPE, which is used to be able to distinguish DescriptorArrays for prototypes from regular ones. This is primarily useful for the live objects, since for dead DescriptorArrays we will likely not be able to figure out whether they belong to a prototype Map, unless they die together. Bug: v8:7266 Change-Id: I4b8e0008cc8bae607778151b7c18d30f4efba88d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554687Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60654}
-
Clemens Hammacher authored
This is a reland of d746be9c Original change's description: > [wasm] Use work-stealing queues for background compilation > > This reduces contention on the mutex protecting the {CompilationState} > by splitting the compilation unit queues into several queues (one per > background task). Each task executes its own queue first, and steals > from other queues once it runs out of work. > The implementation of the set of work-stealing queues is encapsulated > in the new {CompilationUnitQueues} class in module-compiler.cc. > > R=titzer@chromium.org > > Bug: v8:8916 > Change-Id: I5a40314917e7d4a35d7ff9e8ec124ec212beacab > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1543350 > Commit-Queue: Clemens Hammacher <clemensh@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60572} Bug: v8:8916 Change-Id: Ic0cbad0ddc31be24715c5490b9ec71a39186fd3b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549172 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60653}
-
Anna Henningsen authored
Typed arrays with elements cannot be frozen, but this function previously would have falsely reported that they are after an `Object.freeze()` call. Since the latter bails out when the object is already frozen, the effect was that when calling `Object.freeze()` on a typed array more than once, the first call would throw and subsequent ones would not. Change-Id: I75e59f51ebb94797cdf39bac4ec4c25c547e70a3 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552781 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#60652}
-
Benedikt Meurer authored
This introduces new virtual instance types to further diagnose what's going on in MapSpace, namely: - MAP_ABANDONED_PROTOTYPE_TYPE includes all the abandoned (fast-mode) prototype maps. - MAP_DEPRECATED_TYPE includes all the deprecated (fast-mode) maps. - MAP_DICTIONARY_TYPE includes all the dictionary-mode maps. - MAP_PROTOTYPE_DICTIONARY_TYPE includes all the prototype maps in dictionary-mode. - MAP_PROTOTYPE_TYPE includes all the prototype maps in fast-mode. - MAP_STABLE_TYPE includes all the (fast-mode) stable (leaf) maps. Those maps who don't fall into any of the buckets above are categorized as MAP_TYPE (as before). The naming was chosen like this to make it possible to filter for the relevant maps in the object stats via 'MAP_.*_TYPE'. Bug: v8:7266 Change-Id: I233734e96a390ddb391bfff8a34a8fec842d1f7f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554685Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Reviewed-by:
-
Michael Starzinger authored
This ensures the lifetime of reference values on the simulated operand stack of the interpreter is coupled to a lifetime of the {ThreadImpl}. We no longer directly store reference values on the stack, but maintain a separate "reference stack" on the GC'ed heap. This will ensure the GC traces such references properly. The new {StackValue} safety wrapper makes sure all use-sites that access the operand stack properly convert to/from handles when dealing with reference values. R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-interpreter BUG=v8:8091,v8:7581 Change-Id: I8c05f2d945a6def943b89be0cfca538a73df8855 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552791 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: -
tzik authored
This expose v8::Context::DetachGlobal() as Realm.detachGlobal() in d8, so that we can test API behaviors on Blink's detached iframes. Change-Id: I4de1dd1a20d5862aba709e36d1d6afa9b221df6c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554322Reviewed-by:
-
Benedikt Meurer authored
This is the first step towards full huge typed array support in V8. Before this change, the JSTypedArray::length and the elements backing store length (FixedTypedArrayBase::length) were used more or less interchangeably to determine the number of elements in a JSTypedArray. With this change we disentangle these two lengths, and instead make JSTypedArray::length authoritative. For on-heap typed arrays, the FixedTypedArrayBase::length will remain the number of elements in the backing store, but for the off-heap typed arrays, this length will be set to 0 (matching the fact that the FixedTypedArrayBase instance does not contain any elements itself). This also unifies the JSTypedArray::set_/length() and length_value() methods to only have JSTypedArray::set_/length() which returns/takes size_t values. Currently this still requires the values to be in Smi range, but later we will extend this to allow arbitrary size_t values (in the safe integer range). Bug: v8:4153, v8:7881 Change-Id: Iff9089130bb31fa9e08e0cf913e7ab52c3dbf107 Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Doc: http://doc/1Z-wM2qwvAuxH46e9ivtkYvKzzwYZg8ymm0x0wJaomow Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1543729 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Ben Titzer <titzer@chromium.org> Reviewed-by:
-
Frank Tang authored
See https://chromium.googlesource.com/chromium/deps/icu/+/1552155 for changes. Correct test expectation based on icu64 changes. CL of Rolling the same ICU hash to DEPS in chromium/src Repo is in https://chromium-review.googlesource.com/c/chromium/src/+/1536613 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Bug: chromium:943348, v8:9052 Change-Id: I3a4579ba745f7f6a621b2059de325bea7a2472a1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1536559Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60647}
-
Frederik Gossen authored
Locks for compilation state callbacks and for the native module are again taken one after the other. As a consequence, publishing compiled Wasm code again happens in parallel. Compile times are now comparable to before lazy hints were enabled. Bug: chromium:949050 Change-Id: I45c52254d046de080938bd131fd3ed8116660bef Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552787 Commit-Queue: Frederik Gossen <frgossen@google.com> Reviewed-by:
-
Clemens Hammacher authored
This reverts commit 1fb26d83. Reason for revert: Flushes out TSan issues: https://ci.chromium.org/p/v8/builders/ci/V8%20Linux64%20TSAN/25782 Original change's description: > [regalloc] Enable control flow aware allocation > > This is a test to see how much and where we regress. We have seen > some quirks of our current allocator that do not show up in this > new approach, so we need to decide whether to stabilize the new > allocation scheme. Performance numbers are a key indicator for that > decision. > > This patch is intended to be reverted after stability and performance > numbers are in (i.e. after a few days). > > Change-Id: I8df8ff7de8efa82a8abbdfa1d21d7877756f129e > Bug: v8:9088 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552786 > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Reviewed-by: Jaroslav Sevcik <jarin@chromium.org> > Commit-Queue: Sigurd Schneider <sigurds@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60643} TBR=mstarzinger@chromium.org,jarin@chromium.org,sigurds@chromium.org Change-Id: Ia1934b01b0909479b2bd52ba686cc9b3fb364b4b No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:9088 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554682Reviewed-by:
-
Georg Neis authored
Bug: v8:9087 Change-Id: Ia806686b47f0e6ddc89f6b043df65ab8a931bbf8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552798Reviewed-by:
-
Sigurd Schneider authored
This is a test to see how much and where we regress. We have seen some quirks of our current allocator that do not show up in this new approach, so we need to decide whether to stabilize the new allocation scheme. Performance numbers are a key indicator for that decision. This patch is intended to be reverted after stability and performance numbers are in (i.e. after a few days). Change-Id: I8df8ff7de8efa82a8abbdfa1d21d7877756f129e Bug: v8:9088 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552786Reviewed-by:
-
- 04 Apr, 2019 24 commits
-
-
Deepti Gandluri authored
Change-Id: I453c356a6d9098739e7bf32d3c7a75c8afb7cab2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1554106Reviewed-by:
Ben Smith <binji@chromium.org> Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Cr-Commit-Position: refs/heads/master@{#60642}
-
Deepti Gandluri authored
Some state related to WasmMemories is cached on the JSArrayBuffer object (is_growable, is_wasm_memory). The problem with this is in some PostMessage flows, this information can get lost depending on how JSArrayBuffers are deserialized. In this particular case when the WasmMemory is postMessaged, it goes through the Blink DedicatedWorkerMessagingProxy::PostMessageToWorkerGlobalScope flow, which reconstructs the ArrayBuffer from the backing store, and size, and loses the is_growable flag, leading to a failure to grow memory. Moving the is_growable flag so that AllocationData can be the source of truth for all wasm memory state, and is consistently preserved across PostMessage. Change-Id: I775f66ddeff68b8cafc18b75ca5460dfb0343c8b Bug: v8:9065 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549789 Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#60641}
-
Jaroslav Sevcik authored
This makes the DCHECK consistent with the map updater. See https://cs.chromium.org/chromium/src/v8/src/map-updater.cc?l=330&rcl=5671f8b940b0fcdb550e318e449ded0f866e935a Bug: chromium:949435 Change-Id: Id4fef60cdca094e638a1db38878953ecb2422c4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552797Reviewed-by:
-
Daniel Clifford authored
Indexed fields in classes can now be initialized using iterators and a spread syntax, e.g.: class Foo { length: Smi; elements[length]: Object; } new Foo{length: 5, elements: ...iter}; where iter implements Torque's iterator protocol. This protocol requires the definition of a method with the following signature: Next(): <type> labels NoMore; Where <type> is the Torque type of the values to be iterated. In the case of indexed field initialization, the type must be the field's type or a subtype thereof. Field initialization with spread is desugared into a loop that calls the spread iterator's Next method and assigns each returned value in order to the corresponding indexed field element. The general machinery for the spread syntax has been added to the ast and parser, however, it can currently only be used in the specific context of indexed field initialization. Spread operators used in any other context will cause an error. Bug: v8:7793 Change-Id: If071e61db8166573c28d13318879c88ba96f6d98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550407 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by:Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#60639}
-
Sigurd Schneider authored
Bug: v8:9020 Change-Id: I1b9f3c0c805709c6570785ec9f1045f21c9d03e4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1541048Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
Michael Achenbach authored
TBR=sergiyb@chromium.org NOTRY=true Bug: chromium:933093 Change-Id: Iaf703f9f9743c508c1f63301a74a1076286fab79 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552792Reviewed-by:
-
Michael Achenbach authored
TBR=sergiyb@chromium.org NOTRY=true Bug: chromium:933093 Change-Id: Idff6d4bdee2192eea895ca044c5a529e3638e908 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552789Reviewed-by:
-
Clemens Hammacher authored
R=mstarzinger@chromium.org Bug: v8:8217 Change-Id: I91534149f6a1d4cb4bf2beccc7ab53d75e677024 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552780 Auto-Submit: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:
-
Michael Achenbach authored
This reverts commit c652b5a1. Reason for revert: Clang roll detecting this failures was reverted. Original change's description: > [test] Skip tests blocking DEPS roll > > NOTRY=true > > Bug: v8:9086 > Change-Id: I1a430c12d5ddccb17931fa32f45463b7d8992971 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552005 > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > Reviewed-by: Sergiy Belozorov <sergiyb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60624} TBR=machenbach@chromium.org,sigurds@chromium.org,jshin@chromium.org,sergiyb@chromium.org Bug: v8:9086 Change-Id: I083c9b4c037bdae1bc0bfbd872bc73b931fbb853 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552785Reviewed-by:
-
Maciej Goszczycki authored
Bug: v8:8834 Change-Id: I763869297e52baf1142f89f0567441c05e00391c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552784Reviewed-by:
-
Michael Starzinger authored
R=clemensh@chromium.org Change-Id: I643d9a142e55405ec010cfe56915527e3cff2d6d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552783 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/6fdec9f..96d2ee3 Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/235be3c..218cb3d Rolling v8/buildtools/third_party/libc++/trunk: https://chromium.googlesource.com/chromium/llvm-project/libcxx/+log/955113d..fbddc46 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/95a9e86..25ef1f6 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ifcda76b2b210ba6bfdee10170e042b5dbfff6d01 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1551412Reviewed-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@{#60631}
-
Clemens Hammacher authored
We only use the safe math helpers (CheckedNumeric<T>) in very few places. The headers are huge though, and complex. They are pulled in to 839 of our object files, increasing compilation time. I also find the implicit checks more easy to understand than the complex logic in CheckedNumeric. Thus, this CL removes the safe_math headers and implements bounds checks for the five uses explicitly. R=jkummerow@chromium.org, mlippautz@chromium.org Bug: v8:8834 Change-Id: I2d60f95799ee61cfa161354428605f67829cd736 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547651Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60630}
-
Sigurd Schneider authored
Bug: v8:9020 Change-Id: Ic949775e018d2bad08fc36db8cdf912df3d67e65 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552779Reviewed-by:
-
Sigurd Schneider authored
Bug: v8:9020 Change-Id: Ie624a02598f5c3a43e40e03d0337c17ca5cc3769 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1541052 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#60628}
-
Georg Neis authored
It's implied by the last clause of the conjunction. Change-Id: I78a810a259888eda696c77cd6c117b35ef9e861a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549171Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#60627}
-
v8-ci-autoroll-builder authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/c2f2e5a..6fdec9f Rolling v8/buildtools: https://chromium.googlesource.com/chromium/src/buildtools/+log/459baaf..235be3c Rolling v8/buildtools/linux64:gn/gn/linux-amd64: https://chrome-infra-packages.appspot.com/gn/gn/linux-amd64/+log/git_rev..git_rev Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/e1fc0b0..63e0762 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/865445e..b8268ca Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/b823d94..95a9e86 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: Ie516f9c71b9709b86def577369702ae149744091 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552157Reviewed-by:
-
Frank Tang authored
Rolling v8/test/test262/data: https://chromium.googlesource.com/external/github.com/tc39/test262/+log/324f291..6119191 Bug: v8:7834 Change-Id: I2ff745e709727d80ad6be6e910b1896adf78d3db Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1551406Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#60625}
-
Michael Achenbach authored
NOTRY=true Bug: v8:9086 Change-Id: I1a430c12d5ddccb17931fa32f45463b7d8992971 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552005 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
-
tzik authored
Context::microtask_context can be null after v8::Context::DetachGlobal is called, and that should cancel microtasks that are associated to the detached context. However, there are several callers left without the null check to the microtask queue, and that causes crashes. This CL adds the null check and cancellation as the crash fix. Bug: chromium:937784 Change-Id: Ie8d107f28f200cee6e75798e3f72c5ed7a2a461c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545139 Commit-Queue: Taiju Tsuiki <tzik@chromium.org> Reviewed-by:
-
Tobias Tebbi authored
This changes the syntax for constructing structs and classes to explicitly mention the fieldnames, similar to JavaScript object literals. The fields still have to be listed in the same order as in the struct/class declaration. As in Javascript, {foo: foo} can be abbreviated as {foo}. Example: macro NewJSArray(implicit context: Context)( map: Map, elements: FixedArrayBase): JSArray { return new JSArray{ map, properties_or_hash: kEmptyFixedArray, elements, length: elements.length }; } Drive-by cleanup: Make struct and class constructors follow the same pattern in the parser and the AST. Bug: v8:9018 v8:7793 Change-Id: I22ff7f68270e4f406aa80731a709d41ea52f52bb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1551999Reviewed-by:Daniel Clifford <danno@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#60622}
-
Benedikt Meurer authored
Don't record samples from machines without high-resolution timers, as that can cause serious reporting issues. See the thread at http://g/chrome-metrics-team/NwwJEyL8odU/discussion for more details. Bug: v8:9074 Change-Id: I8f9b588b249f944c4bc95feedf56960b28db9ddc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552001 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/8059cd6..2a28a92 [test] Add dedicated test for memory.size (#997) (Andreas Rossberg) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/2a28a92 TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: Idcb9a6f8f57d0e9d3f673d5575e663d729a50366 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1551405Reviewed-by:
-
Yu Yin authored
This is port for https://crrev.com/c/1524482 Original commit message: This allows immediates to be encoded directly into instructions, rather than mov-ing constants to registers first. This patch only changes emit_{i64,i32}_add, other emit_ functions will be changed once this approach has been approved. Bug: v8:9038 Change-Id: I96929f870e54b24403a32428f3db31b42f41087a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545148Reviewed-by:
-
