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/107074] ICE: Bad IO basetype (8)
Date: Mon, 03 Oct 2022 20:31:32 +0000	[thread overview]
Message-ID: <bug-107074-4-HvqxJyvCkV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107074-4@http.gcc.gnu.org/bugzilla/>

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

anlauf at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anlauf at gcc dot gnu.org

--- Comment #3 from anlauf at gcc dot gnu.org ---
Potential fix:

diff --git a/gcc/fortran/trans-io.cc b/gcc/fortran/trans-io.cc
index 9f86815388c..2f1a7be04aa 100644
--- a/gcc/fortran/trans-io.cc
+++ b/gcc/fortran/trans-io.cc
@@ -2529,6 +2529,17 @@ transfer_expr (gfc_se * se, gfc_typespec * ts, tree
addr_expr,
        }
       gcc_fallthrough ();
     default:
+      if (ts->type == BT_PROCEDURE
+         && code->expr1
+         && code->expr1->symtree
+         && code->expr1->symtree->n.sym)
+       {
+         if (code->expr1->symtree->n.sym->attr.proc_pointer)
+           gfc_error ("Procedure pointer at %C cannot be an output item");
+         else
+           gfc_error ("Procedure at %C cannot be an output item");
+         return;
+       }
       gfc_internal_error ("Bad IO basetype (%d)", ts->type);
     }

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 17:34 [Bug fortran/107074] New: " gscfq@t-online.de
2022-09-28 18:53 ` [Bug fortran/107074] " anlauf at gcc dot gnu.org
2022-09-28 19:10 ` anlauf at gcc dot gnu.org
2022-10-03 20:31 ` anlauf at gcc dot gnu.org [this message]
2022-10-04 19:35 ` 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-107074-4-HvqxJyvCkV@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).