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 firstprivate and allocate clauses on scope construct
Date: Fri, 3 Jun 2022 15:41:25 +0200 [thread overview]
Message-ID: <YpoPhWg0YRnR/Qhf@tucnak> (raw)
In-Reply-To: <e89f8b03-3ee1-8c3a-173e-1e662133ff43@codesourcery.com>
On Fri, Jun 03, 2022 at 03:37:56PM +0200, Tobias Burnus wrote:
> Simple patch. Testcases based on the C/C++ commit.
> For allocate, I found an unrelated bug which prevented me from adding
> the associated testcase: https://gcc.gnu.org/PR105836
>
> Tested on x86-64 (w/o offloading).
> OK for mainline?
>
> 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/Fortran: Add support for firstprivate and allocate clauses on scope construct
>
> Fortran commit to C/C++/backend commit
> r13-862-gf38b20d68fade5a922b9f68c4c3841e653d1b83c
>
> gcc/fortran/ChangeLog:
>
> * openmp.cc (OMP_SCOPE_CLAUSES): Add firstprivate and allocate.
>
> libgomp/ChangeLog:
>
> * libgomp.texi (OpenMP 5.2): Mark scope w/ firstprivate/allocate as Y.
> * testsuite/libgomp.fortran/scope-2.f90: New test.
>
> gcc/testsuite/ChangeLog:
>
> * gfortran.dg/gomp/scope-5.f90: New test.
> * gfortran.dg/gomp/scope-6.f90: New test.
Ok, thanks.
Jakub
prev parent reply other threads:[~2022-06-03 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 13:37 Tobias Burnus
2022-06-03 13:41 ` 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=YpoPhWg0YRnR/Qhf@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).