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/109622] [13/14 regression][OpenACC] internal compiler error: in omp_group_base, at gimplify.cc:9412 if -fopenacc is set.
Date: Fri, 05 May 2023 13:15:29 +0000	[thread overview]
Message-ID: <bug-109622-4-kiWyWY89IO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109622-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Julian Brown
<jules@gcc.gnu.org>:

https://gcc.gnu.org/g:a4cc474b15ecd148f5bb13a1db3bc3e40a4ff86e

commit r13-7299-ga4cc474b15ecd148f5bb13a1db3bc3e40a4ff86e
Author: Julian Brown <julian@codesourcery.com>
Date:   Fri Apr 28 22:27:54 2023 +0000

    OpenACC: Further attach/detach clause fixes for Fortran [PR109622]

    This patch moves several tests introduced by the following patch:

      https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616939.html
      commit r14-325-gcacf65d74463600815773255e8b82b4043432bd7

    into the proper location for OpenACC testing (thanks to Thomas for
    spotting my mistake!), and also fixes a few additional problems --
    missing diagnostics for non-pointer attaches, and a case where a pointer
    was incorrectly dereferenced. Tests are also adjusted for vector-length
    warnings on nvidia accelerators.

    2023-04-29  Julian Brown  <julian@codesourcery.com>

            PR fortran/109622

    gcc/fortran/
            * openmp.cc (resolve_omp_clauses): Add diagnostic for
            non-pointer/non-allocatable attach/detach.
            * trans-openmp.cc (gfc_trans_omp_clauses): Remove dereference for
            pointer-to-scalar derived type component attach/detach.  Fix
            attach/detach handling for descriptors.

    gcc/testsuite/
            * gfortran.dg/goacc/pr109622-5.f90: New test.
            * gfortran.dg/goacc/pr109622-6.f90: New test.

    libgomp/
            * testsuite/libgomp.fortran/pr109622.f90: Move test...
            * testsuite/libgomp.oacc-fortran/pr109622.f90: ...to here. Ignore
            vector length warning.
            * testsuite/libgomp.fortran/pr109622-2.f90: Move test...
            * testsuite/libgomp.oacc-fortran/pr109622-2.f90: ...to here.  Add
            missing copyin/copyout variable. Ignore vector length warnings.
            * testsuite/libgomp.fortran/pr109622-3.f90: Move test...
            * testsuite/libgomp.oacc-fortran/pr109622-3.f90: ...to here. 
Ignore
            vector length warnings.
            * testsuite/libgomp.oacc-fortran/pr109622-4.f90: New test.

    (cherry picked from commit 0a26a42b237bada32165e61867a2bf4461c5fab2)

  parent reply	other threads:[~2023-05-05 13:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 10:27 [Bug fortran/109622] New: " patrick.begou@univ-grenoble-alpes.fr
2023-04-25 10:29 ` [Bug fortran/109622] " patrick.begou@univ-grenoble-alpes.fr
2023-04-25 10:32 ` patrick.begou@univ-grenoble-alpes.fr
2023-04-25 12:25 ` patrick.begou@univ-grenoble-alpes.fr
2023-04-25 12:49 ` pault at gcc dot gnu.org
2023-04-25 12:51 ` [Bug fortran/109622] [13/14 regression] " pault at gcc dot gnu.org
2023-04-25 13:20 ` rguenth at gcc dot gnu.org
2023-04-25 13:59 ` [Bug fortran/109622] [13/14 regression][OpenACC] " burnus at gcc dot gnu.org
2023-04-25 16:38 ` patrick.begou@univ-grenoble-alpes.fr
2023-04-26  6:58 ` rguenth at gcc dot gnu.org
2023-04-28 11:03 ` burnus at gcc dot gnu.org
2023-04-28 11:34 ` cvs-commit at gcc dot gnu.org
2023-04-29  9:41 ` patrick.begou@univ-grenoble-alpes.fr
2023-05-04 11:52 ` cvs-commit at gcc dot gnu.org
2023-05-05 13:15 ` cvs-commit at gcc dot gnu.org
2023-05-05 13:15 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-08 12:35 ` tschwinge at gcc dot gnu.org
2023-05-08 13:52 ` patrick.begou@univ-grenoble-alpes.fr
2023-05-08 13:56 ` 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-109622-4-kiWyWY89IO@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).