Subzero: Use a "known" version of clang-format.

There are two problems with "make format" and "make format-diff" in
Makefile.standalone:

1. You have to make sure clang-format and clang-format-diff.py are
available in $PATH.

2. Different users may have different versions installed (even for the
same user on different machines), leading to whitespace wars.  Can't we
all just get along?

Since the normal LLVM build that Subzero depends on also exposes and
builds clang-format and friends, we might as well use it.  The
clang-format binary is found in $LLVM_BIN_PATH, and clang-format-diff.py
is found relative to $LLVM_SRC_PATH.  As long as the user's LLVM build
is fairly up to date, whitespace wars are unlikely.

Given this, there's a much higher incentive to use "make format"
regularly instead of "make format-diff".  In particular, inline comments
on variable/field declaration lists can get lined up more nicely by
looking at the entire context, rather than the small diff window.

BUG= none
R=jvoung@chromium.org

Review URL: https://codereview.chromium.org/877003003

crosstest/test_calling_conv.cpp

diff --git a/crosstest/test_calling_conv.cpp b/crosstest/test_calling_conv.cpp
index 57bfa6f..e7fa616 100644
--- a/crosstest/test_calling_conv.cpp
+++ b/crosstest/test_calling_conv.cpp
@@ -75,9 +75,9 @@
 }
 
 void __attribute__((noinline))
-callee_vlvlivfvdviv(v4f32 arg1, int64_t arg2, v4f32 arg3, int64_t arg4, int arg5,
-                    v4f32 arg6, float arg7, v4f32 arg8, double arg9, v4f32 arg10,
-                    int arg11, v4f32 arg12) {
+callee_vlvlivfvdviv(v4f32 arg1, int64_t arg2, v4f32 arg3, int64_t arg4,
+                    int arg5, v4f32 arg6, float arg7, v4f32 arg8, double arg9,
+                    v4f32 arg10, int arg11, v4f32 arg12) {
   switch (ArgNum) {
     HANDLE_ARG(1);
     HANDLE_ARG(2);