[Mlir-commits] [llvm] [mlir] [mlir] `HasParallelRegion` means region may be parallel (PR #231372)

[llvmlistbot at llvm.org]

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 h -- mlir/include/mlir/Dialect/GPU/IR/GPUDialect.h mlir/include/mlir/Dialect/OpenMP/OpenMPDialect.h mlir/include/mlir/Interfaces/LoopLikeInterface.h --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/include/mlir/Interfaces/LoopLikeInterface.h b/mlir/include/mlir/Interfaces/LoopLikeInterface.h
index 1ccfcef7e..ad83fc50d 100644
--- a/mlir/include/mlir/Interfaces/LoopLikeInterface.h
+++ b/mlir/include/mlir/Interfaces/LoopLikeInterface.h
@@ -39,8 +39,8 @@ namespace OpTrait {
 // parallel execution semantics. Whether it executes in parallel may depend on
 // the operation's attributes or enclosing context. Transformations must account
 // for possible parallel execution unless they can prove sequential execution.
-// For example, hoisting a buffer allocation out of the region may cause parallel
-// executions to share a buffer that was previously private.
+// For example, hoisting a buffer allocation out of the region may cause
+// parallel executions to share a buffer that was previously private.
 template <typename ConcreteType>
 class HasParallelRegion : public TraitBase<ConcreteType, HasParallelRegion> {
 public:

``````````

</details>


https://github.com/llvm/llvm-project/pull/231372