public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bastian.feigl at kit dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59811] New: Huge increase in memory usage and compile time with gfortran 4.8
Date: Tue, 14 Jan 2014 17:30:00 -0000	[thread overview]
Message-ID: <bug-59811-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59811

            Bug ID: 59811
           Summary: Huge increase in memory usage and compile time with
                    gfortran 4.8
           Product: gcc
           Version: 4.8.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bastian.feigl at kit dot edu

Created attachment 31833
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31833&action=edit
Example fortran source code file with problems with gfortran 4.8

When switching from gfortran 4.7 to gfortran 4.8 the memory usage and compile
time vastly increases for some files in our project, e.g. for the attached
example file. gfortran 4.8.2 needs 50s to compile, using up to 1.7 GB of RAM,
while gfortran 4.7 compiles it in 7s with a memory usage of 136 MB.

The command line of the gfortran-call for the attached example is
/opt/gcc/4.8.2/bin/gfortran -fno-automatic -ffixed-line-length-none -O2 -c
FermionBoxEventempCoupling_Div.F -o output.o 

The problem seems to be partly linked to the option -fno-automatic, since
omitting it inhibits the memory increase, but the compile time is still 14s
with gfortran 4.8, compared to 6s with gfortran 4.7.

The problem arises with optimizations -O2 and -O1 lead to a similar
discrepancy, with -O0 the problem does not exist.

The gfortran 4.8 which shows the problematic behaviour is built with:
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.8.2/configure --prefix=/opt/gcc/4.8.2
--enable-languages=c,c++,fortran
gcc version 4.8.2 (GCC) 

The gfortran 4.7 is the built-in from openSUSE 12.2:
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.7
--enable-ssp --disable-libssp --disable-libitm --disable-plugin
--with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--disable-libgcj --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib
--enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --enable-linker-build-id
--program-suffix=-4.7 --enable-linux-futex --without-system-libunwind
--with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux
gcc version 4.7.1 20120723 [gcc-4_7-branch revision 189773] (SUSE Linux)


             reply	other threads:[~2014-01-14 17:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 17:30 bastian.feigl at kit dot edu [this message]
2014-01-15 12:06 ` [Bug rtl-optimization/59811] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2014-01-15 13:53 ` [Bug rtl-optimization/59811] [4.8/4.9 Regression] Huge increase in memory usage and compile time in combine rguenth at gcc dot gnu.org
2014-01-22 15:01 ` jakub at gcc dot gnu.org
2014-01-22 15:16 ` jakub at gcc dot gnu.org
2014-01-31 11:35 ` rguenth at gcc dot gnu.org
2014-01-31 11:41 ` jakub at gcc dot gnu.org
2014-01-31 11:48 ` rguenther at suse dot de
2014-05-22  9:02 ` [Bug rtl-optimization/59811] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:29 ` [Bug rtl-optimization/59811] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23  8:23 ` [Bug rtl-optimization/59811] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 19:59 ` [Bug rtl-optimization/59811] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-59811-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).