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] [OpenMP] PRIVATE/FIRSTPRIVATE with CLASS / polymorphic list items Date: Mon, 24 May 2021 15:10:28 +0000 [thread overview] Message-ID: <bug-99519-4-QV6VNNfvy6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99519-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99519 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> --- The patch was now committed as: commit r12-1016-g0e3b3b77e13cac764a135a7118613c47686e0a62 Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon May 24 16:50:51 2021 +0200 OpenMP/Fortran: Handle polymorphic scalars in data-sharing FIRSTPRIVATE [PR86470] (The PR is the original PR instead of the one of this follow-up PR.) To be done: 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 patch was for CLASS), the default initializer is applied - and what about the finalizer?
prev parent reply other threads:[~2021-05-24 15:10 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 15:27 [Bug fortran/99519] New: " burnus at gcc dot gnu.org 2021-05-24 15:10 ` burnus at gcc dot gnu.org [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=bug-99519-4-QV6VNNfvy6@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).