From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran/OpenMP: Add support for OpenMP 5.1 masked construct (was: Re: [committed] openmp: Add support for OpenMP 5.1 masked construct)
Date: Mon, 16 Aug 2021 09:17:56 +0200 [thread overview]
Message-ID: <20210816071756.GT2380545@tucnak> (raw)
In-Reply-To: <d7aac0c6-e303-5e71-03a7-8c0fe0409daf@codesourcery.com>
On Fri, Aug 13, 2021 at 08:52:34PM +0200, Tobias Burnus wrote:
> gcc/fortran/ChangeLog:
>
> * dump-parse-tree.c (show_omp_clauses): Handle 'filter' clause.
> (show_omp_node, show_code_node): Handle (combined) omp masked construct.
> * frontend-passes.c (gfc_code_walker): Likewise.
> * gfortran.h (enum gfc_statement): Add ST_OMP_*_MASKED*.
> (enum gfc_exec_op): Add EXEC_OMP_*_MASKED*.
> * match.h (gfc_match_omp_masked, gfc_match_omp_masked_taskloop,
> gfc_match_omp_masked_taskloop_simd, gfc_match_omp_parallel_masked,
> gfc_match_omp_parallel_masked_taskloop,
> gfc_match_omp_parallel_masked_taskloop_simd): New prototypes.
> * openmp.c (enum omp_mask1): Add OMP_CLAUSE_FILTER.
> (gfc_match_omp_clauses): Match it.
> (OMP_MASKED_CLAUSES, gfc_match_omp_parallel_masked,
> gfc_match_omp_parallel_masked_taskloop,
> gfc_match_omp_parallel_masked_taskloop_simd,
> gfc_match_omp_masked, gfc_match_omp_masked_taskloop,
> gfc_match_omp_masked_taskloop_simd): New.
> (resolve_omp_clauses): Resolve filter clause.
> (gfc_resolve_omp_parallel_blocks, resolve_omp_do,
> omp_code_to_statement, gfc_resolve_omp_directive): Handle
> omp masked constructs.
> * parse.c (decode_omp_directive, case_exec_markers,
> gfc_ascii_statement, parse_omp_do, parse_omp_structured_block,
> parse_executable): Likewise.
> * resolve.c (gfc_resolve_blocks, gfc_resolve_code): Likewise.
> * st.c (gfc_free_statement): Likewise.
> * trans-openmp.c (gfc_trans_omp_clauses): Handle filter clause.
> (GFC_OMP_SPLIT_MASKED, GFC_OMP_MASK_MASKED): New enum values.
> (gfc_trans_omp_masked): New.
> (gfc_split_omp_clauses): Handle combined masked directives.
> (gfc_trans_omp_master_taskloop): Rename to ...
> (gfc_trans_omp_master_masked_taskloop): ... this; handle also
> combined masked directives.
> (gfc_trans_omp_parallel_master): Rename to ...
> (gfc_trans_omp_parallel_master_masked): ... this; handle
> combined masked directives.
> (gfc_trans_omp_directive): Handle EXEC_OMP_*_MASKED*.
> * trans.c (trans_code): Likewise.
>
> libgomp/ChangeLog:
>
> * testsuite/libgomp.fortran/masked-1.f90: New test.
>
> gcc/testsuite/ChangeLog:
>
> * gfortran.dg/gomp/masked-1.f90: New test.
> * gfortran.dg/gomp/masked-2.f90: New test.
> * gfortran.dg/gomp/masked-3.f90: New test.
> * gfortran.dg/gomp/masked-combined-1.f90: New test.
> * gfortran.dg/gomp/masked-combined-2.f90: New test.
Ok, thanks.
Jakub
next prev parent reply other threads:[~2021-08-16 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 20:48 [committed] openmp: Add support for OpenMP 5.1 masked construct Jakub Jelinek
2021-08-13 14:37 ` [Patch] Fortran/OpenMP: Add support for OpenMP 5.1 masked construct (was: Re: [committed] openmp: Add support for OpenMP 5.1 masked construct) Tobias Burnus
2021-08-13 18:52 ` Tobias Burnus
2021-08-16 7:17 ` Jakub Jelinek [this message]
2021-08-13 21:05 ` [committed] openmp: Add support for OpenMP 5.1 masked construct Thomas Schwinge
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=20210816071756.GT2380545@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).