public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mario-baumann at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53226] New: memory consumption for heavy template instantiations increased massively
Date: Fri, 04 May 2012 07:10:00 -0000 [thread overview]
Message-ID: <bug-53226-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53226
Bug #: 53226
Summary: memory consumption for heavy template instantiations
increased massively
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: mario-baumann@web.de
Hi All,
i noticed that memory consumption for heavy template instantiations increased
massively between gcc revision 187034 and 187074. If a compile my current
project (unfortunately closed source) i got e.g.
> top
top - 08:58:08 up 1 day, 30 min, 11 users, load average: 28.83, 19.13, 13.36
Mem: 24607424k total, 24464568k used, 142856k free, 752k buffers
Swap: 52436120k total, 6650108k used, 45786012k free, 4174408k cached
PID PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14825 20 0 24.5g 18g 496 R 89.1 79.0 3:48.75 cc1plus
Mario.
---
> uname -a
Linux ahsoka.intec.dom 2.6.32-220.13.1.el6.x86_64 #1 SMP Thu Mar 29 11:46:40
EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
> rpm -qa "glibc*" | grep -e 'glibc-[0-9]' | sort -u
glibc-2.12-1.47.el6_2.9.i686
glibc-2.12-1.47.el6_2.9.x86_64
> g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/app2/gcc/4.8.0-20120503-svn187074/x86_64/libexec/gcc/x86_64-unknown-linux-gnu/4.8.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ./configure --prefix=/app2/gcc/4.8.0-20120503-svn187074/x86_64
--enable-languages=c,c++,fortran --disable-nls
--with-gmp=/app2/gcc/4.8.0-20120503-svn187074/x86_64/aux
--with-mpfr=/app2/gcc/4.8.0-20120503-svn187074/x86_64/aux
--with-mpc=/app2/gcc/4.8.0-20120503-svn187074/x86_64/aux
--with-ppl=/app2/gcc/4.8.0-20120503-svn187074/x86_64/aux
--with-cloog=/app2/gcc/4.8.0-20120503-svn187074/x86_64/aux
Thread model: posix
gcc version 4.8.0 20120503 (experimental) (GCC)
> ld -v
GNU ld (GNU Binutils) 2.22.52.20120503
next reply other threads:[~2012-05-04 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 7:10 mario-baumann at web dot de [this message]
2012-05-04 7:22 ` [Bug c++/53226] " manu at gcc dot gnu.org
2012-05-04 9:01 ` rguenth at gcc dot gnu.org
2012-05-04 9:33 ` mario-baumann at web dot de
2012-05-04 19:52 ` mario-baumann at web dot de
2012-05-08 7:15 ` mario-baumann at web dot de
2012-05-08 7:55 ` mario-baumann at web dot de
2012-05-08 10:16 ` rguenth at gcc dot gnu.org
2012-05-08 12:04 ` matz at gcc dot gnu.org
2012-05-08 12:10 ` jakub at gcc dot gnu.org
2012-05-08 12:13 ` matz at gcc dot gnu.org
2012-05-08 12:13 ` rguenth at gcc dot gnu.org
2012-05-08 13:20 ` rguenth at gcc dot gnu.org
2012-05-08 13:25 ` matz at gcc dot gnu.org
2012-05-08 16:36 ` [Bug tree-optimization/53226] [4.8 Regression] Endless loop in forwprop jakub at gcc dot gnu.org
2012-05-09 12:22 ` jakub at gcc dot gnu.org
2012-05-09 12:33 ` jakub 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=bug-53226-4@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).