public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99519] New: [OpenMP] PRIVATE/FIRSTPRIVATE with CLASS / polymorphic list items Date: Wed, 10 Mar 2021 15:27:04 +0000 [thread overview] Message-ID: <bug-99519-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99519 Bug ID: 99519 Summary: [OpenMP] PRIVATE/FIRSTPRIVATE with CLASS / polymorphic list items Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, openmp Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- Follow-up to PR86470. Class variables need some special handling for PRIVATE/FIRSTPRIVATE in data-sharing constructs like: class(*), allocatable :: var1, var2 ... !$omp parallel private(var1) firstprivate(var2) ... !$omp end parallel The following patch handles FIRSTPRIVATE: https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566529.html Missing: * PRIVATE - which causes still ICEs, even though not for PR86470. → use dynamic type of var, apply default initializers * Polymorphic arrays not supported by FIRSTPRIVATE patch * Check that for TYPE, the default initializer is applied - what about the finalizer?
next reply other threads:[~2021-03-10 15:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 15:27 burnus at gcc dot gnu.org [this message] 2021-05-24 15:10 ` [Bug fortran/99519] " burnus at gcc dot gnu.org
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=bug-99519-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).