This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/54107] [4.8 Regression] Memory hog with abstract interface
- From: "janus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 27 Jan 2013 09:46:02 +0000
- Subject: [Bug fortran/54107] [4.8 Regression] Memory hog with abstract interface
- Auto-submitted: auto-generated
- References: <bug-54107-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54107
--- Comment #20 from janus at gcc dot gnu.org 2013-01-27 09:46:02 UTC ---
(In reply to comment #18)
> (In reply to comment #15)
> > Here is a new patch, which does some further cleanup, such as removing the
> > 'formal' and 'formal_ns' members of gfc_component (which are not used any
> > more).
>
> This implies a module version bump. :-(
I actually thought that the module version had already been bumped for 4.8. At
least this is claimed at http://gcc.gnu.org/wiki/GFortran#GCC4.8.
However, I just had a look into module.c in 4.7 and trunk, and both show:
#define MOD_VERSION "9"
I'm confused ...
> If you are into removing things, maybe the resolve_structure_cons hunk can go
> too.
Ah, yes.
> > Further, I removed the class.c part (I don't really see how it is related to
> > the rest of the patch).
>
> The point was to avoid the _copy member having no interface. I don't remember
> if I did this while systematically checking uses of formal/interface or if it
> was fixing a regression; I think it was the latter. Bah, if it works...
Huh, I'm not really sure if we really need the interface for the case of an
ABSTRACT or unlimited polymorphic type (I'd rather think that we don't).
But if you have a case where this makes trouble, it should surely be fixed.
Otherwise: If it ain't broke, don't try to fix fix it ... ;)