This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Dear All, Reinhold Bader has pointed out the naming the submodule files after the submodule name and using .mod as the extension can potentially lead to clashes. Therefore, I have written a patch to change gfortran to follow the naming convention of another leading brand: submodule filename = module@ancestor@....@submodule.smod The implementation is straightforward and the ChangeLog and the patch provide an adequate description. Bootstraps and regtests on x86_64 - OK for trunk? Paul 2015-07-14 Paul Thomas <pault@gcc.gnu.org> PR fortran/52846 * gfortran.h : Add 'submodule_name' to gfc_use_list structure. * module.c (gfc_match_submodule): Define submodule_name and add static 'submodule_name'. (gfc_match_submodule): Build up submodule filenames, using '@' as a delimiter. Store the output filename in 'submodule_name'. (gfc_dump_module): If current state is COMP_SUBMODULE, write to file 'submodule_name', using SUBMODULE_EXTENSION. (gfc_use_module): Similarly, use the 'submodule_name' field in the gfc_use_list structure and SUBMODULE_EXTENSION to read the implicitly used submodule files.
Attachment:
filename.diff
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |