public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54332] New: [4.8 Regression] 481.wrf in SPEC CPU 2006 takes > 10GB memory to compile Date: Mon, 20 Aug 2012 18:06:00 -0000 [thread overview] Message-ID: <bug-54332-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54332 Bug #: 54332 Summary: [4.8 Regression] 481.wrf in SPEC CPU 2006 takes > 10GB memory to compile Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com On Linux/x86-64, revision 190521 takes > 10 GB memory to compile 481.wrf in SPEC CPU 2006: gfortran -c -o module_domain.fppized.o -I. -I./netcdf/include -O3 -funroll-loops -ffast-math -frecord-marker=4 module_domain.fppized.f90
next reply other threads:[~2012-08-20 18:06 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-20 18:06 hjl.tools at gmail dot com [this message] 2012-08-20 20:53 ` [Bug fortran/54332] " hjl.tools at gmail dot com 2012-08-20 21:18 ` hjl.tools at gmail dot com 2012-08-20 21:21 ` steven at gcc dot gnu.org 2012-08-20 21:42 ` hjl.tools at gmail dot com 2012-08-21 2:59 ` hjl.tools at gmail dot com 2012-08-21 8:26 ` rguenth at gcc dot gnu.org 2012-08-21 13:39 ` dnovillo at google dot com 2012-08-21 13:58 ` hjl.tools at gmail dot com 2012-08-21 14:07 ` dnovillo at google dot com 2012-08-21 16:21 ` hjl.tools at gmail dot com 2012-08-21 16:44 ` dnovillo at google dot com 2012-08-21 16:52 ` hjl.tools at gmail dot com 2012-08-21 16:56 ` dnovillo at gcc dot gnu.org 2012-08-21 17:10 ` hjl.tools at gmail dot com 2012-08-21 17:41 ` hjl.tools at gmail dot com 2012-08-21 17:58 ` hjl.tools at gmail dot com 2012-08-21 18:09 ` hjl.tools at gmail dot com 2012-08-21 18:19 ` dnovillo at google dot com 2012-08-21 18:32 ` dnovillo at google dot com 2012-08-21 18:55 ` hjl.tools at gmail dot com 2012-08-21 19:08 ` dnovillo at google dot com 2012-08-21 19:20 ` steven at gcc dot gnu.org 2012-08-21 19:28 ` hjl.tools at gmail dot com 2012-08-21 19:50 ` dnovillo at google dot com 2012-08-21 19:53 ` hjl.tools at gmail dot com 2012-08-21 20:49 ` dnovillo at google dot com 2012-08-21 21:07 ` hjl at gcc dot gnu.org 2012-08-21 21:11 ` hjl.tools at gmail dot com 2012-08-22 9:02 ` [Bug middle-end/54332] " steven 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-54332-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: linkBe 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).