public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49540] New: [4.6/4.7 Regression] Memory-hot with large DATA stmt
Date: Mon, 27 Jun 2011 08:32:00 -0000 [thread overview]
Message-ID: <bug-49540-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49540
Summary: [4.6/4.7 Regression] Memory-hot with large DATA stmt
Product: gcc
Version: 4.6.1
Status: UNCONFIRMED
Keywords: memory-hog
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jakub@gcc.gnu.org
COMMON/A/B(100000,100)
DATA B/10000000*0.0/
END
used to compile in just a couple of MB of memory and fraction of a second, but
starting with
http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159076
it needs over 5GB of RAM and very long time.
That is only small fragment from original real-world testcase, which contains:
PARAMETER (MAXSTR=150001)
c...
COMMON/HJJET2/NSG,NJSG(MAXSTR),IASG(MAXSTR,3),K1SG(MAXSTR,100),
& K2SG(MAXSTR,100),PXSG(MAXSTR,100),PYSG(MAXSTR,100),
& PZSG(MAXSTR,100),PESG(MAXSTR,100),PMSG(MAXSTR,100)
c...
DATA NSG/0/,NJSG/150001*0/,IASG/450003*0/,
& K1SG/15000100*0/,K2SG/15000100*0/,
& PXSG/15000100*0.0/,PYSG/15000100*0.0/,PZSG/15000100*0.0/,
& PESG/15000100*0.0/,PMSG/15000100*0.0/
c...
END
c...
which compiled just fine with gcc up to 4.5.x and with 4.6/4.7 it is basically
out of any hope to compile it.
next reply other threads:[~2011-06-27 8:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 8:32 jakub at gcc dot gnu.org [this message]
2011-06-27 8:34 ` [Bug fortran/49540] [4.6/4.7 Regression] Memory-hog " jakub at gcc dot gnu.org
2011-06-27 8:35 ` jakub at gcc dot gnu.org
2011-06-27 15:53 ` burnus at gcc dot gnu.org
2011-06-27 16:25 ` burnus at gcc dot gnu.org
2011-06-27 16:26 ` jakub at gcc dot gnu.org
2011-06-27 17:12 ` burnus at gcc dot gnu.org
2011-06-27 17:23 ` burnus at gcc dot gnu.org
2011-06-28 9:00 ` adrian.sevcenco at cern dot ch
2011-06-28 12:20 ` burnus at gcc dot gnu.org
2011-06-29 16:55 ` jakub at gcc dot gnu.org
2011-06-30 10:26 ` jakub at gcc dot gnu.org
2011-06-30 13:56 ` [Bug fortran/49540] [4.6 " jakub at gcc dot gnu.org
2011-07-04 21:08 ` jakub at gcc dot gnu.org
2011-07-04 21:18 ` 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-49540-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).