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 01:47:00 -0000 [thread overview]
Message-ID: <bug-44563-4-3TEugE2jpU@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 #10 from Jan Hubicka <hubicka at gcc dot gnu.org> 2010-12-13 01:46:39 UTC ---
Created attachment 22730
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22730
Fix for inline cost problem
The attached patch fixes the inliner cost problem so we converge at -O1. It is
bit brute force, but I guess it should work well in practice. With the fix -O1
converges in 90 secons.
Profile is similar to one at -O0
14898 6.7090 libc-2.11.1.so libc-2.11.1.so _int_malloc
7981 3.5941 cc1 cc1
bitmap_set_bit
5993 2.6988 libc-2.11.1.so libc-2.11.1.so memset
5063 2.2800 cc1 cc1 htab_delete
4091 1.8423 libc-2.11.1.so libc-2.11.1.so _IO_vfscanf
3849 1.7333 no-vmlinux no-vmlinux /no-vmlinux
3807 1.7144 libc-2.11.1.so libc-2.11.1.so _int_free
3632 1.6356 cc1 cc1
df_note_compute
3469 1.5622 libc-2.11.1.so libc-2.11.1.so
malloc_consolidate
3352 1.5095 libc-2.11.1.so libc-2.11.1.so
msort_with_tmp
2978 1.3411 cc1 cc1
htab_traverse_noresize
2941 1.3244 libc-2.11.1.so libc-2.11.1.so free
2824 1.2717 cc1 cc1
bitmap_clear_bit
2653 1.1947 cc1 cc1
df_ref_create_structure
2429 1.0938 libc-2.11.1.so libc-2.11.1.so malloc
2239 1.0083 cc1 cc1
df_insn_refs_collect
next prev parent reply other threads:[~2010-12-13 1:47 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 [this message]
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
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-3TEugE2jpU@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).