summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/top-level/TestTopLevelExprs.py
diff options
context:
space:
mode:
authorTobias Grosser <tobias@grosser.es>2016-06-23 22:17:27 +0000
committerTobias Grosser <tobias@grosser.es>2016-06-23 22:17:27 +0000
commit522478d2c0a1162a42d35faf5c3bfaaa4ff450ab (patch)
tree2c1619df8b24da1a0358a210ca036ce635d98626 /lldb/packages/Python/lldbsuite/test/expression_command/top-level/TestTopLevelExprs.py
parent64adae59f3b95ca64464c69081a1c1711f9ddee3 (diff)
downloadbcm5719-llvm-522478d2c0a1162a42d35faf5c3bfaaa4ff450ab.tar.gz
bcm5719-llvm-522478d2c0a1162a42d35faf5c3bfaaa4ff450ab.zip
clang-tidy: Add llvm namespace comments
llvm commonly adds a comment to the closing brace of a namespace to indicate which namespace is closed. clang-tidy provides with llvm-namespace-comment a handy tool to check for this habit. We use it to ensure we consitently use namespace comments in Polly. There are slightly different styles in how namespaces are closed in LLVM. As there is no large difference between the different comment styles we go for the style clang-tidy suggests by default. To reproduce this fix run: for i in `ls tools/polly/lib/*/*.cpp`; \ clang-tidy -checks='-*,llvm-namespace-comment' -p build $i -fix \ -header-filter=".*"; \ done This cleanup was suggested by Eugene Zelenko <eugene.zelenko@gmail.com> in http://reviews.llvm.org/D21488 and was split out to increase readability. llvm-svn: 273621
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/top-level/TestTopLevelExprs.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud