This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/33542] gfortran does not detect ambigious specific names if they are the same as generic names
- From: "pault at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Oct 2007 16:52:04 -0000
- Subject: [Bug fortran/33542] gfortran does not detect ambigious specific names if they are the same as generic names
- References: <bug-33542-13404@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #9 from pault at gcc dot gnu dot org 2007-10-12 16:52 -------
Subject: Bug 33542
Author: pault
Date: Fri Oct 12 16:51:53 2007
New Revision: 129268
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129268
Log:
2007-10-12 Paul Thomas <pault@gcc.gnu.org>
PR fortran/33542
* resolve.c (resolve_actual_arglist): If the actual argument is
ambiguous, then there is an error.
2007-10-12 Paul Thomas <pault@gcc.gnu.org>
PR fortran/33542
* gfortran.dg/ambiguous_specific_1.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/ambiguous_specific_1.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33542