------- Comment #3 from dominiq at lps dot ens dot fr  2007-10-02 10:05 -------
Works as advertised without regression on PPC Darwin.
However there may be room for improvements for the error message:

pr33542.f90:24.9:

   USE M1
        1
Error: Ambiguous interfaces 'foo2' and 'foo2' in generic interface 'foo' at (1)

and

pr33542_1.f90:24.9:

   USE M1
        1
Error: Ambiguous interfaces 'foo' and 'foo' in generic interface 'foo' at (1)

g95 gives no such error for the first case and

In file pr33542_1.f90:28

   CALL FOO(10)
           1
Error: Name 'foo' at (1) is an ambiguous reference to 'foo' from module 'm1'
In file pr33542_1.f90:29

   CALL FOO(10.)
           1
Error: Name 'foo' at (1) is an ambiguous reference to 'foo' from module 'm1'
In file pr33542_1.f90:30

   CALL BAR(foo)
               1
Error: Symbol 'foo' at (1) is defined in multiple modules

for the second, though I don't really understand the ambiguity!-(is this
because the interfaces appear in different modules?)

Note that gcc version 4.0.3 (g95 0.91!) Jul 26 2007 rejects the first case, but
not gcc version 4.0.3 (g95 0.91!) Sep 25 2007, and xlf complains only about
"Generic procedure names are not permitted as actual arguments." for the first
case.


-- 


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

Reply via email to