public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54332] [4.8 Regression] 481.wrf in SPEC CPU 2006 takes > 10GB memory to compile
Date: Tue, 21 Aug 2012 19:08:00 -0000 [thread overview]
Message-ID: <bug-54332-4-lJoHKQLase@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54332-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54332
--- Comment #20 from dnovillo at google dot com <dnovillo at google dot com> 2012-08-21 19:07:33 UTC ---
On 2012-08-21 14:54 , hjl.tools at gmail dot com wrote:
> With --enable-gather-detailed-mem-stats, I got
>
> Alloc-pool Kind Elt size Pools Allocated (elts) Peak
> (elts) Leak (elts)
>
> -df_scan ref base 64 18 24808192( 387628) 11869056(
> 185454) 0( 0)
> -df_scan ref artificial 72 18 15168528( 210674) 2044944(
> 28402) 0( 0)
> +df_scan ref base 64 18 513091264( 8017051) 500077440(
> 7813710) 0( 0)
> +df_scan ref artificial 72 18 599905368( 8332019) 2044944(
> 28402) 0( 0)
> elt_loc_list 32 27 7982112( 249441) 2399488(
> 74984) 0( 0)
> -df_scan ref regular 72 18 71483184( 992822) 45955584(
> 638272) 0( 0)
> +df_scan ref regular 72 18 2091195360( 29044380) 2065579776(
> 28688608) 0( 0)
> df_scan insn 56 18 7681016( 137161) 3340848(
> 59658) 0( 0)
>
> -Total 15775 253131240
> +Total 16067 3345899232
>
That agrees with what I found, thanks. I've added a link to the
discussion about the df verifier. The vectors need to be cleared, but I
can't just free the vectors:
Stack vectors must be initially allocated with VEC_stack_alloc.
gcc/df-scan.c: In function 'unsigned int df_count_refs(bool, bool, bool)':
gcc/df-scan.c:1507:1: internal compiler error: in vec_reserve, at vec.h:1111
}
next prev parent reply other threads:[~2012-08-21 19:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 18:06 [Bug fortran/54332] New: " hjl.tools at gmail dot com
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 [this message]
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-lJoHKQLase@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).