summaryrefslogtreecommitdiffstats
path: root/lldb/examples/customization/bin-utils/binutils.py
Commit message (Collapse)AuthorAgeFilesLines
* Python 2/3 compat: StringIOSerge Guelton2019-03-251-2/+0
| | | | | | Differential Revision: https://reviews.llvm.org/D59582 llvm-svn: 356910
* Python 2/3 compatibility: from __future__ import print_functionSerge Guelton2019-03-211-8/+9
| | | | | | Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-8/+11
| | | | | | | | | | | | | | | | | | | | | | | *** 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
* Add an example customization directory which uses a binutils.py module to ↵Johnny Chen2011-10-281-0/+69
| | | | | | | | provide commands to print the binary representaion of an integer. llvm-svn: 143252
* Add a binutils.py which contains Python functions for displaying bit ↵Johnny Chen2011-10-281-0/+53
representation of numbers. llvm-svn: 143173
OpenPOWER on IntegriCloud