wasm/AsmJsZenGarden in wasm failing on chromium.perf/Linux Perf |
|||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of ashleymarie@google.com wasm/AsmJsZenGarden in wasm failing on chromium.perf/Linux Perf Builders failed on: - Linux Perf: https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf
,
Apr 11 2018
📍 Found significant differences after each of 3 commits. https://pinpoint-dot-chromeperf.appspot.com/job/16318d18c40000 [wasm] Clean up SetBlockType by clemensh@chromium.org https://chromium.googlesource.com/v8/v8/+/04246dcc1b26f538127187311eba66bbf1bd2ed8 [heap] Move initial objects into RO_SPACE by delphick@chromium.org https://chromium.googlesource.com/v8/v8/+/f8ae62fe14f80fb0f071d4e9a83cb9aa677ccb29 [wasm] Merge the WasmContext into WasmInstanceObject by titzer@chromium.org https://chromium.googlesource.com/v8/v8/+/a6d974fe00df34e866abc1150294a5bbf1d42535 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Apr 16 2018
This should be fixed by: https://chromium-review.googlesource.com/c/v8/v8/+/1004294 |
|||
►
Sign in to add a comment |
|||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Apr 9 2018