public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44563] GCC uses a lot of RAM when compiling a large numbers of functions
Date: Mon, 13 Dec 2010 13:22:00 -0000 [thread overview]
Message-ID: <bug-44563-4-9DkbIB7Fqc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44563-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44563
--- Comment #11 from Jan Hubicka <hubicka at gcc dot gnu.org> 2010-12-13 13:22:28 UTC ---
Patched compiler at -O2 now shows:
integration : 166.20 (16%) usr 0.19 ( 1%) sys 166.86 (15%) wall
92691 kB ( 4%) ggc
tree CCP : 792.75 (74%) usr 0.15 ( 1%) sys 794.63 (73%) wall
66560 kB ( 3%) ggc
integration is probably the overhead of splitting BBs, I wonder what makes tree
CCP so slow, it is probably worth investigating.
The profile shows:
2009425 73.3643 cc1 cc1
gsi_for_stmt
398058 14.5331 cc1 cc1
gimple_set_bb
22230 0.8116 libc-2.11.1.so libc-2.11.1.so _int_malloc
14339 0.5235 cc1 cc1
gimple_split_block
11727 0.4282 libc-2.11.1.so libc-2.11.1.so memset
10411 0.3801 libc-2.11.1.so libc-2.11.1.so _IO_vfscanf
9095 0.3321 cc1 cc1 htab_delete
6061 0.2213 cc1 cc1
bitmap_set_bit
5990 0.2187 no-vmlinux no-vmlinux /no-vmlinux
5912 0.2158 libc-2.11.1.so libc-2.11.1.so _int_free
5077 0.1854 libc-2.11.1.so libc-2.11.1.so
malloc_consolidate
4516 0.1649 cc1 cc1
htab_find_slot_with_hash
4515 0.1648 opreport opreport
/usr/bin/opreport
4284 0.1564 libc-2.11.1.so libc-2.11.1.so free
4234 0.1546 libc-2.11.1.so libc-2.11.1.so malloc
4106 0.1499 cc1 cc1
htab_traverse_noresize
3737 0.1364 libc-2.11.1.so libc-2.11.1.so calloc
3197 0.1167 cc1 cc1 eq_node
2996 0.1094 cc1 cc1
df_note_compute
2632 0.0961 cc1 cc1
ggc_internal_alloc_stat
2476 0.0904 cc1 cc1
bitmap_bit_p
Other passes are sub 10s each.
Maybe tree-ccp just gets the overhead of merging the large BBs into single?
Honza
next prev parent reply other threads:[~2010-12-13 13:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-44563-4@http.gcc.gnu.org/bugzilla/>
2010-12-12 23:55 ` 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 [this message]
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
2024-02-16 13:52 ` rguenth at gcc dot gnu.org
2010-06-17 4:10 [Bug c/44563] New: " jvoss at altsci dot com
2010-06-17 4:14 ` [Bug tree-optimization/44563] " jvoss at altsci dot com
2010-06-17 10:37 ` rguenth at gcc dot gnu dot org
2010-06-17 10:45 ` rguenth at gcc dot gnu dot org
2010-06-17 12:28 ` jakub at gcc dot gnu dot 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-9DkbIB7Fqc@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).