public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57966] [OOP] Using a TBP to specify the shape of a dummy argument
Date: Thu, 25 Jul 2013 09:10:00 -0000	[thread overview]
Message-ID: <bug-57966-4-PI6ZLvG9pv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57966-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from janus at gcc dot gnu.org ---
(In reply to janus from comment #3)
> (In reply to janus from comment #2)
> > Draft patch (not regtested yet):
> 
> Seems to survive the regtest without any failures

However, it ICEs on the following variant (which involves a GENERIC TBP):


MODULE my_mod
  IMPLICIT NONE

  TYPE config_cls
  CONTAINS
    PROCEDURE, NOPASS :: my_size
    GENERIC :: sz => my_size
  END TYPE

  TYPE(config_cls) :: config

CONTAINS

  PURE INTEGER FUNCTION my_size()
    my_size = 10
  END FUNCTION

  SUBROUTINE my_sub( field )
    REAL :: field( config%sz() )
  END SUBROUTINE

END MODULE


With an unpatched gfortran, this yields the same (bogus) error as comment 0.
Unfortunately ifort 12.1.2 ICEs on this variant (and I don't have access to a
newer version), but after all I assume it is valid.


  parent reply	other threads:[~2013-07-25  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 10:40 [Bug fortran/57966] New: " stefan.mauerberger at gmail dot com
2013-07-24 11:34 ` [Bug fortran/57966] [OOP] " janus at gcc dot gnu.org
2013-07-24 12:17 ` janus at gcc dot gnu.org
2013-07-24 14:39 ` janus at gcc dot gnu.org
2013-07-24 23:03 ` burnus at gcc dot gnu.org
2013-07-25  9:10 ` janus at gcc dot gnu.org [this message]
2013-07-25  9:23 ` burnus at gcc dot gnu.org
2013-07-25 12:29 ` janus at gcc dot gnu.org
2013-07-25 13:57 ` janus 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-57966-4-PI6ZLvG9pv@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).