From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4856 invoked by alias); 22 Oct 2007 07:35:41 -0000 Received: (qmail 4799 invoked by uid 48); 22 Oct 2007 07:35:32 -0000 Date: Mon, 22 Oct 2007 07:35:00 -0000 Message-ID: <20071022073532.4798.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/30285] gfortran excessive memory usage with COMMON blocks in modules In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "anlauf at gmx dot de" 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 X-SW-Source: 2007-10/txt/msg01932.txt.bz2 ------- Comment #13 from anlauf at gmx dot de 2007-10-22 07:35 ------- I've adjusted the title slightly to refer to the use of COMMON blocks (in MPICH, OpenMPI) because the problem of .mod size excursion depends only on the "nesting depth", not on the actual size of the modules. I hope this bug will be fixed someday when somebody has a look either at the module writing routines or at the way the structures containing module information are held internally. I am unable to compile a reasonably large project (just in terms of the number of files, not total source code size!) using MPI. The problem appears even worse with OpenMPI than with MPICH. -- anlauf at gmx dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|gfortran excessive memory |gfortran excessive memory |usage with large modules |usage with COMMON blocks in | |modules http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30285