github-actions[bot] wrote:
<!--LLVM CODE FORMAT COMMENT: {clang-format}-->
:warning: C/C++ code formatter, clang-format found issues in your code.
:warning:
<details>
<summary>
You can test this locally with the following command:
</summary>
``````````bash
git-clang-format --diff origin/main HEAD --extensions cpp --
mlir/lib/Bindings/Python/IRCore.cpp mlir/lib/Bindings/Python/MainModule.cpp
--diff_from_common_commit
``````````
:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:
</details>
<details>
<summary>
View the diff from clang-format here.
</summary>
``````````diff
diff --git a/mlir/lib/Bindings/Python/IRCore.cpp
b/mlir/lib/Bindings/Python/IRCore.cpp
index 16d1e74f7..95603c31a 100644
--- a/mlir/lib/Bindings/Python/IRCore.cpp
+++ b/mlir/lib/Bindings/Python/IRCore.cpp
@@ -2021,7 +2021,6 @@ void PyBlockArgument::bindDerived(ClassTy &c) {
nanobind::arg("loc"), "Sets the location of this block argument.");
}
-
PyBlockArgument PyBlockArgumentList::getRawElement(intptr_t pos) const {
MlirValue argument = mlirBlockGetArgument(block, pos);
return PyBlockArgument(operation, argument);
@@ -2208,6 +2207,4 @@ void PyOpAttributeMap::forEachAttr(
} // namespace python
} // namespace mlir
-NB_MODULE(_mlirPythonSupport, m) {
- m.doc() = "MLIR Python Support Extension";
-}
\ No newline at end of file
+NB_MODULE(_mlirPythonSupport, m) { m.doc() = "MLIR Python Support Extension"; }
\ No newline at end of file
``````````
</details>
https://github.com/llvm/llvm-project/pull/174043
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
