aboutsummaryrefslogtreecommitdiff
path: root/android_bench_suite
AgeCommit message (Collapse)Author
2019-03-08Swap READMEs to markdownGeorge Burgess IV
Suggested by vapier@ in I7daf1cbe93f8809e469698d7772a6c68baf9e194 This ignores README.chromium, since I'm unsure if that's a special name that some tool somewhere relies on. I skimmed over all of these in gitiles (as you can probably tell by the 35 patch sets :) ) and fixed the issues that jumped out at me. I'm sure that some remain somewhere, but I think I got the majority of them. An attempt has been made to make all files roughly follow the rules here: https://github.com/google/styleguide/blob/gh-pages/docguide/style.md Note that not all of them have super meaningful introductions with ToCs/etc, but the rest should be relatively consistent with that guide. BUG=None TEST=Manual inspection Change-Id: I158048d972d49966e3b8ff1e07e5429928edb339 Reviewed-on: https://chromium-review.googlesource.com/1504893 Commit-Ready: George Burgess <gbiv@chromium.org> Tested-by: George Burgess <gbiv@chromium.org> Reviewed-by: George Burgess <gbiv@chromium.org>
2017-07-21Modify the method to patch synthmarkZhizhou Yang
The old way to patch synthmark kept a .mk file which will cause build failing. Have put the .mk file patch into a diff file so that Android building system will not see a .mk file here. BUG=None TEST=Checkbuild succeeded with this patched to external/toolchain-utils on Android side. Change-Id: I704aa02d9ca91098727786f053aeb26e989bd481 Reviewed-on: https://chromium-review.googlesource.com/581869 Commit-Ready: Zhizhou Yang <zhizhouy@chromium.org> Tested-by: Zhizhou Yang <zhizhouy@chromium.org> Reviewed-by: George Burgess <gbiv@chromium.org>
2017-07-18Add Android toolchain benchmark suiteZhizhou Yang
Add Android toolchain benchmark suite into toolchain-utils, which will be synced to Android Repository. BUG=None TEST=None Change-Id: Iee1ba9aa21a99ff6ce8d669c59d53af6e953703c Reviewed-on: https://chromium-review.googlesource.com/569481 Commit-Ready: Zhizhou Yang <zhizhouy@chromium.org> Tested-by: Zhizhou Yang <zhizhouy@chromium.org> Reviewed-by: Luis Lozano <llozano@chromium.org>