public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105318] [OpenMP][5.1] is_device_ptr rejects valid arguments to has_device_addr
Date: Fri, 30 Sep 2022 11:37:52 +0000	[thread overview]
Message-ID: <bug-105318-4-pxdFaTCHuE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105318-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:

https://gcc.gnu.org/g:10a116104969b3ecc9ea4abdd5436c66fd78d537

commit r13-2980-g10a116104969b3ecc9ea4abdd5436c66fd78d537
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Sep 30 13:27:32 2022 +0200

    Fortran: Update use_device_ptr for OpenMP 5.1 [PR105318]

    OpenMP 5.1 added has_device_addr and relaxed the restrictions for
    use_device_ptr, including processing non-type(c_ptr) arguments as
    if has_device_addr was used. (There is a semantic difference.)

    For completeness, the likewise change was done for 'use_device_ptr',
    where non-type(c_ptr) arguments now use use_device_addr.

    Finally, a warning for 'device(omp_{initial,invalid}_device)' was
    silenced on the way as affecting the new testcase.

            PR fortran/105318

    gcc/fortran/ChangeLog:
            * openmp.cc (resolve_omp_clauses): Update is_device_ptr
restrictions
            for OpenMP 5.1 and map to has_device_addr where applicable; map
            use_device_ptr to use_device_addr where applicable.
            Silence integer-range warning for
device(omp_{initial,invalid}_device).

    libgomp/ChangeLog:
            * testsuite/libgomp.fortran/is_device_ptr-2.f90: New test.

    gcc/testsuite/ChangeLog:
            * gfortran.dg/gomp/is_device_ptr-1.f90: Remove dg-error.
            * gfortran.dg/gomp/is_device_ptr-2.f90: Likewise.
            * gfortran.dg/gomp/is_device_ptr-3.f90: Update tree-scan-dump.

  parent reply	other threads:[~2022-09-30 11:37 UTC|newest]

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