- 25 Jan, 2022 1 commit
-
-
Manos Koukoutos authored
Change-Id: I1289fcab6c4812868258b14492d85bad20ae7e9f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3406536Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/main@{#78755}
-
- 14 Jun, 2021 1 commit
-
-
Manos Koukoutos authored
Additionally, reduce the maximum times a loop can be unrolled to 5. Bug: v8:11298 Change-Id: Ia3cc5955c91e70abf388e08bdc37aba998b34b93 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2953297Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#75118}
-
- 01 Mar, 2021 2 commits
-
-
Manos Koukoutos authored
Bug: v8:11298 Change-Id: I064cfda6744f01099f70aab37cfd620afaff1262 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2726505Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#73102}
-
Manos Koukoutos authored
During loop exploration implemented for wasm loop unrolling, we can exit early if we already know that the loop is too large to unroll. Bug: v8:11298 Change-Id: I213edef995b58500d07d428f1f1a725132dd44e5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2726501Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Cr-Commit-Position: refs/heads/master@{#73095}
-
- 24 Feb, 2021 1 commit
-
-
Manos Koukoutos authored
Design doc: https://docs.google.com/document/d/1AsUCqslMUB6fLdnGq0ZoPk2kn50jIJAWAL77lKXXP5g/ Currently, wasm loop unrolling is disabled by default. We intend to further investigate its compilation time cost and running time benefits before enabling it. Additional changes: - Introduce LoopFinder::FindUnnestedLoopFromHeader() as a lightweight loop analysis. - Move EliminateLoopExit into LoopPeeling and expose it. - Introduce loop_info_ field into WasmGraphBuildingInterface, fill it up in Loop(). - Break after encountering the first loop in BuildNestedLoopExits. - Introduce struct WasmLoopInfo. A WasmLoopInfo vector is instantiated in ExecuteTurbofanWasmCompilation, passed to BuildGraphForWasmFunction to be filled up by WasmGraphBuildingInterface, and then passed to GenerateCodeForWasmFunction to be used in WasmLoopUnrollingPhase. - Introduce WasmLoopUnrollingPhase and insert it into the wasm compilation pipeline. - Fix an issue where exception values were not wrapped in WasmGraphBuilderInterface. - Update --wasm-loop-unrolling flag description. Bug: v8:11298 Change-Id: I4b57cf2ea8520931f60769f843ffd57b3ca6399b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2697349 Commit-Queue: Manos Koukoutos <manoskouk@chromium.org> Reviewed-by:
Clemens Backes <clemensb@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Nico Hartmann <nicohartmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#73009}
-