This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/29975] [meta-bugs] ICEs with CP2K
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Dec 2006 14:44:46 -0000
- Subject: [Bug fortran/29975] [meta-bugs] ICEs with CP2K
- References: <bug-29975-6642@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #17 from burnus at gcc dot gnu dot org 2006-12-03 14:44 -------
> This fixes the INTERFACE part of the problem.
> I have not regtested the full suite yet; just gfortran.dg/i*
I just regression tested it on x86_64-unknown-linux-gnu.
I also tried to compile all_cp2k_gfortran.f90 -- and it compiles (gfortran -c)
ok.
The patch looks good -- and the test cases as well.
Just for completeness, the relevant part of the standard is:
"C1209 (R1206) A procedure-name shall not specify a procedure that is specified
previously in any procedure-stmt in any accessible interface with the same
generic identifier."
Note that this does not fix everything as gfortran rejects also interface_y.f90
if I comment the "call bl_copy(1.0, chr)"; if I understand the standard
correctly, the ambiguity is ok as long as one does not try to access bl_copy.
(And ifort/NAG f95 and sunf95 agree with me.)
Something which puzzles me is also the error message; one gets *twice*:
interface_y.f90:39.58:
USE f77_blas_extra ! { dg-error "Ambiguous|interfaces" }
1
Error: Ambiguous interfaces 'sdcopy' and 'recopy' in generic interface
'bl_copy' at (1)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975