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 c++/29433] using boost::MPL requires lots of memory Date: Tue, 28 Nov 2006 12:38:00 -0000 [thread overview] Message-ID: <20061128123802.26127.qmail@sourceware.org> (raw) In-Reply-To: <bug-29433-12712@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from rguenth at gcc dot gnu dot org 2006-11-28 12:38 ------- Most of the memory used is spent in the string pool: String pool entries 68980 identifiers 68980 (100.00%) slots 131072 bytes 1012M (10M overhead) table size 1024k coll/search 0.7816 ins/search 0.2876 avg. entry 15394.37 bytes (+/- 68924.74) longest entry 2130575 if you add -g to the compilation, dwarf2out.c happily xstrdup()s most of them a few times and memory consumption goes up to 3.9GB. All the stringpool handling and it's usage by classtype_mangled_name is not very well optimized for such large strings (after all, we know the string length there for example). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29433
next prev parent reply other threads:[~2006-11-28 12:38 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-11 19:05 [Bug c++/29433] New: Internal error while compiling code using boost::MPL grayyoga at gmail dot com 2006-10-11 19:10 ` [Bug c++/29433] " grayyoga at gmail dot com 2006-10-11 19:13 ` grayyoga at gmail dot com 2006-10-11 19:14 ` grayyoga at gmail dot com 2006-10-11 19:36 ` pinskia at gcc dot gnu dot org 2006-10-11 21:56 ` [Bug c++/29433] using boost::MPL requires lots of memory rguenth at gcc dot gnu dot org 2006-10-12 8:20 ` rguenth at gcc dot gnu dot org 2006-10-12 9:52 ` grayyoga at gmail dot com 2006-10-12 13:09 ` rguenth at gcc dot gnu dot org 2006-10-12 16:50 ` grayyoga at gmail dot com 2006-10-12 19:56 ` grayyoga at gmail dot com 2006-10-13 10:58 ` rguenth at gcc dot gnu dot org 2006-10-13 11:05 ` rguenth at gcc dot gnu dot org 2006-10-13 12:16 ` grayyoga at gmail dot com 2006-10-13 12:19 ` rguenth at gcc dot gnu dot org 2006-10-13 12:21 ` grayyoga at gmail dot com 2006-10-13 13:19 ` rguenth at gcc dot gnu dot org 2006-11-22 12:39 ` rguenth at gcc dot gnu dot org 2006-11-28 12:38 ` rguenth at gcc dot gnu dot org [this message] 2006-11-28 16:21 ` patchapp at dberlin dot org 2006-11-30 16:15 ` patchapp at dberlin dot org 2006-12-01 16:38 ` rguenth at gcc dot gnu dot org 2006-12-01 16:38 ` rguenth at gcc dot gnu dot org 2007-02-23 14:21 ` rguenth at gcc dot gnu dot org 2007-06-12 11:30 ` rguenth 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=20061128123802.26127.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: linkBe 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).