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/96668] [OpenMP] Re-mapping allocated but previously unallocated allocatable does not work
Date: Tue, 18 Aug 2020 08:59:23 +0000	[thread overview]
Message-ID: <bug-96668-4-zdbhC6mJ9V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96668-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cltang at gcc dot gnu.org

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #0)
>      ! pointer: allegedly target is automatically mapped
>      ! without requiring an explicit mapping or even the always modifier
>      !$omp target  !! map(always, tofrom: p1, p2, q1, q2)

Namely:
"If a list item in a map clause is an associated pointer and
 the pointer is not the base pointer of another list item in
 a map clause on the same construct, then it is treated as if
 its pointer target is implicitly mapped in the same clause.
 For the purposes of the map clause, the mapped pointer
 target is treated as if its base pointer is the associated pointer."

  reply	other threads:[~2020-08-18  8:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18  6:56 [Bug fortran/96668] New: " burnus at gcc dot gnu.org
2020-08-18  8:59 ` burnus at gcc dot gnu.org [this message]
2020-08-18 10:26 ` [Bug fortran/96668] " cltang at gcc dot gnu.org
2020-08-18 16:11 ` kargl at gcc dot gnu.org
2020-08-18 17:02 ` burnus at gcc dot gnu.org
2020-09-15  7:25 ` cvs-commit at gcc dot gnu.org
2020-09-15  7:39 ` burnus at gcc dot gnu.org
2020-09-15 19:44 ` cvs-commit at gcc dot gnu.org
2022-03-10 10:22 ` burnus at gcc dot gnu.org
2022-11-02 20:03 ` cvs-commit 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-96668-4-zdbhC6mJ9V@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).