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/98862] Complex reduction support in offload region
Date: Thu, 28 Jan 2021 14:18:18 +0000	[thread overview]
Message-ID: <bug-98862-4-i9fmqu535J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98862-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
> libstdc++-v3 isn't supported ATM on either nvptx* or amdgcn* offloading, so
> if one needs anything from libstdc++, it will not work.

I can confirm that it does not work with '-O0', showing that the
symbol
   _ZNSt7complexIfEC1Eff
alias
   std::complex<float>::complex(float, float)
is missing.

But:

> As for the 16 byte atomics, I thought this was meant to be solved through
> -latomic, but I might misremember.

Yes,
  $ g++ -fopenmp -O2 complex_reduction.cpp -foffload=-latomic
works – both compiling and running (on nvptx).

Note the added '-foffload=-latomic' (and -O2).
See also: https://gcc.gnu.org/wiki/Offloading#Compilation_options

  parent reply	other threads:[~2021-01-28 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  3:14 [Bug c++/98862] New: " xw111luoye at gmail dot com
2021-01-28 13:06 ` [Bug target/98862] " jakub at gcc dot gnu.org
2021-01-28 14:18 ` burnus at gcc dot gnu.org [this message]
2021-01-28 18:39 ` xw111luoye at gmail dot com
2022-09-08 18:51 ` xw111luoye at gmail dot com

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-98862-4-i9fmqu535J@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).