public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102544] GCN offloading not working for 'amdgcn-amd-amdhsa--gfx906:sramecc+:xnack-'
Date: Fri, 01 Oct 2021 10:54:54 +0000	[thread overview]
Message-ID: <bug-102544-4-MYa3MZxFmQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102544-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Stubbs <ams at gcc dot gnu.org> ---
That output shows that we have the correct libgomp and rocm is installed and
working. Libgomp initialized the GCN plugin, but did not attempt to initialize
the device (the next message in the output should have been "Selected kernel
arguments memory region", or at least a GCN error message).

Instead we have a target-independent libgomp error. Presumably the kernel
metadata is malformed, somehow?

I think we need a testcase to debug this further, preferably reduced to be as
simple as possible.

Perhaps it would be a good idea to start with a minimal toy example and see if
that works on the device.

#include <openacc.h>
#include <stdio.h>

int main ()
{
  int v = 1;

#pragma acc parallel copy(v)
  {
    if (acc_on_device(acc_device_host))
      v = -1; // error
    else {
      v = 2; // success
    }
  }

  printf ("v is %d\n", v);
  return v;
}

  parent reply	other threads:[~2021-10-01 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30 10:17 [Bug target/102544] New: " tschwinge at gcc dot gnu.org
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 [this message]
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-MYa3MZxFmQ@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).