public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/44563] GCC uses a lot of RAM when compiling a large numbers of functions
Date: Mon, 16 Mar 2015 00:07:00 -0000 [thread overview]
Message-ID: <bug-44563-4-wXskHdruCs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44563-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44563
--- Comment #34 from Jan Hubicka <hubicka at ucw dot cz> ---
The problem is (as described earlier) the fact htat we sum size of all call
statmts
in function after every inline decision.
Most of time is spent in calling estimate_edge_size_and_time:
79.95% cc1 cc1 [.]
_ZL28estimate_calls_size_and_timeP11cgraph_nodePiS1_S1_S1_j3vecIP9tree_node7va_heap6vl_ptrES2_I28ipa_polymorphic_call_contextS5_S6_ES2_IP21ipa_agg
2.21% cc1 libc-2.13.so [.] _int_malloc
0.59% cc1 libc-2.13.so [.] _int_free
Updating summaries incrementally will solve it but at the moment do not see any
really simple change for GCC-5 (i looked at this code couple times already
because of this PR)
Honza
next prev parent reply other threads:[~2015-03-16 0:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-44563-4@http.gcc.gnu.org/bugzilla/>
2010-12-12 23:55 ` [Bug tree-optimization/44563] " hubicka at gcc dot gnu.org
2010-12-13 0:58 ` hubicka at gcc dot gnu.org
2010-12-13 1:00 ` hubicka at gcc dot gnu.org
2010-12-13 1:07 ` hubicka at gcc dot gnu.org
2010-12-13 1:17 ` hubicka at gcc dot gnu.org
2010-12-13 1:47 ` hubicka at gcc dot gnu.org
2010-12-13 13:22 ` hubicka at gcc dot gnu.org
2010-12-17 0:08 ` hubicka at gcc dot gnu.org
2015-03-07 0:22 ` hubicka at gcc dot gnu.org
2015-03-09 9:36 ` rguenth at gcc dot gnu.org
2015-03-09 11:33 ` rguenth at gcc dot gnu.org
2015-03-09 15:26 ` rguenth at gcc dot gnu.org
2015-03-09 15:36 ` rguenth at gcc dot gnu.org
2015-03-10 4:55 ` hubicka at ucw dot cz
2015-03-10 8:26 ` rguenth at gcc dot gnu.org
2015-03-10 8:35 ` rguenther at suse dot de
2015-03-10 11:54 ` rguenth at gcc dot gnu.org
2015-03-10 12:03 ` rguenth at gcc dot gnu.org
2015-03-10 12:31 ` jakub at gcc dot gnu.org
2015-03-10 12:44 ` rguenth at gcc dot gnu.org
2015-03-10 12:51 ` rguenther at suse dot de
2015-03-10 13:19 ` rguenth at gcc dot gnu.org
2015-03-12 15:09 ` rguenth at gcc dot gnu.org
2015-03-13 8:43 ` [Bug ipa/44563] " rguenth at gcc dot gnu.org
2015-03-13 8:47 ` rguenth at gcc dot gnu.org
2015-03-13 8:53 ` rguenth at gcc dot gnu.org
2015-03-13 8:55 ` rguenth at gcc dot gnu.org
2015-03-16 0:07 ` hubicka at ucw dot cz [this message]
2024-02-16 13:52 ` rguenth 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-44563-4-wXskHdruCs@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).