summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-10-17 21:23:35 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-10-17 21:23:35 +0000
commita0f6c6434cc4fa98c83e57c9fb6608fb3248dc48 (patch)
tree44954aec0365925cd72ead42b695999c639d87cf
parent9a335b6eda4fa619c37ec23f2c8bce20c9207eb2 (diff)
downloadbcm5719-llvm-a0f6c6434cc4fa98c83e57c9fb6608fb3248dc48.tar.gz
bcm5719-llvm-a0f6c6434cc4fa98c83e57c9fb6608fb3248dc48.zip
[test] Add a .clang-format file for the shell test.
The API tests have a .clang-format file that disables formatting altogether. While this is needed for some tests, it also leads to inconsistency between test files. The shell tests suffer from a similar problem: a test with a source-file extension (.c, .cpp) will get formatted, potentially breaking up lines and leading to invalid RUN commands. Rather than completely disabling formatting here, I propose to not enforce a line limit instead. That way tests will be consistent, but you can still have long run commands (as is not uncommon in LLVM either) and use breakpoints with patters that extend beyond 80 cols. Differential revision: https://reviews.llvm.org/D69058 llvm-svn: 375172
-rw-r--r--lldb/test/Shell/.clang-format3
1 files changed, 3 insertions, 0 deletions
diff --git a/lldb/test/Shell/.clang-format b/lldb/test/Shell/.clang-format
new file mode 100644
index 00000000000..e032e3d4702
--- /dev/null
+++ b/lldb/test/Shell/.clang-format
@@ -0,0 +1,3 @@
+BasedOnStyle: LLVM
+# We don't want clang-format to introduce line breaks in RUN commands.
+ColumnLimit: 999
OpenPOWER on IntegriCloud