public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99818] [10/11 Regression] ICE in gfc_get_tree_for_caf_expr, at fortran/trans-expr.c:2186
Date: Thu, 01 Apr 2021 13:34:14 +0000	[thread overview]
Message-ID: <bug-99818-4-J8FJe5Bl6z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99818-4@http.gcc.gnu.org/bugzilla/>

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

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |pault at gcc dot gnu.org

--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 50494
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50494&action=edit
Fix for the PR

The fix is trivial - gfortran now gives the correct error.
   15 |       call y%s
      |            1
Error: Actual argument to ‘x’ at (1) must be a coarray

Paul

  parent reply	other threads:[~2021-04-01 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 19:33 [Bug fortran/99818] New: " gscfq@t-online.de
2021-03-30 13:08 ` [Bug fortran/99818] " rguenth at gcc dot gnu.org
2021-03-31 12:49 ` marxin at gcc dot gnu.org
2021-03-31 13:24 ` pault at gcc dot gnu.org
2021-04-01 13:34 ` pault at gcc dot gnu.org [this message]
2021-04-03  9:19 ` gscfq@t-online.de
2021-04-03 11:50 ` cvs-commit at gcc dot gnu.org
2021-04-05  6:21 ` pault at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-05-04 12:31 ` [Bug fortran/99818] [10/11/12 " rguenth at gcc dot gnu.org
2021-08-28 20:05 ` cvs-commit at gcc dot gnu.org
2021-08-28 20:06 ` anlauf 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-99818-4-J8FJe5Bl6z@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).