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/56284] [OOP] ICE with alternate return in type-bound procedure
Date: Mon, 11 Feb 2013 10:09:00 -0000	[thread overview]
Message-ID: <bug-56284-4-2yAvnYXXf7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56284-4@http.gcc.gnu.org/bugzilla/>


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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[OOP] ICE with contained    |[OOP] ICE with alternate
                   |routine which               |return in type-bound
                   |inappropriately compares a  |procedure
                   |string and a number         |

--- Comment #3 from janus at gcc dot gnu.org 2013-02-11 10:09:39 UTC ---
(In reply to comment #2)
> 
>   subroutine getRecord ( * )
>   end subroutine

Ok, I admit that I had to look up the asterisk thingy. It's called "alternate
return" and is a obsolescent feature since at least F95.

According to PR 40881, we should have a warning message for this, but it does
not seem to trigger for the test case here. Should be fixed I guess (just as
the ICE, although combining obsolescent features like alternate return with new
stuff such as type binding is surely not recommended).


  parent reply	other threads:[~2013-02-11 10:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  8:58 [Bug fortran/56284] New: ICE with contained routine which inappropriately compares a string and a number arjen.markus at deltares dot nl
2013-02-11  9:02 ` [Bug fortran/56284] " arjen.markus at deltares dot nl
2013-02-11  9:51 ` [Bug fortran/56284] [OOP] " janus at gcc dot gnu.org
2013-02-11 10:09 ` janus at gcc dot gnu.org [this message]
2013-02-11 12:17 ` [Bug fortran/56284] [OOP] ICE with alternate return in type-bound procedure janus at gcc dot gnu.org
2013-02-11 12:37 ` janus at gcc dot gnu.org
2013-02-11 13:57 ` janus at gcc dot gnu.org
2013-02-11 19:06 ` dominiq at lps dot ens.fr
2013-02-11 19:46 ` janus at gcc dot gnu.org
2013-02-12 12:58 ` dominiq at lps dot ens.fr
2013-02-12 13:31 ` janus at gcc dot gnu.org
2013-04-03  7:51 ` 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-56284-4-2yAvnYXXf7@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).