public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102204] OpenMP offload map type restriction Date: Mon, 13 Sep 2021 13:41:53 +0000 [thread overview] Message-ID: <bug-102204-4-9rmiBjiVMJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102204-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102204 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- That isn't a made up restriction, but the OpenMP 4.5 standard (and older too) explicitly requiring that "A mappable type cannot contain virtual members." OpenMP 5.0 doesn't have that restriction anymore, but removing it is part of significant other changes that need to be implemented on the compiler and library side and those haven't been done yet. AFAIK no compiler has full OpenMP 5.0 support yet.
next prev parent reply other threads:[~2021-09-13 13:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-05 3:30 [Bug c++/102204] New: " xw111luoye at gmail dot com 2021-09-13 13:41 ` jakub at gcc dot gnu.org [this message] 2021-09-13 14:03 ` [Bug c++/102204] " xw111luoye at gmail dot com 2022-01-28 18:27 ` xw111luoye at gmail dot com 2022-02-10 18:04 ` cvs-commit at gcc dot gnu.org 2022-02-10 18:07 ` 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-102204-4-9rmiBjiVMJ@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).