| commit | 9c4ff80d9b76e1bda532fb9182f66f67cfc95324 | [log] [tgz] |
|---|---|---|
| author | mtklein <mtklein@chromium.org> | Tue Jun 03 13:56:54 2014 -0700 |
| committer | Commit bot <commit-bot@chromium.org> | Tue Jun 03 13:56:54 2014 -0700 |
| tree | f14cf81529b67be5961ecb5317a0262c3ad010fe | |
| parent | 182a631e989b9b6c58e4342c9f661682361446ed [diff] |
DM: go back to memcmp for BitmapsEqual Even when autovectorized, using MaxComponentDifference is slower than memcmp. And debug builds (most runs of DM) will never even be autovectorized. DM::MaxComponentDifference is the top function on DM profile, and memcmp moves to ~20th. BUG=skia: R=halcanary@google.com, mtklein@google.com Author: mtklein@chromium.org Review URL: https://codereview.chromium.org/315743002