public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102544] New: GCN offloading not working for 'amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-'
Date: Thu, 30 Sep 2021 10:17:58 +0000 [thread overview]
Message-ID: <bug-102544-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102544
Bug ID: 102544
Summary: GCN offloading not working for
'amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-'
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: openacc, openmp
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: ams at gcc dot gnu.org, caplanr at predsci dot com,
jules at gcc dot gnu.org
Target Milestone: ---
Target: GCN
Ron Caplan (in CC) is always eager to try his computational codes with GCC (in
addition to other/proprietary/vendor-provided compilers), and I very much
appreciate him providing feedback of any kind, which I find is always
constructive.
He's recently reported that "using Ubuntu 20.04 with the latest rocm and a
Radeon VII", they got GCN offloading "to compile but when we run it we get:
'libgomp: target function wasn't mapped'".
He sent me 'rocm-smi' and 'rocminfo' output, and comparing his vs. that of our
amd_ryzen3 system, I find the following differences:
-/+ Agent [...]
*******
Name: gfx906
-/+ Uuid: [...]
- Marketing Name: Vega 20
+ Marketing Name: Vega 20 [Radeon VII]
Vendor Name: AMD
[...]
- Node: 1
+ Node: 2
Device Type: GPU
Cache Info:
L1: 16(0x10) KB
+ L2: 8192(0x2000) KB
Chip ID: 26287(0x66af)
Cacheline Size: 64(0x40)
-/+ Max Clock Freq. (MHz): [...]
- BDFID: 2816
+ BDFID: 33536
- Internal Node ID: 1
+ Internal Node ID: 2
Compute Unit: 60
SIMDs per CU: 4
Shader Engines: 4
@@ -128,7 +188,7 @@ Agent 2
Accessible by all: FALSE
ISA Info:
ISA 1
- Name: amdgcn-amd-amdhsa--gfx906:sramecc-:xnack-
+ Name: amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-
The very last item, I suppose, is the crucial one: 'sramecc-' vs. 'sramecc+' --
Andrew?
(a) How do we improve upon the run-time 'libgomp: target function wasn't
mapped' error reporting mode?
(b) What needs to be done to make this work?
next reply other threads:[~2021-09-30 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 10:17 tschwinge at gcc dot gnu.org [this message]
2021-09-30 12:38 ` [Bug target/102544] " ams at gcc dot gnu.org
2021-10-01 5:44 ` miko at predsci dot com
2021-10-01 10:54 ` ams at gcc dot gnu.org
2021-10-01 17:07 ` miko at predsci dot com
2021-10-01 17:21 ` ams at gcc dot gnu.org
2021-10-01 18:44 ` miko at predsci dot com
2021-10-01 18:48 ` caplanr at predsci dot com
2021-10-04 12:07 ` ams at gcc dot gnu.org
2021-10-04 16:52 ` miko at predsci 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-102544-4@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).