public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Thu, 10 Feb 2022 18:04:11 +0000	[thread overview]
Message-ID: <bug-102204-4-HhWXqejlVT@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 #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:c22f3fb780775b91548e32937a3ce1095a7c72a3

commit r12-7185-gc22f3fb780775b91548e32937a3ce1095a7c72a3
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Feb 10 18:57:37 2022 +0100

    OpenMP/C++: Permit mapping classes with virtual members [PR102204]

            PR c++/102204
    gcc/cp/ChangeLog:

            * decl2.cc (cp_omp_mappable_type_1): Remove check for virtual
            members as those are permitted since OpenMP 5.0.

    libgomp/ChangeLog:

            * testsuite/libgomp.c++/target-virtual-1.C: New test.

    gcc/testsuite/ChangeLog:

            * g++.dg/gomp/unmappable-1.C: Remove previously expected
dg-message.

  parent reply	other threads:[~2022-02-10 18:04 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 ` [Bug c++/102204] " jakub at gcc dot gnu.org
2021-09-13 14:03 ` 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 [this message]
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-HhWXqejlVT@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).