This is the mail archive of the
mailing list for the GCC project.
Re: [Patch, fortran] PR24398 - broken module files
As it happens, I have not yet applied the patch because I am doing
house-husband duty and our daughter is unwell.
A version number could
easily be added. I wonder what should trigger the number changes?
Changes to .mod files themselves, which would be my choice, or to the
library or the gcc version number?
I guess having (in module.c):
#define CURRENT_GCC_BRANCH 4.2
#define CURRENT_MODFILE_VERSION 7
would ensure that within each release series (4.2, 4.3, etc.) the
CURRENT_MODFILE_VERSION is the right condition to make decisions.