From: Tobias Burnus <tburnus@baylibre.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [Patch] OpenMP/Fortran: Fix defaultmap(none) issue with dummy procedures [PR114283]
Date: Tue, 12 Mar 2024 12:26:50 +0100 [thread overview]
Message-ID: <7cfeed83-761f-49e4-a431-4586b82afa00@baylibre.com> (raw)
In-Reply-To: <Ze7bUJnwQ5xu6IgH@tucnak>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
Jakub Jelinek wrote:
> So firstprivate clause handling remaps them then if declare target indirect
> is used? If so, the patch looks reasonable to me.
[I have now updated the patch to turn the testcase to ensure
that is also keeps works at runtime.]
OpenMP leaves it a bit open when the remapping has to happen,
but one can construct cases – in particular with unified-shared memory –
where it is not possible to do this upon entry to a target region.
Thus, it has to be done when the function is invoked, e.g.
i = (*g) ();
is turned (in the target region but only on the device side) into
i = (*GOMP_target_map_indirect_ptr (g)) ();
Thus, as long as the host pointer value is transferred to the device,
it works – as the lookup is done on the device side. Directly using a
device address (remap when mapping to the target) will also not shorten
the lookup, i.e. there is no need for it.
Does it still look reasonable to you?
Tobias
PS: The current OpenMP specification, it is listed mainly described via
the glossary (newest change is the addition of dummy procedure):
"indirect device invocation – An indirect call to the _device_ version of
a _procedure_ on a _device_ other than the _host-device_, through a
function pointer (C/C++), a pointer to a member function (C++), a dummy
procedure (Fortran), or a procedure pointer (Fortran) that refers to the
host version of the _procedure_."
[-- Attachment #2: dummyproc-v2.diff --]
[-- Type: text/x-patch, Size: 3176 bytes --]
OpenMP/Fortran: Fix defaultmap(none) issue with dummy procedures [PR114283]
Dummy procedures look similar to variables but aren't - neither in Fortran
nor in OpenMP. As the middle end sees PARM_DECLs, mark them as predetermined
firstprivate for mapping (as already done in gfc_omp_predetermined_sharing).
This does not address the isses related to procedure pointers, which are
still discussed on spec level [see PR].
PR fortran/114283
gcc/fortran/ChangeLog:
* trans-openmp.cc (gfc_omp_predetermined_mapping): Map dummy
procedures as firstprivate.
libgomp/ChangeLog:
* testsuite/libgomp.fortran/declare-target-indirect-4.f90: New test.
gcc/fortran/trans-openmp.cc | 9 +++++
.../libgomp.fortran/declare-target-indirect-4.f90 | 43 ++++++++++++++++++++++
2 files changed, 52 insertions(+)
diff --git a/gcc/fortran/trans-openmp.cc b/gcc/fortran/trans-openmp.cc
index a2bf15665b3..1dba47126ed 100644
--- a/gcc/fortran/trans-openmp.cc
+++ b/gcc/fortran/trans-openmp.cc
@@ -343,6 +343,15 @@ gfc_omp_predetermined_mapping (tree decl)
&& GFC_DECL_SAVED_DESCRIPTOR (decl)))
return OMP_CLAUSE_DEFAULTMAP_TO;
+ /* Dummy procedures aren't considered variables by OpenMP, thus are
+ disallowed in OpenMP clauses. They are represented as PARM_DECLs
+ in the middle-end, so return OMP_CLAUSE_DEFAULTMAP_FIRSTPRIVATE here
+ to avoid complaining about their uses with defaultmap(none). */
+ if (TREE_CODE (decl) == PARM_DECL
+ && TREE_CODE (TREE_TYPE (decl)) == POINTER_TYPE
+ && TREE_CODE (TREE_TYPE (TREE_TYPE (decl))) == FUNCTION_TYPE)
+ return OMP_CLAUSE_DEFAULTMAP_FIRSTPRIVATE;
+
/* These are either array or derived parameters, or vtables. */
if (VAR_P (decl) && TREE_READONLY (decl)
&& (TREE_STATIC (decl) || DECL_EXTERNAL (decl)))
diff --git a/libgomp/testsuite/libgomp.fortran/declare-target-indirect-4.f90 b/libgomp/testsuite/libgomp.fortran/declare-target-indirect-4.f90
new file mode 100644
index 00000000000..43f4295494c
--- /dev/null
+++ b/libgomp/testsuite/libgomp.fortran/declare-target-indirect-4.f90
@@ -0,0 +1,43 @@
+! { dg-additional-options "-fdump-tree-gimple" }
+
+! PR fortran/114283
+
+! { dg-final { scan-tree-dump "#pragma omp parallel shared\\(i\\) if\\(0\\) default\\(none\\) firstprivate\\(g\\)" "gimple" } }
+! { dg-final { scan-tree-dump "#pragma omp target num_teams\\(-2\\) thread_limit\\(0\\) firstprivate\\(h\\) map\\(from:j \\\[len: 4\\\]\\) defaultmap\\(none\\)" "gimple" } }
+
+
+module m
+ implicit none (type, external)
+ !$omp declare target indirect enter(f1, f2)
+contains
+ integer function f1 ()
+ f1 = 99
+ end
+ integer function f2 ()
+ f2 = 89
+ end
+end module m
+
+use m
+implicit none (type, external)
+call sub1(f1)
+call sub2(f2)
+contains
+ subroutine sub1(g)
+ procedure(integer) :: g
+ integer :: i
+ !$omp parallel default(none) if(.false.) shared(i)
+ i = g ()
+ !$omp end parallel
+ if (i /= 99) stop 1
+ end
+
+ subroutine sub2(h)
+ procedure(integer) :: h
+ integer :: j
+ !$omp target defaultmap(none) map(from:j)
+ j = h ()
+ !$omp end target
+ if (j /= 89) stop 1
+ end
+end
prev parent reply other threads:[~2024-03-12 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 10:07 Tobias Burnus
2024-03-11 10:22 ` Jakub Jelinek
2024-03-12 11:26 ` Tobias Burnus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7cfeed83-761f-49e4-a431-4586b82afa00@baylibre.com \
--to=tburnus@baylibre.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).