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:24 +0000	[thread overview]
Message-ID: <bug-109622-4-Iz7qyFp8II@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 #13 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:fa7c4ab36585ba128733265fb626ff3f4066400f

commit r13-7298-gfa7c4ab36585ba128733265fb626ff3f4066400f
Author: Julian Brown <julian@codesourcery.com>
Date:   Wed Apr 26 14:31:53 2023 +0000

    OpenACC: Stand-alone attach/detach clause fixes for Fortran [PR109622]

    This patch fixes several cases where multiple attach or detach mapping
    nodes were being created for stand-alone attach or detach clauses
    in Fortran.  After the introduction of stricter checking later during
    compilation, these extra nodes could cause ICEs, as seen in the PR.

    The patch also fixes cases that "happened to work" previously where
    the user attaches/detaches a pointer to array using a descriptor, and
    (I think!) the "_data" field has offset zero, hence the same address as
    the descriptor as a whole.

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

            PR fortran/109622

    gcc/fortran/
            * trans-openmp.cc (gfc_trans_omp_clauses): Attach/detach clause
fixes.

    gcc/testsuite/
            * gfortran.dg/goacc/attach-descriptor.f90: Adjust expected output.

    libgomp/
            * testsuite/libgomp.fortran/pr109622.f90: New test.
            * testsuite/libgomp.fortran/pr109622-2.f90: New test.
            * testsuite/libgomp.fortran/pr109622-3.f90: New test.

    (cherry picked from commit cacf65d74463600815773255e8b82b4043432bd7)

  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 [this message]
2023-05-05 13:15 ` cvs-commit at gcc dot gnu.org
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-Iz7qyFp8II@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).