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/105318] New: [OpenMP] is_device_ptr rejects valid arguments to has_device_addr
Date: Wed, 20 Apr 2022 12:29:49 +0000	[thread overview]
Message-ID: <bug-105318-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105318
           Summary: [OpenMP] is_device_ptr rejects valid arguments to
                    has_device_addr
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: openmp, rejects-valid
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
                CC: marcel at codesourcery dot com
  Target Milestone: ---

OpenMP 5.2 has the following (likewise wording in 5.1):

  "If the is_device_ptr clause is specified on a target construct, if any list
item
   is not of type C_PTR, the behavior is as if the list item appeared in a
   has_device_addr clause. Support for such list items in an is_device_ptr
clause is
   deprecated."


However, input is rejected due to the OpenMP 5.0 checks:

   12 |         !$omp target is_device_ptr(bbbb, aaaa)
      |                                   1
Error: Non-dummy object ‘bbbb’ in IS_DEVICE_PTR clause at (1)

   12 |         !$omp target is_device_ptr(bbbb, aaaa)
      |                                   1
Error: ALLOCATABLE object ‘bbbb’ in IS_DEVICE_PTR clause at (1)


For:

program main
  implicit none
  integer, allocatable :: aaa(:,:,:)
  allocate (aaa(-4:10,-3:8,2))
  call test_ptr (aaa)
  deallocate (aaa)
contains
  subroutine test_ptr (aaaa)
    integer, allocatable :: aaaa(:,:,:), bbbb(:,:,:)
    !$omp target data map(bbbb, aaaa)
      !$omp target data use_device_ptr(bbbb, aaaa)
        !$omp target is_device_ptr(bbbb, aaaa)
          ! ...
        !$omp end target
      !$omp end target data
    !$omp end target data
    deallocate (bbbb)
  end subroutine test_ptr
end program main

             reply	other threads:[~2022-04-20 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 12:29 burnus at gcc dot gnu.org [this message]
2022-08-17  6:48 ` [Bug fortran/105318] " burnus at gcc dot gnu.org
2022-09-30 11:37 ` [Bug fortran/105318] [OpenMP][5.1] " cvs-commit at gcc dot gnu.org
2022-09-30 11:42 ` 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-105318-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).