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 middle-end/106316] [OpenMP] Auto "declare target" should honor  'declare variant'  kind(nohost)
Date: Thu, 03 Nov 2022 16:10:29 +0000	[thread overview]
Message-ID: <bug-106316-4-ouQRpRhzLw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106316-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
I note that the OpenMP example document has a similar example at
  https://github.com/OpenMP/examples-internal/pull/329
for OpenMP-Examples Issue https://github.com/OpenMP/spec/issues/3332
For that example, GCC produces device code, which according to the testcase it
shouldn't.

Result: The Fortran example currently fails with nvptx as Fortran 'print' is
not yet supported. (Scheduled to become available. The C 'printf' is available
and AMDGCN also has both.)

Note: Issue/PR is unfortunately not publicly accessible. The example is not in
the 5.2.1 example document, scheduled to be released really soon (for SC22,
i.e. mid-Nov 22). It might become publicly available next year for SC23.

      parent reply	other threads:[~2022-11-03 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 15:34 [Bug middle-end/106316] New: " burnus at gcc dot gnu.org
2022-07-26 12:18 ` [Bug middle-end/106316] " jakub at gcc dot gnu.org
2022-11-03 16:10 ` burnus at gcc dot gnu.org [this message]

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-106316-4-ouQRpRhzLw@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).