Make V8 WASM-version-0xC compatible |
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: Support the new binary format! What is the expected behavior? What went wrong? It doesn't support the new format! Did this work before? N/A Chrome version: 53.0.2785.116 Channel: stable OS Version: Flash Version: Shockwave Flash 23.0 r0
,
Sep 28 2016
,
Sep 28 2016
,
Sep 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/70d9edc46f1bfb87ef84807355098d15bf94a664 commit 70d9edc46f1bfb87ef84807355098d15bf94a664 Author: mtrofin <mtrofin@chromium.org> Date: Tue Sep 27 20:11:18 2016 [wasm] Update incrementer.wasm example binary module to version 0xC. Note that this CL depends on a V8 CL that implements binary version 0xC for WASM, which will land momentarily. R=titzer@chromium.org,jochen@chromium.org BUG=chromium:575167, chromium:650655 Review-Url: https://codereview.chromium.org/2370963003 Cr-Commit-Position: refs/heads/master@{#421312} [modify] https://crrev.com/70d9edc46f1bfb87ef84807355098d15bf94a664/third_party/WebKit/LayoutTests/TestExpectations [modify] https://crrev.com/70d9edc46f1bfb87ef84807355098d15bf94a664/third_party/WebKit/LayoutTests/http/tests/wasm/incrementer.wasm
,
Sep 28 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Sep 27 2016