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/20896] ambiguous interface not detected
Date: Wed, 27 Dec 2006 13:47:00 -0000 [thread overview]
Message-ID: <20061227134659.31535.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20896-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pault at gcc dot gnu dot org 2006-12-27 13:46 -------
Subject: Bug 20896
Author: pault
Date: Wed Dec 27 13:46:47 2006
New Revision: 120218
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120218
Log:
2006-12-27 Paul Thomas <pault@gcc.gnu.org>
PR fortran/20896
* interface.c (check_sym_interfaces): Try to resolve interface
reference as a global symbol, if it is not a nodule procedure.
(compare_actual_formal): Remove call to gfc_find_symbol; if
the expression is already a variable it is locally declared
and this has precedence.
gfortran.h : Add prototype for resolve_global_procedure.
resolve.c (resolve_global_procedure): Remove static attribute
from function declaration.
(resolve_fl_procedure): Remove symtree declaration and the
redundant check for an ambiguous procedure.
PR fortran/25135
* module.c (load_generic_interfaces): If the symbol is present
and is not generic it is ambiguous.
2006-12-27 Paul Thomas <pault@gcc.gnu.org>
PR fortran/20896
* gfortran.dg/interface_10.f90: New test.
* gfortran.dg/dummy_procedure_1.f90: Add error for call s1(z),
since z is already, locally a variable.
PR fortran/25135
* gfortran.dg/generic_11.f90: New test.
* gfortran.dg/interface_7.f90: Remove name clash between module
name and procedure 'x' referenced in the interface.
Added:
trunk/gcc/testsuite/gfortran.dg/generic_11.f90
trunk/gcc/testsuite/gfortran.dg/interface_10.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/interface.c
trunk/gcc/fortran/module.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/dummy_procedure_1.f90
trunk/gcc/testsuite/gfortran.dg/interface_7.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20896
next prev parent reply other threads:[~2006-12-27 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-20896-6642@http.gcc.gnu.org/bugzilla/>
2006-12-26 14:38 ` patchapp at dberlin dot org
2006-12-27 13:47 ` pault at gcc dot gnu dot org [this message]
2006-12-27 16:38 ` [Bug fortran/20896] [4.2 and 4.1 only] " pault at gcc dot gnu dot org
2007-01-02 14:23 ` pault at gcc dot gnu dot org
2007-01-03 18:05 ` patchapp at dberlin dot org
2007-01-21 20:41 ` jvdelisle at gcc dot gnu dot org
2007-01-31 9:55 ` burnus at gcc dot gnu dot org
2007-05-10 22:21 ` fxcoudert at gcc dot gnu dot org
2007-08-16 11:50 ` fxcoudert at gcc dot gnu dot org
2007-08-20 3:48 ` pault at gcc dot gnu dot org
2007-12-14 12:26 ` burnus at gcc dot gnu dot org
2007-12-17 18:05 ` [Bug fortran/20896] " dfranke at gcc dot gnu dot org
2009-04-14 14:50 ` dfranke at gcc dot gnu dot org
2009-04-14 15:05 ` dfranke at gcc dot gnu dot org
[not found] <bug-20896-4@http.gcc.gnu.org/bugzilla/>
2010-12-28 21:42 ` dfranke at gcc dot gnu.org
2005-04-08 16:05 [Bug fortran/20896] New: error needed jv244 at cam dot ac dot uk
2005-05-19 17:37 ` [Bug fortran/20896] ambiguous interface not detected tobi 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=20061227134659.31535.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).