public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <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: Fri, 13 Mar 2015 08:43:00 -0000 [thread overview]
Message-ID: <bug-44563-4-xuoa8YuCYV@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|tree-optimization |ipa
Known to fail| |5.0
--- Comment #30 from Richard Biener <rguenth at gcc dot gnu.org> ---
With all the patches I have for now we end up with a pure IPA issue:
phase opt and generate : 193.97 (99%) usr 13.82 (93%) sys 207.75 (99%) wall
3311016 kB (94%) ggc
ipa inlining heuristics : 140.48 (72%) usr 0.44 ( 3%) sys 141.13 (67%) wall
396289 kB (11%) ggc
dominance computation : 2.99 ( 2%) usr 1.00 ( 7%) sys 3.89 ( 2%) wall
0 kB ( 0%) ggc
integrated RA : 4.05 ( 2%) usr 0.85 ( 6%) sys 5.26 ( 3%) wall
1577496 kB (45%) ggc
rest of compilation : 6.53 ( 3%) usr 1.67 (11%) sys 7.91 ( 4%) wall
155664 kB ( 4%) ggc
unaccounted todo : 3.82 ( 2%) usr 1.07 ( 7%) sys 4.98 ( 2%) wall
0 kB ( 0%) ggc
TOTAL : 195.46 14.79 210.23
3514948 kB
everything <= 1% dropped. I wonder what that unaccounted todo is ;)
next prev parent reply other threads:[~2015-03-13 8:43 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 ` rguenth at gcc dot gnu.org [this message]
2015-03-13 8:47 ` [Bug ipa/44563] " 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
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-xuoa8YuCYV@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).