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/Fortran: Add support for OpenMP 5.2 linear clause syntax
Date: Mon, 4 Jul 2022 21:08:57 +0200 [thread overview]
Message-ID: <YsM6yYwHStKRZK3w@tucnak> (raw)
In-Reply-To: <26d77b3f-2665-164d-60e8-9504af8991de@codesourcery.com>
On Mon, Jul 04, 2022 at 08:29:37PM +0200, Tobias Burnus wrote:
> Fortran part to C/C++
> commit r13-1002-g03b71406323ddc065b1d7837d8b43b17e4b048b5
>
> gcc/fortran/ChangeLog:
>
> * gfortran.h (gfc_omp_namelist): Update by creating 'linear' struct,
> move 'linear_op' as 'op' to id and add 'old_modifier' to it.
> * dump-parse-tree.cc (show_omp_namelist): Update accordingly.
> * module.cc (mio_omp_declare_simd): Likewise.
> * trans-openmp.cc (gfc_trans_omp_clauses): Likewise.
> * openmp.cc (resolve_omp_clauses): Likewise; accept new-style
> 'val' modifier with do/simd.
> (gfc_match_omp_clauses): Handle OpenMP 5.2 linear clause syntax.
>
> libgomp/ChangeLog:
>
> * libgomp.texi (OpenMP 5.2): Mark linear-clause change as 'Y'.
>
> gcc/testsuite/ChangeLog:
>
> * c-c++-common/gomp/linear-4.c: New test.
> * gfortran.dg/gomp/linear-2.f90: New test.
> * gfortran.dg/gomp/linear-3.f90: New test.
> * gfortran.dg/gomp/linear-4.f90: New test.
> * gfortran.dg/gomp/linear-5.f90: New test.
> * gfortran.dg/gomp/linear-6.f90: New test.
> * gfortran.dg/gomp/linear-7.f90: New test.
> * gfortran.dg/gomp/linear-8.f90: New test.
Ok, thanks.
Jakub
prev parent reply other threads:[~2022-07-04 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 14:10 Tobias Burnus
2022-07-04 14:53 ` Jakub Jelinek
2022-07-04 16:09 ` Tobias Burnus
2022-07-04 17:20 ` Jakub Jelinek
2022-07-04 18:29 ` Tobias Burnus
2022-07-04 19:08 ` 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=YsM6yYwHStKRZK3w@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).