public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97203] [nvptx] 'illegal memory access was encountered' with 'omp simd'/SIMT and cexpf call
Date: Thu, 08 Oct 2020 15:37:00 +0000	[thread overview]
Message-ID: <bug-97203-4-i9mbd8bYbA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97203-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
FWIW, another aspect here is convergence (as usual).

Looking at the SASS code for main$_omp_fn$0$impl, I don't find evidence for the
usual divergence/convergence ops (SSY/SYNC), which might mean that the
following shfl is executed in divergent mode, so, even if we would not get the
memory access error, we would not get correct results.

  parent reply	other threads:[~2020-10-08 15:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  8:52 [Bug target/97203] New: " burnus at gcc dot gnu.org
2020-09-25  8:57 ` [Bug target/97203] " burnus at gcc dot gnu.org
2020-10-08  9:56 ` vries at gcc dot gnu.org
2020-10-08 12:57 ` vries at gcc dot gnu.org
2020-10-08 15:27 ` vries at gcc dot gnu.org
2020-10-08 15:37 ` vries at gcc dot gnu.org [this message]
2020-10-09  8:36 ` amonakov at gcc dot gnu.org
2020-10-12  8:44 ` vries at gcc dot gnu.org
2020-10-12  9:36 ` amonakov at gcc dot gnu.org
2020-10-12 13:00 ` vries at gcc dot gnu.org
2020-10-12 15:10 ` vries at gcc dot gnu.org
2020-10-12 15:15 ` amonakov 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-97203-4-i9mbd8bYbA@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).