[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Bug fortran/42607] add information about how to compile a module




------- Comment #4 from jv244 at cam dot ac dot uk  2010-04-02 05:29 -------
(In reply to comment #2)
> I think .mod files are not obvious; the standard does not say anything about
> them, though (almost?) all compilers use them. On the other hand, few people
> seem to have problems with .mod files.

the current Cray compiler (from cce) does not have modules, the mod info ends
up in the .o files.

one thing that could be documented about the gfortran mod files is that they
are left untouched if possible. We use that in our makefile to avoid
recompilation cascades. This is actually an important feature for developers,
since it makes gfortran much faster for development than many of the other
compilers.

Furthermore, the fact that left-over mod files from older/newer gfortran
compilers leads to user-visible error messages could also be worth documenting
(At least state that even though .o, .a and .so files might be 'ABI-compatible'
over several versions of the compiler, .mod files a specific to even a minor
version of the compiler). 


-- 


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

------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.


Reply to: