From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] OpenMP: Add omp_all_memory support to Fortran
Date: Tue, 17 May 2022 09:40:26 +0200 [thread overview]
Message-ID: <YoNRagw8WpXYPQTT@tucnak> (raw)
In-Reply-To: <c7c353a8-1a16-c6b1-92c2-83bbce6b7d9f@codesourcery.com>
On Fri, May 13, 2022 at 10:51:56PM +0200, Tobias Burnus wrote:
> This adds omp_all_memory handling to Fortran, following C/C++ and shamelessly coping
> the C testcases and adapting them to Fortran.
>
> OK?
>
> Tobias
> -----------------
> Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
> OpenMP: Add omp_all_memory support to Fortran
>
> Fortran part to the C/C++/backend implementation
> r13-337-g7f78783dbedca0183d193e475262ca3c489fd365
>
> gcc/fortran/ChangeLog:
>
> * dump-parse-tree.cc (show_omp_namelist): Handle omp_all_memory.
> * openmp.cc (gfc_match_omp_variable_list, gfc_match_omp_depend_sink,
> gfc_match_omp_clauses, resolve_omp_clauses): Likewise.
> * trans-openmp.cc (gfc_trans_omp_clauses, gfc_trans_omp_depobj):
> Likewise.
> * resolve.cc (resolve_symbol): Reject it as symbol.
>
> libgomp/ChangeLog:
>
> * libgomp.texi (OpenMP 5.1): Set omp_all_memory to 'Y'.
> * testsuite/libgomp.fortran/depend-5.f90: New test.
> * testsuite/libgomp.fortran/depend-6.f90: New test.
> * testsuite/libgomp.fortran/depend-7.f90: New test.
>
> gcc/testsuite/ChangeLog:
>
> * gfortran.dg/gomp/all-memory-1.f90: New test.
> * gfortran.dg/gomp/all-memory-2.f90: New test.
> * gfortran.dg/gomp/all-memory-3.f90: New test.
LGTM, thanks.
Jakub
prev parent reply other threads:[~2022-05-17 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 20:51 Tobias Burnus
2022-05-17 7:40 ` Jakub Jelinek [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=YoNRagw8WpXYPQTT@tucnak \
--to=jakub@redhat.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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).