From: Tobias Burnus <tobias@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] OpenMP/Fortran: Handle polymorphic scalars in data-sharing FIRSTPRIVATE (PR86470)
Date: Mon, 31 Aug 2020 10:28:14 +0200 [thread overview]
Message-ID: <4d392886-4a31-fbbc-acdc-303f547f4967@codesourcery.com> (raw)
In-Reply-To: <8bcd00c3-9de5-c072-d893-9218a08a1c2f@codesourcery.com>
*PING* — For this part 1/n patch series.
On 8/25/20 12:50 PM, Tobias Burnus wrote:
> This patch adds support for polymorphic variables ("CLASS")
> to OpenMP's data-sharing clause FIRSTPRIVATE.
>
> While the patch should be okay, there is more follow-up
> work required, but one has to make a start :-)
>
> * PRIVATE – as used in the testcase of the PR is not yet supported,
> only FIRSTPRIVATE.
> * polymorphic arrays are not supported (see 'sorry').
> – For nonallocatable arrays, the decl passed to the function
> does contain much information; the LANG_SPECIFIC is non-NULL
> its the pointer components contain garbage :-(
> – Handling noncharacter polymorphic arrays (hence: non-unlimited
> polymorphic) seems to be simpler; the current patch seems to
> work for some cases already, if the "sorry" is commented.
> * ...
>
> OK for mainline?
>
> Tobias
>
> PS: Supporting *map*ing of polymorphic variables is another matter,
> which is unfortunately even harder.
>
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
next prev parent reply other threads:[~2020-08-31 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 10:50 Tobias Burnus
2020-08-31 8:28 ` Tobias Burnus [this message]
2020-08-31 10:55 ` Andre Vehreschild
2020-08-31 13:58 ` Tobias Burnus
2020-08-31 16:34 ` Jakub Jelinek
2021-03-10 10:55 [Patch] OpenMP/Fortran: Handle polymorphic scalars in data-sharing FIRSTPRIVATE [PR86470] Tobias Burnus
2021-05-23 9:47 ` Tobias Burnus
2021-05-24 14:06 ` Jakub Jelinek
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=4d392886-4a31-fbbc-acdc-303f547f4967@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).