public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46413] [OOP] ICE when printing a polymorphic type
Date: Thu, 11 Nov 2010 09:16:00 -0000	[thread overview]
Message-ID: <bug-46413-4-xaxv7F8LNN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46413-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46413

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-11-11 09:16:08 UTC ---
Untested patch:

Index: resolve.c
===================================================================
--- resolve.c   (Revision 166596)
+++ resolve.c   (Arbeitskopie)
@@ -7948,6 +7948,15 @@ resolve_transfer (gfc_code *code)
     if (ref->type == REF_COMPONENT)
       ts = &ref->u.c.component->ts;

+  if (ts->type == BT_CLASS)
+    {
+      /* FIXME: Test whether there defined input/output is done.  */
+      gfc_error ("Data transfer element at %L cannot be polymorphic unless "
+                "it is processed by a defined input/output procedure",
+                &code->loc);
+      return;
+    }
+
   if (ts->type == BT_DERIVED)
     {
       /* Check that transferred derived type doesn't contain POINTER


  reply	other threads:[~2010-11-11  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 13:53 [Bug fortran/46413] New: " burnus at gcc dot gnu.org
2010-11-11  9:16 ` burnus at gcc dot gnu.org [this message]
2010-11-11 23:07 ` [Bug fortran/46413] " burnus at gcc dot gnu.org
2010-11-11 23:09 ` 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-46413-4-xaxv7F8LNN@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).