[Patch, fortran] PR33542 - gfortran does not detect ambigious specific names if they are the same as generic names

Jerry DeLisle jvdelisle@verizon.net
Sun Oct 7 19:40:00 GMT 2007


Paul Richard Thomas wrote:
> :ADDPATCH fortran:
> 
> This is the obvious version of the 'obvious' patch that wasn't.  Sorry
> about the last mess.
> 
> The general rule is that use associated symbols can be ambiguous just
> as long as they are not referenced.  This is done so that other
> symbols may be used from these modules that are not ambiguous, without
> necessitating only clauses.
> 
> In the case of this PR, the symtree for 'foo' is ambiguous, where
> there are two identically named specific procedures.  Thus, the trick
> is to make sure this is detected when resolving the actual argument.
> The testcase is the original..
> 
> This time, I have tested tonto-2.3 with the patch, as well as
> bootstrapping and regtesting.
> 
> OK for trunk?
> 
> Paul
> 
> 2007-10-07  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-07  Paul Thomas  <pault@gcc.gnu.org>
> 
> 	PR fortran/33542
> 	* gfortran.dg/ambiguous_specific_1.f90: New test.
> 
> 
> 
OK



More information about the Fortran mailing list