| commit | 3d096654b910e52768d7335a0c2c7d7cd32c8bb7 | [log] [tgz] |
|---|---|---|
| author | mtklein <mtklein@chromium.org> | Tue Sep 29 10:38:59 2015 -0700 |
| committer | Commit bot <commit-bot@chromium.org> | Tue Sep 29 10:38:59 2015 -0700 |
| tree | f374580f11a84f53e339df64620b019d9bfffbda | |
| parent | 03ba61436bbcc2f0081ddc975ed00e6a0c49e67c [diff] |
update memset16/32 inlining heuristics I spent some time looking at perf.skia.org and it looks like we can do better. It is weird, weird, weird that on x86, we see three completely different behaviors: - x86 Android: inlining better for small N, custom better for large N; - Windows: inlining better for large N, custom better for small N; - other x86: inlining generally better BUG=skia:4316,chromium:516426 Committed: https://skia.googlesource.com/skia/+/b68fa409fc00ce2f38e2a0fd6f9dc2379b372481 Summaries: https://perf.skia.org/#4179 All traces, log scale: https://perf.skia.org/#4180 TBR=reed@google.com No public API changes. Review URL: https://codereview.chromium.org/1357193002