https://github.com/ergawy updated
https://github.com/llvm/llvm-project/pull/126026
>From f946ee6c8c34819d36818dbc3a5430c8b9e8a059 Mon Sep 17 00:00:00 2001
From: ergawy
Date: Wed, 5 Feb 2025 23:31:15 -0600
Subject: [PATCH] [flang][OpenMP] Upstream first part of `do concurrent`
mapping
This PR
https://github.com/ergawy updated
https://github.com/llvm/llvm-project/pull/126026
>From 477b5b8d22ddd7b0a873519c8cc16b0e4a3c81ca Mon Sep 17 00:00:00 2001
From: ergawy
Date: Wed, 5 Feb 2025 23:31:15 -0600
Subject: [PATCH] [flang][OpenMP] Upstream first part of `do concurrent`
mapping
This PR
https://github.com/ergawy created
https://github.com/llvm/llvm-project/pull/127478
Upstreams the next part of `do concurrent` to OpenMP mapping pass (from
AMD's ROCm implementation). See
https://github.com/llvm/llvm-project/pull/126026 for more context.
This PR add loop nest detection logic. T
@@ -0,0 +1,104 @@
+//===- DoConcurrentConversion.cpp -- map `DO CONCURRENT` to OpenMP loops
--===//
+//
+// Part of the LLVM Project, under the Apache License v2.0 with LLVM
Exceptions.
+// See https://llvm.org/LICENSE.txt for license information.
+// SPDX-License-Identifier: Ap
ergawy wrote:
Thanks @skatrak and @bhandarkar-pranav for the approval.
@kiranchandramohan @clementval I think there is a pretty simple solution that
enables us to mark multi-range loop nests. I think we can add an optional
attribute to the `fir::DoLoopOp` to store the loop nest depth: `nest_de
ergawy wrote:
@clementval @jeanPerier can you please take a look at the PR and
@kiranchandramohan's comment above? 🙏
https://github.com/llvm/llvm-project/pull/127595
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bi
ergawy wrote:
@kiranchandramohan @clementval thanks for your comments (and sorry for the late
response, I was off yesterday).
Sure, we can works on a multi-range loop op in FIR, our team did not write the
current loop op definition so I was working with what I have.
Just to be on the same pag
https://github.com/ergawy updated
https://github.com/llvm/llvm-project/pull/127595
>From 2e89efa197e7a5d3c27e33795781b1c25a123a8c Mon Sep 17 00:00:00 2001
From: ergawy
Date: Wed, 5 Feb 2025 23:31:15 -0600
Subject: [PATCH 1/2] [flang][OpenMP] Upstream first part of `do concurrent`
mapping
This
ergawy wrote:
> Extending the current fir.do_loop operation to model multi-block loop bodies
> is not recommended, I think. It is there to model structured fortran loops.
> If you want to handle multi-block loop bodies you will need a new operation.
If it is ok, let's postpone this issue until
https://github.com/ergawy edited
https://github.com/llvm/llvm-project/pull/127634
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
ergawy wrote:
> LLVM Buildbot has detected a new failure on builder `ppc64-flang-aix` running
> on `ppc64-flang-aix-test` while building `clang,flang` at step 6
> "test-build-unified-tree-check-flang".
>
> Full details are available at:
> https://lab.llvm.org/buildbot/#/builders/201/builds/39
https://github.com/ergawy edited
https://github.com/llvm/llvm-project/pull/127635
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
101 - 112 of 112 matches
Mail list logo