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/100154] [9/10/11/12 Regression] ICE in gfc_conv_procedure_call, at fortran/trans-expr.c:6131
Date: Wed, 21 Apr 2021 20:55:30 +0000	[thread overview]
Message-ID: <bug-100154-4-XAkVJTajaj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100154-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #7)
> Do you think the following is the right thing?

Correction:

diff --git a/gcc/fortran/check.c b/gcc/fortran/check.c
index 82db8e4e1b2..e1ec1c610e8 100644
--- a/gcc/fortran/check.c
+++ b/gcc/fortran/check.c
@@ -1055,6 +1055,13 @@ variable_check (gfc_expr *e, int n, bool allow_proc)
          return true;
     }

+  /* F2018:R902: function reference having a data pointer result.  */
+  if (e->expr_type == EXPR_FUNCTION
+      && e->symtree->n.sym->attr.flavor == FL_PROCEDURE
+      && e->symtree->n.sym->attr.function
+      && e->symtree->n.sym->attr.pointer)
+    return true;
+
   gfc_error ("%qs argument of %qs intrinsic at %L must be a variable",
             gfc_current_intrinsic_arg[n]->name, gfc_current_intrinsic,
&e->where);

It's getting late...

  parent reply	other threads:[~2021-04-21 20:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 17:36 [Bug fortran/100154] New: [9/10/11 " gscfq@t-online.de
2021-04-20 20:58 ` [Bug fortran/100154] " anlauf at gcc dot gnu.org
2021-04-20 21:21 ` anlauf at gcc dot gnu.org
2021-04-21  6:19 ` marxin at gcc dot gnu.org
2021-04-21  8:51 ` burnus at gcc dot gnu.org
2021-04-21 20:00 ` [Bug fortran/100154] [9/10/11/12 " anlauf at gcc dot gnu.org
2021-04-21 20:09 ` anlauf at gcc dot gnu.org
2021-04-21 20:36 ` anlauf at gcc dot gnu.org
2021-04-21 20:55 ` anlauf at gcc dot gnu.org [this message]
2021-04-22 21:06 ` anlauf at gcc dot gnu.org
2021-04-24 18:52 ` cvs-commit at gcc dot gnu.org
2021-04-24 19:48 ` anlauf at gcc dot gnu.org
2021-04-27 21:13 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:29 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:41 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:42 ` 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-100154-4-XAkVJTajaj@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).