------- Comment #13 from jv244 at cam dot ac dot uk 2006-12-02 13:55 ------- (In reply to comment #11) > Created an attachment (id=12724) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12724&action=view) [edit] > test case for interface "bl_copy"
> all_cp2k_gfortran.f90:418697.22: > USE f77_blas_generic > 1 > Error: Name 'bl_copy' at (1) is an ambiguous reference to 'bl_copy' from > current program unit > This is an error (see attachment) since the 'bl_copy' is only enhanced by the > second "interface bl_copy" (happily accepted by ifort, g95 and NAG f95). I don't think this is an error... you can add further compilers to the list of 'believers' xlf90 / pgf90. > > And g95 (after using VIRT=3GB of memory for 7m [on a 2GB system]): > virtual memory exhausted: Cannot allocate memory > compiles fine here. However, that's why I'm hoping that the gfortran crew adds this somewhere to a nightly tester. A whole list of commercial compilers failed (in the past years) to compile even single files with either memory explosions / infinite loops / ICEs ... this is particularly true if things like IPO are switched on. first things first however ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29975
