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/49638] [OOP] length parameter is ignored when overriding type bound character functions with constant length.
Date: Sun, 07 Aug 2011 21:00:00 -0000	[thread overview]
Message-ID: <bug-49638-4-1jncpN8mFt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49638-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from janus at gcc dot gnu.org 2011-08-07 20:59:20 UTC ---
Author: janus
Date: Sun Aug  7 20:59:16 2011
New Revision: 177550

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=177550
Log:
2011-08-07  Janus Weil  <janus@gcc.gnu.org>
        Thomas Koenig  <tkoenig@gcc.gnu.org>

    PR fortran/49638
    * dependency.c (are_identical_variables): For dummy arguments only
    check for equal names, not equal symbols.
    * interface.c (gfc_check_typebound_override): Add checking for rank
    and character length.

2011-08-07  Janus Weil  <janus@gcc.gnu.org>

    PR fortran/49638
    * gfortran.dg/typebound_override_1.f90: New.

Added:
    trunk/gcc/testsuite/gfortran.dg/typebound_override_1.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/dependency.c
    trunk/gcc/fortran/interface.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-08-07 21:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05  8:04 [Bug fortran/49638] New: " boschmann at tp1 dot physik.uni-siegen.de
2011-07-30 16:16 ` [Bug fortran/49638] " janus at gcc dot gnu.org
2011-07-30 16:24 ` janus at gcc dot gnu.org
2011-07-31 11:05 ` janus at gcc dot gnu.org
2011-08-03 18:37 ` janus at gcc dot gnu.org
2011-08-03 18:53 ` janus at gcc dot gnu.org
2011-08-03 19:43 ` janus at gcc dot gnu.org
2011-08-03 20:20 ` janus at gcc dot gnu.org
2011-08-03 21:36 ` mikael at gcc dot gnu.org
2011-08-04  7:42 ` janus at gcc dot gnu.org
2011-08-04  8:10 ` burnus at gcc dot gnu.org
2011-08-04 11:00 ` janus at gcc dot gnu.org
2011-08-04 11:15 ` mikael at gcc dot gnu.org
2011-08-04 11:17 ` mikael at gcc dot gnu.org
2011-08-04 15:19 ` kargl at gcc dot gnu.org
2011-08-04 21:17 ` janus at gcc dot gnu.org
2011-08-07 10:13 ` janus at gcc dot gnu.org
2011-08-07 10:17 ` janus at gcc dot gnu.org
2011-08-07 21:00 ` janus at gcc dot gnu.org [this message]
2011-08-07 21:13 ` janus at gcc dot gnu.org
2011-08-20 19:31 ` janus at gcc dot gnu.org
2011-08-20 19:35 ` janus at gcc dot gnu.org
2011-08-21 21:26 ` 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-49638-4-1jncpN8mFt@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).