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/104131] ICE in gfc_conv_array_ref, at fortran/trans-array.c:3810
Date: Thu, 03 Mar 2022 10:28:00 +0000	[thread overview]
Message-ID: <bug-104131-4-77mnYwb8QV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104131-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kwok Yeung <kcy@gcc.gnu.org>:

https://gcc.gnu.org/g:88c4d85e27e18bf991ab8728b73127a0385f2c27

commit r12-7464-g88c4d85e27e18bf991ab8728b73127a0385f2c27
Author: Kwok Cheung Yeung <kcy@codesourcery.com>
Date:   Thu Mar 3 10:23:26 2022 +0000

    openmp, fortran: Check that the type of an event handle in a detach clause
is suitable [PR104131]

    This rejects variables that are array types, array elements or derived type
    members when used as the event handle inside a detach clause (in accordance
    with the OpenMP specification).  This would previously lead to an ICE.

    2022-03-03  Kwok Cheung Yeung  <kcy@codesourcery.com>

    gcc/fortran/

            PR fortran/104131
            * openmp.cc (gfc_match_omp_detach): Move check for type of event
            handle to...
            (resolve_omp_clauses) ...here.  Also check that the event handle is
            not an array, or an array access or structure element access.

    gcc/testsuite/

            PR fortran/104131
            * gfortran.dg/gomp/pr104131.f90: New.
            * gfortran.dg/gomp/task-detach-1.f90: Update expected error
message.

  parent reply	other threads:[~2022-03-03 10:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 18:53 [Bug fortran/104131] New: " gscfq@t-online.de
2022-01-20 10:19 ` [Bug fortran/104131] " marxin at gcc dot gnu.org
2022-01-26 17:25 ` gscfq@t-online.de
2022-03-03 10:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-23 18:50 ` anlauf at gcc dot gnu.org
2023-10-23 19:15 ` anlauf at gcc dot gnu.org
2023-10-24 19:53 ` burnus at gcc dot gnu.org
2023-10-24 20:26 ` anlauf at gcc dot gnu.org
2023-10-25  7:07 ` 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-104131-4-77mnYwb8QV@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).