| commit | f2509381bdd9e712919418f7ebe831f974208154 | [log] [tgz] |
|---|---|---|
| author | mtklein <mtklein@chromium.org> | Wed May 04 14:02:14 2016 -0700 |
| committer | Commit bot <commit-bot@chromium.org> | Wed May 04 14:02:14 2016 -0700 |
| tree | d17a15c24a12d6c805ef04c938016c3e1a59f864 | |
| parent | b37c68ad42ae7880e702649a01655165c7e12acc [diff] |
Now we're on MSVC 2015, try using std::chrono for timing again. 2015's std::chrono::high_resolution_clock should have a precision equal to our old custom code. Tested this locally on Windows 10 and Mac (the two affected platforms). Long term SkTime::GetNSecs() can probably be phased out for direct <chrono> use. BUG=skia: GOLD_TRYBOT_URL= https://gold.skia.org/search2?unt=true&query=source_type%3Dgm&master=false&issue=1950173002 Review-Url: https://codereview.chromium.org/1950173002