Switch compiler to LLVM/MLIR formatting style (#14181)
The high-level goal is to better align with the LLVM/MLIR coding style
and allow for easier prototyping and code movement between the two. The
`runtime/` and `tools/` directories still use the `Google` style, as the
LLVM config is not always preferred for C code, and we do not expect
much sharing/movement of this code with LLVM.
This adds a new `.clang-format` file local to the `compiler/` directory
with the same formatting settings as those used by MLIR. The only
divergence is not having special case for include ordering that places
llvm includes last. It also reformats this directory using the new
formatting config.
I used the following command to reformat the code:
```shell
cd compiler
fd -e h -e cpp -e cc -e c | xargs clang-format -i
```
I plan to add this commit to `.git-blame-ignore-revs` in a follow-up PR,
once the final commit SHA is known.
Issue: https://github.com/openxla/iree/issues/12866
diff --git a/.clang-format b/.clang-format
index 0c40907..8514ff8 100644
--- a/.clang-format
+++ b/.clang-format
@@ -4,6 +4,6 @@
# See https://llvm.org/LICENSE.txt for license information.
# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-# IREE's runtime follows Google style while its compiler follows mostly LLVM
-# style (for naming/etc.) but using Google formatting.
+# IREE's runtime follows Google style while its compiler follows the
+# LLVM/MLIR variable naming and formatting style.
BasedOnStyle: Google
