public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66927] [6.0 regression] ICE in gfc_conf_procedure_call
Date: Sat, 18 Jul 2015 13:01:00 -0000	[thread overview]
Message-ID: <bug-66927-4-ZE0ccOhlBS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66927-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from vehre at gcc dot gnu.org ---
This fixes the issue:

diff --git a/gcc/fortran/trans-stmt.c b/gcc/fortran/trans-stmt.c
index 6409f7f..181cbce 100644
--- a/gcc/fortran/trans-stmt.c
+++ b/gcc/fortran/trans-stmt.c
@@ -5189,7 +5189,9 @@ gfc_trans_allocate (gfc_code * code)
          /* Get the descriptor for all arrays, that are not allocatable or
             pointer, because the latter are descriptors already.  */
          attr = gfc_expr_attr (code->expr3);
-         if (code->expr3->rank != 0 && !attr.allocatable && !attr.pointer)
+         if (code->expr3->rank != 0 && ((!attr.allocatable && !attr.pointer)
+                                  || (code->expr3->expr_type == EXPR_FUNCTION
+                                      && code->expr3->ts.type != BT_CLASS)))
            gfc_conv_expr_descriptor (&se, code->expr3);
          else
            gfc_conv_expr_reference (&se, code->expr3);


  parent reply	other threads:[~2015-07-18 13:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18  9:40 [Bug fortran/66927] New: " juergen.reuter at desy dot de
2015-07-18  9:41 ` [Bug fortran/66927] " juergen.reuter at desy dot de
2015-07-18  9:55 ` dominiq at lps dot ens.fr
2015-07-18  9:58 ` vehre at gcc dot gnu.org
2015-07-18 10:01 ` juergen.reuter at desy dot de
2015-07-18 13:01 ` vehre at gcc dot gnu.org [this message]
2015-07-21  7:58 ` [Bug fortran/66927] [6 Regression] " rguenth at gcc dot gnu.org
2015-08-06 10:09 ` vehre at gcc dot gnu.org
2015-10-06  8:40 ` vehre at gcc dot gnu.org
2015-10-16  8:34 ` rguenth at gcc dot gnu.org
2015-10-25 12:29 ` vehre at gcc dot gnu.org
2015-10-25 13:03 ` vehre at gcc dot gnu.org
2015-10-25 16:47 ` hjl.tools at gmail dot com
2015-10-25 18:04 ` vehre at gcc dot gnu.org
2015-10-26 13:04 ` vehre at gcc dot gnu.org
2015-10-26 22:43 ` juergen.reuter at desy dot de
2015-10-26 23:42 ` juergen.reuter at desy dot de
2015-10-27  0:55 ` kargl at gcc dot gnu.org
2015-10-27  1:01 ` juergen.reuter at desy dot de

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-66927-4-ZE0ccOhlBS@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).