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/69090] Allocatable arrays mishandled in 'omp declare target'
Date: Fri, 04 Nov 2022 11:42:08 +0000	[thread overview]
Message-ID: <bug-69090-4-c4TyU8h6JT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-69090-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69090

--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #8)
> Has this been fixed via PR96668 "[OpenMP] Re-mapping allocated but
> previously unallocated allocatable does not work", by chance?  (Tobias?)

I think both examples should work since that commit went into GCC 11 (untested,
however).

(It is clear why the example in comment 0 did not work back then (2015),
 but the one in comment 7 is unclear as no GCC version was mentioned;
 if it was mainline it should work (GCC 11), if it was a release
 branch, the fail is understandable.)

NOTE: While the fix for PR96668 handles previously unallocated arrays,
the OpenMP specification since 5.1 (or rather already TR 9) clarified that
the 'always' modifier is required. This requirement might go away in
OpenMP 6.0, but even TR11 still has it.

NOTE 2: PR96668 is not yet closed as scalar allocatables are not handled, yet.
(But both examples in this PR use arrays.)

      parent reply	other threads:[~2022-11-04 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-69090-4@http.gcc.gnu.org/bugzilla/>
2020-10-05 15:15 ` dominiq at lps dot ens.fr
2021-02-17 22:39 ` john.donners at atos dot net
2022-11-04 10:50 ` tschwinge at gcc dot gnu.org
2022-11-04 11:42 ` 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-69090-4-c4TyU8h6JT@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: 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).