forked from OSchip/llvm-project
6f56a586c5
Summary: Any change to clang-format is tested with the unit tests, However sometimes the better approach is to run it over a very large fully formatted source tree and then inspect the differences. This seems to be a source of many of the regressions found by @krasimir and by @sylvestre.ledru and @Abpostelnicu who run it over the Mozilla sources, but often these regressions are only found after changes have been committed. LLVM itself would be a good dog-fooding candidate for similar tests except such a large proportion of the tree is not 100% clang formatted, as such you are never aware if the change comes from a change to clang-format or just because the tree has not been formatted first. The following review is for a small python tool which scans the whole of the LLVM source tree and counts the number of files which have one or more clang-format violations. This revision contains the tool and the output from the initial run of the tool and the generated documentation which looks like the following Reviewers: krasimir, JakeMerdichAMD, sammccall, curdeius, bollu, alexshap, jdoerfert, DavidTruby, sscalpone Reviewed By: curdeius Subscribers: dschuff, aheejin, fedor.sergeev, ilya-biryukov, simoncook, cryptoad, arphaman, jfb, kadircet, mstorsjo, s.egerton, usaxena95, aartbik, phosek, sstefan1, cfe-commits, sylvestre.ledru, Abpostelnicu, krasimir Tags: #clang, #clang-format Differential Revision: https://reviews.llvm.org/D80627 |
||
---|---|---|
.. | ||
dump_ast_matchers.py | ||
dump_format_style.py | ||
generate_formatted_state.py |