[flang-commits] [flang] [llvm] [mlir] [Flang][OpenMP]Handling restrictions of using Memory-Order-Clause with Atomic-Clause (PR #199636)

[via flang-commits]

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 -- flang/lib/Lower/OpenMP/Atomic.cpp flang/lib/Semantics/check-omp-atomic.cpp llvm/lib/Frontend/OpenMP/OMPIRBuilder.cpp mlir/lib/Dialect/OpenMP/IR/OpenMPDialect.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/flang/lib/Lower/OpenMP/Atomic.cpp b/flang/lib/Lower/OpenMP/Atomic.cpp
index 5aa073fbb..b80564fdd 100644
--- a/flang/lib/Lower/OpenMP/Atomic.cpp
+++ b/flang/lib/Lower/OpenMP/Atomic.cpp
@@ -252,7 +252,7 @@ makeValidForAction(std::optional<mlir::omp::ClauseMemoryOrderKind> memOrder,
   // The individual sub-operations (read/write/update) inside the capture
   // will have their orderings handled separately.
   if (isCapture)
-     return memOrder;
+    return memOrder;
 
   // Avaliable orderings: acquire, acq_rel, relaxed, release, seq_cst
 

``````````

</details>


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