public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xw111luoye at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95474] New: class member array cannot be mapped
Date: Tue, 02 Jun 2020 07:06:33 +0000	[thread overview]
Message-ID: <bug-95474-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95474
           Summary: class member array cannot be mapped
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: xw111luoye at gmail dot com
  Target Milestone: ---

https://github.com/ye-luo/openmp-target/blob/master/hands-on/tests/map/map_class_member.cpp

$ g++ -fopenmp map_class_member.cpp
map_class_member.cpp: In instantiation of ‘maptest<T>::maptest() [with T =
float]’:
map_class_member.cpp:26:18:   required from here
map_class_member.cpp:12:45: error: ‘maptest<float>::data’ is not a variable in
‘map’ clause
   12 |     #pragma omp target enter data map(alloc:data[:6])
      |                                             ^~~~
map_class_member.cpp: In instantiation of ‘maptest<T>::~maptest() [with T =
float]’:
map_class_member.cpp:26:18:   required from here
map_class_member.cpp:19:45: error: ‘maptest<float>::data’ is not a variable in
‘map’ clause
   19 |     #pragma omp target exit data map(delete:data[:6])
      |                                             ^~~~

Syntax parsing seems broken.

             reply	other threads:[~2020-06-02  7:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02  7:06 xw111luoye at gmail dot com [this message]
2020-06-02  9:12 ` [Bug c++/95474] " jakub at gcc dot gnu.org
2020-06-02 14:24 ` xw111luoye at gmail dot com
2020-06-02 14:35 ` jakub at gcc dot gnu.org
2020-06-02 14:55 ` xw111luoye at gmail dot com
2020-06-02 14:57 ` jakub 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-95474-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).