From: Julian Brown <julian@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <fortran@gcc.gnu.org>, Tobias Burnus <tobias@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: [PATCH 0/6] OpenMP 5.0: Fortran "declare mapper" support
Date: Wed, 1 Jun 2022 11:39:18 -0700 [thread overview]
Message-ID: <cover.1654107784.git.julian@codesourcery.com> (raw)
This patch series implements "declare mapper" support for Fortran,
following on from the C and C++ support for same in the currently
in-review series posted here:
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591973.html
Further commentary on individual patches. Tested with offloading to NVPTX.
OK? (Pending rework of the patch series it depends on?)
Thanks,
Julian
Julian Brown (6):
Fortran: Typo/unicode-o fixes
OpenMP: Templatize omp_mapper_list
OpenMP: Rename strip_components_and_deref to omp_get_root_term
OpenMP: Tweak NOP handling in in omp_get_root_term and
accumulate_sibling_list
OpenMP: Pointers and member mappings
OpenMP: Fortran "!$omp declare mapper" support
gcc/c-family/c-common.h | 4 +-
gcc/c-family/c-omp.cc | 2 +-
gcc/c/c-decl.cc | 6 +-
gcc/cp/semantics.cc | 8 +-
gcc/fortran/dump-parse-tree.cc | 5 +-
gcc/fortran/f95-lang.cc | 7 +
gcc/fortran/gfortran.h | 55 +-
gcc/fortran/match.cc | 8 +-
gcc/fortran/match.h | 1 +
gcc/fortran/module.cc | 252 +++++-
gcc/fortran/openmp.cc | 296 ++++++-
gcc/fortran/parse.cc | 9 +-
gcc/fortran/resolve.cc | 2 +
gcc/fortran/st.cc | 2 +-
gcc/fortran/symbol.cc | 16 +
gcc/fortran/trans-decl.cc | 30 +-
gcc/fortran/trans-openmp.cc | 778 +++++++++++++++++-
gcc/fortran/trans-stmt.h | 1 +
gcc/fortran/trans.h | 3 +
gcc/gimplify.cc | 422 ++++++++--
gcc/omp-general.h | 32 +-
.../gfortran.dg/gomp/declare-mapper-1.f90 | 71 ++
.../gfortran.dg/gomp/declare-mapper-14.f90 | 26 +
.../gfortran.dg/gomp/declare-mapper-16.f90 | 22 +
.../gfortran.dg/gomp/declare-mapper-5.f90 | 45 +
gcc/tree-pretty-print.cc | 3 +
include/gomp-constants.h | 5 +-
.../libgomp.fortran/declare-mapper-10.f90 | 40 +
.../libgomp.fortran/declare-mapper-11.f90 | 38 +
.../libgomp.fortran/declare-mapper-12.f90 | 33 +
.../libgomp.fortran/declare-mapper-13.f90 | 49 ++
.../libgomp.fortran/declare-mapper-15.f90 | 24 +
.../libgomp.fortran/declare-mapper-17.f90 | 92 +++
.../libgomp.fortran/declare-mapper-18.f90 | 46 ++
.../libgomp.fortran/declare-mapper-19.f90 | 29 +
.../libgomp.fortran/declare-mapper-2.f90 | 32 +
.../libgomp.fortran/declare-mapper-20.f90 | 29 +
.../libgomp.fortran/declare-mapper-3.f90 | 33 +
.../libgomp.fortran/declare-mapper-4.f90 | 36 +
.../libgomp.fortran/declare-mapper-6.f90 | 28 +
.../libgomp.fortran/declare-mapper-7.f90 | 29 +
.../libgomp.fortran/declare-mapper-8.f90 | 115 +++
.../libgomp.fortran/declare-mapper-9.f90 | 27 +
.../libgomp.fortran/map-subarray.f90 | 33 +
.../libgomp.fortran/map-subcomponents.f90 | 32 +
.../libgomp.fortran/struct-elem-map-1.f90 | 10 +-
46 files changed, 2702 insertions(+), 164 deletions(-)
create mode 100644 gcc/testsuite/gfortran.dg/gomp/declare-mapper-1.f90
create mode 100644 gcc/testsuite/gfortran.dg/gomp/declare-mapper-14.f90
create mode 100644 gcc/testsuite/gfortran.dg/gomp/declare-mapper-16.f90
create mode 100644 gcc/testsuite/gfortran.dg/gomp/declare-mapper-5.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-10.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-11.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-12.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-13.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-15.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-17.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-18.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-19.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-2.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-20.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-3.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-4.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-6.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-7.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-8.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/declare-mapper-9.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/map-subarray.f90
create mode 100644 libgomp/testsuite/libgomp.fortran/map-subcomponents.f90
--
2.29.2
next reply other threads:[~2022-06-01 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 18:39 Julian Brown [this message]
2022-06-01 18:39 ` [PATCH 1/6] Fortran: Typo/unicode-o fixes Julian Brown
2022-12-23 10:53 ` Julian Brown
2022-06-01 18:39 ` [PATCH 2/6] OpenMP: Templatize omp_mapper_list Julian Brown
2022-06-01 18:39 ` [PATCH 3/6] OpenMP: Rename strip_components_and_deref to omp_get_root_term Julian Brown
2022-06-01 18:39 ` [PATCH 4/6] OpenMP: Tweak NOP handling in in omp_get_root_term and accumulate_sibling_list Julian Brown
2022-06-01 18:40 ` [PATCH 5/6] OpenMP: Pointers and member mappings Julian Brown
2022-06-01 18:40 ` [PATCH 6/6] OpenMP: Fortran "!$omp declare mapper" support Julian Brown
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=cover.1654107784.git.julian@codesourcery.com \
--to=julian@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tobias@codesourcery.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).