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++/104493] New: OpenMP offload map cannot handle const Date: Thu, 10 Feb 2022 20:23:55 +0000 [thread overview] Message-ID: <bug-104493-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104493 Bug ID: 104493 Summary: OpenMP offload map cannot handle const Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: xw111luoye at gmail dot com Target Milestone: --- See reproducer https://github.com/ye-luo/openmp-target/blob/master/tests/map/struct_with_const.cpp $ g++ -fopenmp -foffload=nvptx-none struct_with_const.cpp struct_with_const.cpp: In constructor ‘with_const::with_const()’: struct_with_const.cpp:9:42: error: array section does not have mappable type in ‘map’ clause 9 | #pragma omp target enter data map(to:this[:1]) | ^~~~ struct_with_const.cpp:12:24: note: static field ‘with_const::size’ is not mappable 12 | constexpr static int size = 6; | ^~~~ struct_with_const.cpp:13:20: note: static field ‘with_const::b’ is not mappable 13 | static const int b = 12; | ^ In file included from /soft/gcc/gcc-12-dev-2022-02-10/include/c++/12.0.1/string:53, from /soft/gcc/gcc-12-dev-2022-02-10/include/c++/12.0.1/bits/locale_classes.h:40, from /soft/gcc/gcc-12-dev-2022-02-10/include/c++/12.0.1/bits/ios_base.h:41, from /soft/gcc/gcc-12-dev-2022-02-10/include/c++/12.0.1/ios:42, from /soft/gcc/gcc-12-dev-2022-02-10/include/c++/12.0.1/ostream:38, from /soft/gcc/gcc-12-dev-2022-02-10/include/c++/12.0.1/iostream:39, from struct_with_const.cpp:1: /soft/gcc/gcc-12-dev-2022-02-10/include/c++/12.0.1/bits/basic_string.h:140:33: note: static field ‘std::__cxx11::basic_string<char>::npos’ is not mappable 140 | static const size_type npos = static_cast<size_type>(-1); | ^~~~ struct_with_const.cpp:9:13: error: ‘#pragma omp target enter data’ must contain at least one ‘map’ clause 9 | #pragma omp target enter data map(to:this[:1]) |
next reply other threads:[~2022-02-10 20:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-10 20:23 xw111luoye at gmail dot com [this message] 2022-05-24 0:50 ` [Bug c++/104493] " xw111luoye at gmail dot com 2022-05-25 9:09 ` burnus at gcc dot gnu.org 2022-05-25 13:45 ` xw111luoye at gmail dot com 2022-07-04 21:13 ` xw111luoye at gmail dot com 2022-08-05 8:03 ` burnus 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-104493-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: 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).