- 19 Dec, 2018 1 commit
-
-
Igor Sheludko authored
Also added != 0 for readability in checks like: if (FIELD_SIZE(kFooOffset) != 0) {...} Bug: v8:8477, v8:8562 Change-Id: Ibc305103475e6ec029e89e7ad095ec0a1fa30189 Reviewed-on: https://chromium-review.googlesource.com/c/1382743 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#58360}
-
- 28 Nov, 2018 1 commit
-
-
George Wort authored
This reduces wasm's ABI on Arm to only using the even-numbered float registers in anticipation of Liftoff supporting f32 values on the arm32 port. This is due to Liftoff assuming a one-to-one mapping between double and float registers. The ABI must be restricted in order to allow Liftoff compiled and Turbofan compiled functions to call each other. Turbofan continues to use all float registers internally however. Bug: v8:6600 Change-Id: I47d91b8216136e57f42fd9665ed57ec631eb0374 Reviewed-on: https://chromium-review.googlesource.com/c/1352278Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Bill Budge <bbudge@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#57901}
-
- 10 Oct, 2018 1 commit
-
-
Ben L. Titzer authored
This CL refactors the implementation of WASM->JS import wrappers in order to make the wrapper code shareable. Instead of specializing to the import index, we use a tuple as the object ref in the both the import and indirect tables. The tuple allows the wrapper code to load both the calling instance and the target callable, rather than relying on code specialization. This requires some tricky codegen machinery, because WASM call descriptors expect an instance argument in a given register, yet the wrappers receive a tuple, the code generator must generate a prologue that loads the instance (and the callable), since it is not possible to express this at the graph level. R=mstarzinger@chromium.org CC=clemensh@chromium.org Change-Id: Id67e307f7f5089e776f5439a53b5aee4b76934b6 Reviewed-on: https://chromium-review.googlesource.com/c/1268237 Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#56520}
-
- 09 Oct, 2018 1 commit
-
-
Sigurd Schneider authored
Change-Id: I41b5c8e2700ebef102ffd3e7bdc9140978d971b7 Bug: v8:6666 Reviewed-on: https://chromium-review.googlesource.com/c/1264281Reviewed-by: Ben Titzer <titzer@chromium.org> Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#56471}
-
- 06 Sep, 2018 1 commit
-
-
Bill Budge authored
- Removes workarounds in test-run-native_calls for ARM and adds ARM 32-bit aliasing-aware register allocation. - Uses wasm::LinkageAllocator instead of custom allocator to avoid duplication of this logic. - Fixes a problem in wasm::LinkageAllocator with high 16 VFP regs, and makes member variable naming consistent. Bug: v8:8015 Change-Id: Ie8bb8bad06bebce2cef3da0f6ad5c59d5f3b3b36 Reviewed-on: https://chromium-review.googlesource.com/1199907Reviewed-by: Ben Titzer <titzer@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#55696}
-
- 18 Jul, 2018 1 commit
-
-
Bill Budge authored
- Modifies LinkageAllocator to understand aliasing on ARM. - Adds ability to allocate SIMD registers too. Before, these would default to stack allocated. - Modifies WasmCompiler to be platform-independent. Bug: v8:7754 Change-Id: I0c4355a44a4f409053b51ff675521a465e38aeb8 Reviewed-on: https://chromium-review.googlesource.com/1141114Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#54533}
-
- 07 May, 2018 1 commit
-
-
Andreas Haas authored
R=clemensh@chromium.org CC=titzer@chromium.org Change-Id: I4951bf7ffc8baf51225e7bef60349186811b9f76 Reviewed-on: https://chromium-review.googlesource.com/1024037 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#53020}
-
- 27 Apr, 2018 1 commit
-
-
Clemens Hammacher authored
Linkage-related methods were declared in wasm-compiler.h and implemented in wasm-linkage.cc. This required all users of e.g. wasm call descriptors to include the whole wasm compiler header. Also, some wasm linkage information is independent of turbofan and also used outside of the compiler directory. This CL splits off wasm-linkage.h (with minimal includes) and puts it in src/wasm. This allows to use that information without including compiler headers (will clean up several uses in follow-up CLs). R=mstarzinger@chromium.org, titzer@chromium.org Bug: v8:7570 Change-Id: Ifcae70b4ea7932cda30953b325c2b87c4176c598 Reviewed-on: https://chromium-review.googlesource.com/1013701Reviewed-by: Ben Titzer <titzer@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#52849}
-