public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov 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: Mon, 12 Oct 2020 09:36:03 +0000 [thread overview] Message-ID: <bug-97203-4-YOkeo1GqHf@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 #8 from Alexander Monakov <amonakov at gcc dot gnu.org> --- No, -msoft-stack-reserve-local is really meant to be in bytes: it may not exceed the amount of .local memory reserved by CUDA driver (which is just 1-2 KB, unless overridden via cuCtxSetLimit, which nvptx-run.c does, but plugin-nvptx.c does not). Keep in mind that .local memory reservation is multiplied by number of active contexts, which could be in range 20000-30000 when the code was written: 128KB local memory per active thread would imply a 2.5GB allocation on the GPU.
next prev parent reply other threads:[~2020-10-12 9:36 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 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 [this message] 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-YOkeo1GqHf@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).