[Bug fortran/49149] Dependency autogeneration with `-M` rendered useless by requiring .mod files

["zbeekman at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

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

--- Comment #13 from Zaak <zbeekman at gmail dot com> 2011-09-01 01:27:46 UTC ---
As for intrinsic F2003 modules, like ISO_C_BINDING, ISO_FORTRAN_ENV, etc. I
would expect the compiler to be able to handle this appropriately, i.e. not
require the presence of a iso_c_binding module in the build directory. Modules
which are provided as compiler extensions to the Fortran standard should also
be handled appropriately. My preference would be to exclude such intrinsic and
compiler extension modules from the dependency list, but if a .mod file is
installed with the compiler, the dependency could be given with a full path to
its location. I can't think of an occasion when you would need a path to these
intrinsic/extension modules, unless, perhaps, the tool were used while
developing the compiler itself.

Also, every time I read 'The dependencies take modules, Fortran's include, and
CPP's #include into account.' I can't help but think that the creators of this
feature were trying to make a useful tool which could handle Fortran specific,
especially module, dependency resolution.