http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25708
--- Comment #12 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-04-04 12:27:28 UTC --- (In reply to comment #11) > An associated issue is the size of module files. Joost suggested to cut down the string tags "d" instead of "dimension", "al" instead of "allocatable" or something like that. That would help with the file size, the I/O (also: I/O caching), and the string parsing. > Clearly, where a module uses > another module, we could help by inserting use statements in the module file. There are pro and cons doing so. For binary-only code, it is much more convenient to ship only a single ".mod" instead of several - that was at least a complaint I have heard about NAG's compiler. Though, having by default a simple "use" in the .mod file would help. Another thing which could help is to read a .mod file only once per translation unit (source file) instead of every time a USE statement is encountered.
