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 fortran/115559] [OpenMP] 'link' clause of 'declare target' causes link errors
Date: Thu, 20 Jun 2024 17:46:20 +0000	[thread overview]
Message-ID: <bug-115559-4-pRrjHJMFBy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115559-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
For C, it is actually handled in the FE for

      tree at1 = lookup_attribute ("omp declare target", DECL_ATTRIBUTES (t));
      tree at2 = lookup_attribute ("omp declare target link",
                                   DECL_ATTRIBUTES (t));
      only_device_type_or_indirect = false;
      if (OMP_CLAUSE_CODE (c) == OMP_CLAUSE_LINK)
        {   
          id = get_identifier ("omp declare target link");
          std::swap (at1, at2);
        }
...
      if (!at1)
        {
          DECL_ATTRIBUTES (t) = tree_cons (id, NULL_TREE, DECL_ATTRIBUTES (t));
          if (TREE_CODE (t) != FUNCTION_DECL && !is_global_var (t))
            continue;

          symtab_node *node = symtab_node::get (t);
          if (node != NULL)
            {
              node->offloadable = 1;
              if (ENABLE_OFFLOADING)
                {
                  g->have_offload = true;
                  if (is_a <varpool_node *> (node))
                    vec_safe_push (offload_vars, t);
                }
            }

  parent reply	other threads:[~2024-06-20 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 14:44 [Bug fortran/115559] New: " burnus at gcc dot gnu.org
2024-06-20 15:15 ` [Bug fortran/115559] " burnus at gcc dot gnu.org
2024-06-20 17:46 ` burnus at gcc dot gnu.org [this message]
2024-06-20 18:47 ` burnus at gcc dot gnu.org
2024-06-20 19:03 ` burnus at gcc dot gnu.org
2024-06-21 16:08 ` burnus at gcc dot gnu.org
2024-06-21 16:11 ` burnus at gcc dot gnu.org
2024-06-25 10:47 ` burnus 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-115559-4-pRrjHJMFBy@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).