summaryrefslogtreecommitdiffstats
path: root/lldb/examples/python/performance.py
Commit message (Collapse)AuthorAgeFilesLines
* Python 2/3 compatibility: from __future__ import print_functionSerge Guelton2019-03-211-19/+21
| | | | | | Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-60/+117
| | | | | | | | | | | | | | | | | | | | | | | *** to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751
* Playing around with making performance test cases run from within python. Greg Clayton2013-04-031-25/+122
| | | | llvm-svn: 178708
* A few more tweaks to the python perf tests. Now there is a MemoryMeasurement.Greg Clayton2013-03-261-19/+60
| | | | llvm-svn: 178069
* Added a python version of the performance tests. It will be good to see if ↵Greg Clayton2013-03-231-0/+197
the overhead of python interferes at all with our performance readings. We can try things out with this script and see how things go. llvm-svn: 177811
OpenPOWER on IntegriCloud