public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/42175] Slow compile and much memory use at -O1
Date: Fri, 27 Nov 2009 12:13:00 -0000 [thread overview]
Message-ID: <20091127121310.6205.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42175-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from rguenth at gcc dot gnu dot org 2009-11-27 12:13 -------
At -O2 gcc 4.4 uses about 2.7GB ram and shows:
Execution times (seconds)
df reaching defs : 30.13 ( 6%) usr 7.70 (73%) sys 39.01 ( 8%) wall
0 kB ( 0%) ggc
df live regs : 14.44 ( 3%) usr 0.01 ( 0%) sys 14.51 ( 3%) wall
0 kB ( 0%) ggc
df live&initialized regs: 22.65 ( 5%) usr 0.00 ( 0%) sys 22.45 ( 5%) wall
0 kB ( 0%) ggc
df use-def / def-use chains: 4.86 ( 1%) usr 0.02 ( 0%) sys 4.67 ( 1%)
wall 0 kB ( 0%) ggc
tree SSA incremental : 23.30 ( 5%) usr 0.01 ( 0%) sys 23.00 ( 5%) wall
15627 kB ( 1%) ggc
tree operand scan : 17.51 ( 4%) usr 0.31 ( 3%) sys 17.91 ( 4%) wall
126792 kB ( 5%) ggc
tree PRE : 107.30 (23%) usr 0.43 ( 4%) sys 107.77 (22%) wall
53805 kB ( 2%) ggc
loop analysis : 130.15 (28%) usr 0.01 ( 0%) sys 130.09 (27%) wall
10542 kB ( 0%) ggc
TOTAL : 469.03 10.51 480.58
2378268 kB
There is a bug about the PRE slowness already, PR36439.
trunk uses about 3GB ram and shows:
ipa SRA : 6.41 ( 4%) usr 0.00 ( 0%) sys 6.44 ( 4%) wall
11215 kB ( 1%) ggc
df multiple defs : 8.56 ( 5%) usr 0.33 (13%) sys 8.84 ( 5%) wall
0 kB ( 0%) ggc
df reaching defs : 7.07 ( 4%) usr 0.16 ( 6%) sys 7.13 ( 4%) wall
0 kB ( 0%) ggc
df live regs : 9.98 ( 6%) usr 0.00 ( 0%) sys 9.77 ( 6%) wall
0 kB ( 0%) ggc
df live&initialized regs: 14.85 ( 9%) usr 0.01 ( 0%) sys 15.15 ( 9%) wall
0 kB ( 0%) ggc
tree VRP : 3.04 ( 2%) usr 0.09 ( 4%) sys 3.31 ( 2%) wall
123387 kB ( 6%) ggc
tree SSA incremental : 3.18 ( 2%) usr 0.02 ( 1%) sys 3.08 ( 2%) wall
12660 kB ( 1%) ggc
tree operand scan : 1.08 ( 1%) usr 0.25 (10%) sys 1.41 ( 1%) wall
113932 kB ( 6%) ggc
tree PRE : 4.12 ( 2%) usr 0.02 ( 1%) sys 4.32 ( 3%) wall
36286 kB ( 2%) ggc
expand : 7.74 ( 5%) usr 0.04 ( 2%) sys 7.26 ( 4%) wall
194890 kB (10%) ggc
loop analysis : 35.87 (21%) usr 0.02 ( 1%) sys 35.97 (21%) wall
7798 kB ( 0%) ggc
integrated RA : 7.26 ( 4%) usr 0.28 (11%) sys 7.81 ( 5%) wall
33879 kB ( 2%) ggc
reload : 6.23 ( 4%) usr 0.01 ( 0%) sys 6.24 ( 4%) wall
35384 kB ( 2%) ggc
reload CSE regs : 3.41 ( 2%) usr 0.00 ( 0%) sys 3.65 ( 2%) wall
30591 kB ( 2%) ggc
TOTAL : 169.84 2.56 172.43
1990005 kB
which is all reasonable again apart from "loop analysis".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42175
next prev parent reply other threads:[~2009-11-27 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 16:28 [Bug rtl-optimization/42175] New: " rguenth at gcc dot gnu dot org
2009-11-25 16:29 ` [Bug rtl-optimization/42175] " rguenth at gcc dot gnu dot org
2009-11-25 16:41 ` rguenth at gcc dot gnu dot org
2009-11-27 11:58 ` rguenth at gcc dot gnu dot org
2009-11-27 12:13 ` rguenth at gcc dot gnu dot org [this message]
2009-11-27 12:38 ` rguenth at gcc dot gnu dot org
2010-01-03 16:52 ` rguenth at gcc dot gnu dot org
2010-01-03 17:03 ` rguenth at gcc dot gnu dot org
2010-01-03 19:37 ` rakdver at kam dot mff dot cuni dot cz
[not found] <bug-42175-4@http.gcc.gnu.org/bugzilla/>
2014-01-15 15:22 ` 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=20091127121310.6205.qmail@sourceware.org \
--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).