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 target/101544] [OpenMP][AMDGCN][nvptx] C++ offloading: unresolved _Znwm = "operator new(unsigned long)"
Date: Wed, 21 Jul 2021 07:58:39 +0000 [thread overview]
Message-ID: <bug-101544-4-41ngULeraU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101544-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101544
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c++ |target
Summary|[OpenMP] 'declare target' |[OpenMP][AMDGCN][nvptx] C++
|block around class – |offloading: unresolved
|unresolved _Znwm = |_Znwm = "operator
|"operator new(unsigned |new(unsigned long)"
|long)" |
Target| |nvptx-none,amdgcn-amdhsa
CC|cltang at gcc dot gnu.org |ams at gcc dot gnu.org,
| |vries at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Looking at it more closely, the problem seems to be that
libstdc++{.so,.a}
does not exist for neither nvptx nor amdgcn – and the ME handles this
correctly.
The question is what's needed to get better libstdc++ support – either full
support or like with libgfortran for nvptx stripped-down minimal version.
next prev parent reply other threads:[~2021-07-21 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 6:40 [Bug c++/101544] New: [OpenMP] 'declare target' block around class – " burnus at gcc dot gnu.org
2021-07-21 7:58 ` burnus at gcc dot gnu.org [this message]
2021-07-21 8:05 ` [Bug target/101544] [OpenMP][AMDGCN][nvptx] C++ offloading: " jakub at gcc dot gnu.org
2021-07-21 9:06 ` ams at gcc dot gnu.org
2021-07-21 9:33 ` redi at gcc dot gnu.org
2021-07-21 10:03 ` ams at gcc dot gnu.org
2021-07-21 13:27 ` rguenth at gcc dot gnu.org
2021-07-21 13:37 ` redi at gcc dot gnu.org
2021-07-26 12:01 ` tschwinge at gcc dot gnu.org
2022-07-22 13:32 ` tschwinge at gcc dot gnu.org
2022-07-22 14:04 ` tschwinge at gcc dot gnu.org
2022-07-25 11:20 ` rguenth at gcc dot gnu.org
2023-06-01 19:27 ` tschwinge 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-101544-4-41ngULeraU@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).