This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/32147] Module file change due to order of writting out changes
- From: "tobi at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Oct 2007 17:34:02 -0000
- Subject: [Bug fortran/32147] Module file change due to order of writting out changes
- References: <bug-32147-14475@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #11 from tobi at gcc dot gnu dot org 2007-10-05 17:33 -------
Created an attachment (id=14305)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14305&action=view)
A patch
Wolfgang, this patch works for your testcase, but it is somewhat dependent on
the history of memory allocation during the compilation (i.e. if the relative
order of two pointers in memory is interchanged between compilations, the
module file may come out different). Therefore it may not work for large
source files where lots of memory is allocated and disallocated during
compilation.
Can you try this patch on a bigger project of yours to see if it's worth
incorporating?
--
tobi at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |tobi at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32147