public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "antony at cosmologist dot info" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60255] New: Deferred character length variable at (1) cannot yet be associated with unlimited polymorphic entities
Date: Tue, 18 Feb 2014 00:03:00 -0000	[thread overview]
Message-ID: <bug-60255-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60255
           Summary: Deferred character length variable at (1) cannot yet
                    be associated with unlimited polymorphic entities
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: antony at cosmologist dot info

Created attachment 32157
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32157&action=edit
OOP module with derived TStringList implementing list of strings

Attached file gives multiple repeated errors

ObjectLists2.f90:818.26:

    end module ObjectLists
                          1
Error: TODO: Deferred character length variable at (1) cannot yet be associated
with unlimited polymorphic entities


It should surely give a line number of the error rather than end of module
(currently very hard to workaround as origin of error is unclear). Better,
actually compile (tested valid in ifort 14).


             reply	other threads:[~2014-02-18  0:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  0:03 antony at cosmologist dot info [this message]
2014-02-18  2:00 ` [Bug fortran/60255] " kargl at gcc dot gnu.org
2014-02-18  9:09 ` janus at gcc dot gnu.org
2014-02-18 14:20 ` janus at gcc dot gnu.org
2014-02-19 10:06 ` dominiq at lps dot ens.fr
2014-02-19 12:08 ` janus at gcc dot gnu.org
2014-02-27 14:30 ` antony at cosmologist dot info
2015-01-18 22:02 ` [Bug fortran/60255] [OOP] " pault at gcc dot gnu.org
2015-01-23 10:56 ` vehre at gmx dot de
2015-03-23 12:57 ` vehre 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-60255-4@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).