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/104696] New: [12 Regression][OpenMP] Implicit mapping breaks struct mapping
Date: Sat, 26 Feb 2022 00:06:24 +0000	[thread overview]
Message-ID: <bug-104696-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104696
           Summary: [12 Regression][OpenMP] Implicit mapping breaks struct
                    mapping
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: openmp, wrong-code
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
                CC: cltang at gcc dot gnu.org, jakub at gcc dot gnu.org
  Target Milestone: ---

Created attachment 52519
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52519&action=edit
implicit.f90 - compile with -fopenmp and run with a non-shared-memory device.

In my understanding, the following is valid and should work.

However, it fails – and I bet it is due to the implicit mapping of 'var3'. The
code uses:

!$omp target map(to: var3%R(2)%d)
 ...

Printing on the host the  'loc (var3%R(2)%d)'  shows:
         21516C0
    7F51E5E001D8
    STOP 11

As var%R(2)%d  (or in the dump 'var3.r[1].d.data')  is now in device address
space,
accessing it after the target region crashes the program.


implicit.f90.005t.original:
  #pragma omp target
     map(to:var3.r[1].d [len: 88])
     map(to:*(struct t2[0:] *) var3.r[1].d.data [len: D.4243 * 4])
     map(always_pointer:(struct t2[0:] *) var3.r[1].d.data [pointer assign,
bias: 0])

implicit.f90.006t.gimple:
  #pragma omp target num_teams(1) thread_limit(0)
     map(tofrom:var3 [len: 440][implicit])
     map(to:var3.r[1].d [len: 88])
     map(to:MEM <struct t2[0:]> [(struct t2[0:] *)_9] [len: _8])
     map(always_pointer:var3.r[1].d.data [pointer assign, bias: 0])

             reply	other threads:[~2022-02-26  0:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26  0:06 burnus at gcc dot gnu.org [this message]
2022-03-01  7:35 ` [Bug fortran/104696] " rguenth at gcc dot gnu.org
2022-03-03 17:18 ` [Bug fortran/104696] [OpenMP] " burnus at gcc dot gnu.org
2022-03-07 13:53 ` burnus at gcc dot gnu.org
2022-03-10 14:27 ` cltang at gcc dot gnu.org
2022-03-10 15:13 ` burnus at gcc dot gnu.org
2022-03-14 14:48 ` [Bug middle-end/104696] [OpenMP] component/array-ref/component (x.r[1].d) should use 'x' for GOMP_MAP_STRUCT (not yield 'x.r[1]' for nonptr 'x.r') burnus at gcc dot gnu.org
2022-05-06  8:32 ` jakub at gcc dot gnu.org
2023-05-08 12:23 ` rguenth 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-104696-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: 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).