public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29652] ambiguous interface declaration undetected
Date: Thu, 23 Nov 2006 19:14:00 -0000	[thread overview]
Message-ID: <20061123191419.29868.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29652-6552@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from pault at gcc dot gnu dot org  2006-11-23 19:14 -------
Subject: Bug 29652

Author: pault
Date: Thu Nov 23 19:14:05 2006
New Revision: 119132

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=119132
Log:
2006-11-23 Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/25087
        * resolve.c (resolve_fl_procedure): Add an error if an external
        automatic character length function does not have an explicit
        interface.

        PR fortran/29652
        * interface.c (check_interface1): Use a local value, instead of
        the dummy, as the inner iterator over interface symbols.

        PR fortran/29820
        * trans-array.c (gfc_get_derived_type): Once done, spread the
        backend_decl to all identical derived types in all sibling
        namespaces.

2006-11-23 Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/25087
        * gfortran.dg/auto_char_len_4.f90: New test.

        PR fortran/29652
        * gfortran.dg/generic_7.f90: New test.
        * gfortran.dg/defined_operators_1.f90: Add new error.

        PR fortran/29820
        * gfortran.dg/used_types_13.f90: New test.



Added:
    branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/auto_char_len_4.f90
    branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/generic_7.f90
    branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/used_types_13.f90
Modified:
    branches/gcc-4_2-branch/gcc/fortran/ChangeLog
    branches/gcc-4_2-branch/gcc/fortran/interface.c
    branches/gcc-4_2-branch/gcc/fortran/resolve.c
    branches/gcc-4_2-branch/gcc/fortran/trans-types.c
    branches/gcc-4_2-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/defined_operators_1.f90


-- 


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


  parent reply	other threads:[~2006-11-23 19:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 14:55 [Bug fortran/29652] New: " franke dot daniel at gmail dot com
2006-10-31  5:41 ` [Bug fortran/29652] " pault at gcc dot gnu dot org
2006-11-15 18:25 ` patchapp at dberlin dot org
2006-11-15 18:58 ` pault at gcc dot gnu dot org
2006-11-22  0:02 ` pault at gcc dot gnu dot org
2006-11-23 19:14 ` pault at gcc dot gnu dot org [this message]
2006-11-23 19:18 ` pault at gcc dot gnu dot 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=20061123191419.29868.qmail@sourceware.org \
    --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).