http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51727
Bug #: 51727
Summary: Changing module files
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: mik...@gcc.gnu.org
Reported at http://gcc.gnu.org/ml/fortran/2011-12/msg00148.html
For a given fortran source file with module(s), repeated compilations may not
create always the same module file. The URL above provides an example.
It seems that the symbols are not output in the same order. In the example
provided, there are two module variants, the difference between them being that
one single symbol is at a different place in the file ( as reported at
http://gcc.gnu.org/ml/fortran/2011-12/msg00163.html ).
Possible causes:
- unitialized memory, though valgrind reported nothing for me.
- tree rebalancing. Module I/O manages structures to be serialized using a
global tree ordered (when writing) by structures' addresses. Could an
unrepeatable order just mean an unrepeatable address?.
