public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf 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: Mon, 23 Oct 2023 19:15:22 +0000 [thread overview] Message-ID: <bug-104131-4-lIdyR9MWUT@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 #5 from anlauf at gcc dot gnu.org --- The coarray cases in comment#2 will be rejected with: diff --git a/gcc/fortran/openmp.cc b/gcc/fortran/openmp.cc index 1cc65d7fa49..08081dacde4 100644 --- a/gcc/fortran/openmp.cc +++ b/gcc/fortran/openmp.cc @@ -8967,6 +8967,9 @@ resolve_omp_clauses (gfc_code *code, gfc_omp_clauses *omp_clauses, else if (omp_clauses->detach->symtree->n.sym->attr.dimension > 0) gfc_error ("The event handle at %L must not be an array element", &omp_clauses->detach->where); + else if (omp_clauses->detach->symtree->n.sym->attr.codimension) + gfc_error ("The event handle at %L must not be a coarray", + &omp_clauses->detach->where); else if (omp_clauses->detach->symtree->n.sym->ts.type == BT_DERIVED || omp_clauses->detach->symtree->n.sym->ts.type == BT_CLASS) gfc_error ("The event handle at %L must not be part of " I assume that these are not allowed.
next prev parent reply other threads:[~2023-10-23 19:15 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 2023-10-23 18:50 ` anlauf at gcc dot gnu.org 2023-10-23 19:15 ` anlauf at gcc dot gnu.org [this message] 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-lIdyR9MWUT@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: linkBe 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).