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/64943] No error on ultimate allocatable components in IO list
Date: Thu, 05 Feb 2015 12:36:00 -0000	[thread overview]
Message-ID: <bug-64943-4-8TStqko4GE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64943-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
In principle, we do have a similar check in resolve.c's resolve_transfer. The
question is why it doesn't trigger.

  if (ts->type == BT_CLASS)
    {
      /* FIXME: Test for defined input/output.  */
      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->u.derived->attr.alloc_comp)
        {
          gfc_error ("Data transfer element at %L cannot have ALLOCATABLE "
                     "components unless it is processed by a defined "
                     "input/output procedure", &code->loc);
          return;


  parent reply	other threads:[~2015-02-05 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05  8:16 [Bug fortran/64943] New: " pault at gcc dot gnu.org
2015-02-05 12:14 ` [Bug fortran/64943] " dominiq at lps dot ens.fr
2015-02-05 12:36 ` burnus at gcc dot gnu.org [this message]
2015-02-05 12:39 ` burnus at gcc dot gnu.org
2015-02-05 21:59 ` burnus at gcc dot gnu.org
2015-02-05 22:00 ` 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-64943-4-8TStqko4GE@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).