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:07:00 -0000	[thread overview]
Message-ID: <bug-44563-4-VTYnPubC9c@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 #8 from Jan Hubicka <hubicka at gcc dot gnu.org> 2010-12-13 01:07:33 UTC ---
My profile was at -O2.  Concerning Jakub's callgrind, the -O0 compilation
finishes in about 44s for me. Profile is:
4349      3.8607  libc-2.11.1.so           libc-2.11.1.so           _int_malloc
3150      2.7963  cc1                      cc1                     
record_reg_classes.constprop.9
2881      2.5575  cc1                      cc1                     
htab_find_slot_with_hash
2104      1.8678  cc1                      cc1                     
ggc_set_mark
2039      1.8101  libc-2.11.1.so           libc-2.11.1.so          
msort_with_tmp
2005      1.7799  cc1                      cc1                     
bitmap_set_bit
1836      1.6299  cc1                      cc1                     
df_ref_create_structure
1775      1.5757  cc1                      cc1                     
find_reloads
1738      1.5429  cc1                      cc1                     
ggc_internal_alloc_stat
1538      1.3653  libc-2.11.1.so           libc-2.11.1.so           memset
1430      1.2694  cc1                      cc1                      eq_node
1375      1.2206  cc1                      cc1                     
preprocess_constraints
1317      1.1691  libc-2.11.1.so           libc-2.11.1.so           _int_free
1309      1.1620  cc1                      cc1                     
df_insn_refs_collect
1289      1.1443  cc1                      cc1                     
ix86_function_arg_regno_p
1277      1.1336  cc1                      cc1                     
df_ref_record
1249      1.1088  cc1                      cc1                     
ix86_save_reg
1215      1.0786  cc1                      cc1                     
ix86_compute_frame_layout
1171      1.0395  libc-2.11.1.so           libc-2.11.1.so          
malloc_consolidate
1134      1.0067  cc1                      cc1                     
extract_insn

So I don't get that much of RA by itself.  Tracking that malloc ineffeciency
might be low hanging fruit.


  parent reply	other threads:[~2010-12-13  1:07 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 [this message]
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
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-VTYnPubC9c@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).