From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3756 invoked by alias); 25 Jun 2013 18:06:39 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 3662 invoked by uid 48); 25 Jun 2013 18:06:30 -0000 From: "anlauf at gmx dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/40958] module files too large Date: Tue, 25 Jun 2013 18:06:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gmx dot de X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-06/txt/msg01499.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40958 Harald Anlauf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gmx dot de --- Comment #16 from Harald Anlauf --- (In reply to Dominique d'Humieres from comment #15) > > However, the fundamental(?) issue of module sizes growing exponentially > > with deep module hierarchies still remains. The solution to that is to > > not include transitive dependencies, which in turn would require a module > > cache for good performance. Whether that is worth doing, and who is willing > > and able to do it, is unclear. > > Would not it be simpler to tell the users what they should do to avoid this > issue? If yes, what would be the basic rules? I doubt that this is the right answer. The user wants to write maintainable and portable code. The paradigm of object-oriented programming will more often lead to deeper module hierarchies than simple code. You'd had a hard time to tell users that gfortran requires to flatten those hierarchies when other compilers don't (assuming that the others perform acceptably).