- 11 Apr, 2019 1 commit
-
-
Ben Smith authored
See intent to ship here: https://groups.google.com/forum/#!topic/v8-users/zM05lYEBVog wasm-module-builder.js is also changed to use the new syntax for specifying a table index in an element segment. In the MVP, the table index was always zero. The reference types proposal adds support for multiple tables, and originally used this value to specify a non-zero table index. The bulk memory proposal needed a way to specify a passive element segment, so it re-purposed the table index as a flags field and uses a different field for the table index. Bug: v8:7747 Change-Id: If24f2d04e88a29b714f1a78ed417803bae702c76 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1560215 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#60796}
-
- 09 Apr, 2019 4 commits
-
-
Michael Starzinger authored
This adds support for passing/returning reference type parameter/return values when the interpreter is calling extern functions. It expands the existing test coverage to the interpreter. R=clemensh@chromium.org TEST=mjsunit/wasm/anyref-interpreter,mjsunit/wasm/anyfunc-interpreter BUG=v8:8091,v8:7581 Change-Id: I377e9d28aa36866c0441683ffd6a48160b721ec1 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1559853Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60715}
-
Michael Starzinger authored
This adds support for loading and storing mutable imported globals having a reference type in the interpreter. It expands existing test coverage to the interpreter. R=clemensh@chromium.org TEST=mjsunit/wasm/anyref-globals-interpreter BUG=v8:8091,v8:7581 Change-Id: I78e0c5c73664a183e1d92ec91eadf8b9a93e4787 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1559743Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60701}
-
Frederik Gossen authored
When compilation hints are disabled (they are by default) the decoder failed on custom sections with the name 'compilationHints'. This is fixed and a test is added. Bug: v8:9003 Change-Id: I5d25c019a702a722d8baf497d1bcd3a578a2d4bf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557150 Commit-Queue: Frederik Gossen <frgossen@google.com> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60696}
-
Michael Starzinger authored
This adds support for handling reference types when loading/storing globals. Support for imported mutable globals is still missing and will be done in a follow-up change. R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-global-interpreter BUG=v8:8091,v8:7581 Change-Id: I0d14919b1ce7f49c4a0541e3d6a99ee203cfb311 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1558086 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60695}
-
- 08 Apr, 2019 1 commit
-
-
Michael Starzinger authored
This adds preliminary support for references types as argument or return values to functions that are redirected to the interpreter. The current interpreter entry stub remains unchanged, using one buffer area that is hidden from the GC. The corresponding {Runtime_WasmRunInterpreter} now correctly boxes/un-boxes reference types into handles. This switch to a handlified representation happens before any method that potentially triggers a GC is called. R=clemensh@chromium.org TEST=mjsunit/wasm/exceptions-anyref-interpreter BUG=v8:8091,v8:7581 Change-Id: I41c766ed5ac877042d5964e72f3fd7df390c4e98 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1557147 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60684}
-
- 05 Apr, 2019 4 commits
-
-
Ben Smith authored
This is a reland of 63608968 The previous CL failed on Windows, but it was a general bug. The dropped_elem_segments was not being set on the instance properly in cctests, so`table.init` instructions would fail by reading uninitialized data. I took this opportunity to also add an implementation of `elem.drop` in the interpreter, and ported the JS tests for those too. Original change's description: > [wasm] Implement table.init for interpreter > > This also fixes CheckCallViaJS when a trap occurs. In that case, the > trap callback is called instead of an exception being thrown, so if it > isn't handled, a bogus result will be returned instead. > > Bug: v8:8965 > Change-Id: I560e89f353756df23c062fb8c9484d9971c19253 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1539078 > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Ben Smith <binji@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60473} Bug: v8:8965 Change-Id: Ia547d9530b7ca67fde5bd94539f49153b796e82d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547142 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60664}
-
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}
-
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: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60655}
-
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: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60650}
-
- 03 Apr, 2019 1 commit
-
-
Frederik Gossen authored
The tiers are now consistently referred to as baselin and top tier. Bug: v8:9003 Change-Id: I74ad1867aca63bee9eb83b7f0f9fbaf2b1523dcb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547667 Commit-Queue: Frederik Gossen <frgossen@google.com> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60591}
-
- 29 Mar, 2019 1 commit
-
-
Michael Starzinger authored
This fixes initialization of reference type global variables (i.e. anyref and except_ref) based on an index of another global. It extends the existing support to exception types, fixes the logic, and also fixes a missing write barrier. R=ahaas@chromium.org TEST=mjsunit/wasm/exceptions-global BUG=v8:8091 Change-Id: Ia91f1ea03be24fadf3023a5acdd073badb8dcd93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1539581 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60525}
-
- 28 Mar, 2019 1 commit
-
-
Sven Sauleau authored
This CL splits a specific test out the bigint.js test suite in order to be, eventually, ignored by the wasm-bigint proposal 32-bit support CL. Change-Id: I8ab673abfb53bac95952b11716fe4f29a4a7feaa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1543352 Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60510}
-
- 26 Mar, 2019 2 commits
-
-
Michael Achenbach authored
This reverts commit 63608968. Reason for revert: https://ci.chromium.org/p/v8/builders/ci/V8%20Win32%20-%20debug/19535 Original change's description: > [wasm] Implement table.init for interpreter > > This also fixes CheckCallViaJS when a trap occurs. In that case, the > trap callback is called instead of an exception being thrown, so if it > isn't handled, a bogus result will be returned instead. > > Bug: v8:8965 > Change-Id: I560e89f353756df23c062fb8c9484d9971c19253 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1539078 > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Commit-Queue: Ben Smith <binji@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60473} TBR=binji@chromium.org,mstarzinger@chromium.org Change-Id: Iee528ac2f16988b25579af3555e6f17974cb0b05 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:8965 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1539498Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#60474}
-
Ben Smith authored
This also fixes CheckCallViaJS when a trap occurs. In that case, the trap callback is called instead of an exception being thrown, so if it isn't handled, a bogus result will be returned instead. Bug: v8:8965 Change-Id: I560e89f353756df23c062fb8c9484d9971c19253 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1539078Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/heads/master@{#60473}
-
- 25 Mar, 2019 1 commit
-
-
Andreas Haas authored
In the implementation of WebAssembly.compileStreaming and WebAssembly.instantiateStreaming, we did not handle the case where the input, which is a Promise, gets rejected. When this Promise got rejected, the Promise returned by compileStreaming remained pending forever. With this CL, the rejection object of the input Promise gets forwarded to the result Promise. I also extended the --wasm-test-streaming flag to provide WebAssembly.compileStreaming and WebAssembly.instantiateStreaming in d8. The difference to the Chrome versions of these function is that d8 does not know about Response objects. That's why in d8 compileStreaming and instantiateStreaming expect a Promise to an ArrayBuffer or a TypedArray and not to a Response object. Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Bug: chromium:943487 Change-Id: I77f789e9ae5d50ae9c9bc92bf27dbfe338fe0f13 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535817Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60427}
-
- 21 Mar, 2019 2 commits
-
-
Ben Smith authored
Most of the mjsunit/wasm/table-copy.js tests have been ported to cctests, so they can be tested with all execution tiers. Bug: v8:8965 Change-Id: I448719be30a4b2bddb9e2cffb4c74d3134db2f50 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1529548 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60396}
-
Andreas Haas authored
The reason for the revert was that Liftoff did not bail out on indirect calls to tables other than table 0. Whenever the Liftoff code got executed, the test would fail. Original message: With this CL it is possible to use any anyfunc table in call-indirect, not just the first table. The current implementation is based on runtime calls. This is just an initial implementation which should be replaced by a dispatch-table-based eventually. However, this implementation allows us to move forward with the anyref proposal implementation. R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: Iedd56ee7acb281441bca32ffd3dc7157203ee1ac Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532072 Commit-Queue: Andreas Haas <ahaas@chromium.org> Auto-Submit: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60382}
-
- 20 Mar, 2019 2 commits
-
-
Andreas Haas authored
This reverts commit 9d167f57. Reason for revert: There is a crash on https://ci.chromium.org/p/v8/builders/ci/V8%20Win32/20026 Original change's description: > [wasm][anyref] Add support of call-indirect for multiple tables > > With this CL it is possible to use any anyfunc table in call-indirect, > not just the first table. > > The current implementation is based on runtime calls. This is just an > initial implementation which should be replaced by a > dispatch-table-based eventually. However, this implementation allows > us to move forward with the anyref proposal implementation. > > R=mstarzinger@chromium.org > > Bug: v8:7581 > Change-Id: I57d09b18add7f525555bf7c949aef17a64b0e7c5 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1530801 > Commit-Queue: Andreas Haas <ahaas@chromium.org> > Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60360} TBR=mstarzinger@chromium.org,ahaas@chromium.org Change-Id: Iba4b84078aa070498be7e79212970b94595f5757 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7581 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1532069Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60362}
-
Andreas Haas authored
With this CL it is possible to use any anyfunc table in call-indirect, not just the first table. The current implementation is based on runtime calls. This is just an initial implementation which should be replaced by a dispatch-table-based eventually. However, this implementation allows us to move forward with the anyref proposal implementation. R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: I57d09b18add7f525555bf7c949aef17a64b0e7c5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1530801 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60360}
-
- 19 Mar, 2019 3 commits
-
-
Andreas Haas authored
R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: I93044dc0065d1d0146ec9b5190e50ca63ce94f4e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1530808Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60341}
-
Michael Starzinger authored
This extends the support for the "except_ref" type on global variables to support mutable globals, as well as importing and exporting such globals. Test coverage is also increased. R=ahaas@chromium.org TEST=mjsunit/wasm/exceptions-global BUG=v8:8091 Change-Id: I816406e322ffb574a4f054947682491e7b40335f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1530802Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60327}
-
Michael Starzinger authored
This adds basic support and tests for having global variables of type "except_ref" that are default initialized to "null". The functionality is part of the exception handling proposal and solely enabled by the corresponding feature flag. R=ahaas@chromium.org TEST=mjsunit/wasm/exceptions-global BUG=v8:8091 Change-Id: I581bc942fbe6688a5c58790a842fb024de22d924 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1528439 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60317}
-
- 18 Mar, 2019 4 commits
-
-
Sven Sauleau authored
According to WebAssembly's thread proposal, the memory type is decided at the Object's creation and don't change over time. When growing a shared memory and the old buffer was marked as shared; setup the new buffer as shared as well. Bug: v8:8564 Change-Id: I7e59071d11b41315429232ae0c90436c6810bd0e Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1526012Reviewed-by: Deepti Gandluri <gdeepti@chromium.org> Commit-Queue: Sven Sauleau <ssauleau@igalia.com> Auto-Submit: Sven Sauleau <ssauleau@igalia.com> Cr-Commit-Position: refs/heads/master@{#60312}
-
Frederik Gossen authored
Implements decoding of compilation hints section in {ModuleDecoderImpl}. The {wasm-module-builder.js} supports the creation of that section. The feature can be enabled with {--experimental-wasm-compilation-hints}. Bug: v8:9003 Change-Id: Ic87e19d916f2ce316de453ea8c7c48c236a6d673 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1521115Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Frederik Gossen <frgossen@google.com> Cr-Commit-Position: refs/heads/master@{#60299}
-
Andreas Haas authored
Anyfunc globals are very similar to anyref globals. This CL is mostly about extending the conditions which guard the anyref globals code. R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: Ia92ac4560102cc3ed0060342f92758db28f415ca Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1526004Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60281}
-
Andreas Haas authored
R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: Ica85ba80c29d6d5c5b9163df8cf743c0f1da7f4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1520715 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60280}
-
- 15 Mar, 2019 4 commits
-
-
Aseem Garg authored
This CL allows for either of 'minimum' or 'initial' for MemoryDescriptor and TableDescriptor. It also adds a flag for the reflection features. R=binji@chromium.org,adamk@chromium.org Bug=v8:7742 Change-Id: Icfd4825f63e1eb784a39d10f740d55e81489eba7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1485243 Commit-Queue: Aseem Garg <aseemgarg@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/heads/master@{#60256}
-
Ben Smith authored
This CL only provides the implementation of memory.{init,copy,fill} and data.drop. Bug: v8:8965 Change-Id: I439f2520bfee8f147e4b0d1d31f954aaad2e14ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1510575 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60253}
-
Aseem Garg authored
R=binji@chromium.org,adamk@chromium.org Bug=v8:7742 Change-Id: I5b9a614dd0c8b028d756cbd401c803de4cb9437f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1513159 Commit-Queue: Aseem Garg <aseemgarg@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Reviewed-by: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#60252}
-
Aseem Garg authored
This CL also changes the constructor for WasmTableObject so that the maximum_length is set to undefined instead of a default value if there's no maximum provided. R=binji@chromium.org,adamk@chromium.org Bug=v8:7742 Change-Id: I6310224e9997464bf69c198e2694a6cd76e01e8f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1513156 Commit-Queue: Aseem Garg <aseemgarg@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/heads/master@{#60250}
-
- 14 Mar, 2019 2 commits
-
-
Clemens Hammacher authored
Compilation only stores whether an error has been found, but not the exact error or it's location. This is generated by running a validation pass once all wire bytes have been received. This unifies error messages by removing one more location where we generate compilation error messages, and makes it deterministic because a) we always report the error in the first failing function, and b) if names are present, the error message will always contain the function name. R=titzer@chromium.org Bug: chromium:926311, v8:8814 Change-Id: I79551b8bb73dcee503484de343a3ada60a6add4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1521112 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60242}
-
Andreas Haas authored
R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: Id8b9c3596eb6caf5ee7048a87a676a85dba0c5dc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1520711 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60239}
-
- 13 Mar, 2019 3 commits
-
-
Andreas Haas authored
This CL just adds a parameter to addElementSegment and adjusts all existing tests. Note that addElementSegment contains some convenience code to construct one initial table if it does not exist yet. I did not extend that code to multiple tables. If you want to use multiple tables, you have to create them first before calling addElementSegment. R=clemensh@chromium.org Bug: v8:7581 Change-Id: Ie131fd5dc19856703ab5cfb2fa8f7d576f70a18b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1520709Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60211}
-
Andreas Haas authored
This Cl adds a type to {WasmTableObject}, and extends {WasmTableObject::Set} and {WasmTableObject::Get} to support anyref tables. I did it in one CL so that I can write tests. R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: I6c6d78f84715a7805f7bb881a63d3c1174f6a6ab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1511332Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60206}
-
Aseem Garg authored
R=binji@chromium.org,adamk@chromium.org Bug: v8:7742 Change-Id: I13a317372fa06c706e2c648b92d2f2dd3c5a337b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1513152Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Commit-Queue: Aseem Garg <aseemgarg@chromium.org> Cr-Commit-Position: refs/heads/master@{#60200}
-
- 12 Mar, 2019 2 commits
-
-
Clemens Hammacher authored
In particular, remove {toUint8Array} method and make {toBuffer} return a {Uint8Array} view to the buffer like before https://crrev.com/c/1508352. Also, the returned view does not need to be another copy of the bytes, it can really just be a view. As a follow-up, this requires the test-only DeserializeWasmModule runtime method to receive the wire bytes as Uint8Array, and also requires the {IsWasmCompileAllowed} callback to handle {ArrayBufferView} (like chromium's version already does). R=ahaas@chromium.org Change-Id: I87296cdbac14b74e7c8b38a372aa3df572ca6ad6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1518172 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60195}
-
Andreas Haas authored
According to the wasm js-spec, the table index can be uint32. The implementation in our implementation expected an int though. We did not check for the int overflow. I replaced the throwing of the exception in WasmTableObject::Get to use the ErrorThrower instead of throwing the exception with Isolate::Throw directly. The reason is that I see with other CL's that I have to throw several errors, and I don't want to introduce a new message and MessageId for every error. Moreover, the ErrorThrower is a standard way in wasm to throw errors. It feels right to throw the error the same way here. R=mstarzinger@chromium.org Bug: chromium:940296 Change-Id: Idb77c813506fe66a3192b66fe0e8e807b80580ab Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1514496 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60181}
-
- 11 Mar, 2019 1 commit
-
-
Andreas Haas authored
I forgot to add the test file to https://crrev.com/c/1463519. R=mstarzinger@chromium.org Bug: v8:7581 Change-Id: I88d50fe83ae60a8170110504ce7f765aa28db517 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1511480Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#60148}
-
- 09 Mar, 2019 1 commit
-
-
Deepti Gandluri authored
Change-Id: Ie080683af1d990e5205c75a2a199f0581d826811 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1511630 Commit-Queue: Deepti Gandluri <gdeepti@chromium.org> Reviewed-by: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/heads/master@{#60135}
-