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] memory consumption for heavy template instantiations increased massively
Date: Tue, 08 May 2012 07:55:00 -0000 [thread overview]
Message-ID: <bug-53226-4-okwSh2bQJE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53226-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53226
--- Comment #6 from Mario Baumann <mario-baumann at web dot de> 2012-05-08 07:54:22 UTC ---
Created attachment 27341
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27341
c++ source
Added testcase (needs include files from boost ->
http://sourceforge.net/projects/boost/files/boost/1.49.0/ -> just extract any
tarball).
> /app2/gcc/4.8.0-20120507-svn187053/x86_64/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/app2/gcc/4.8.0-20120507-svn187053/x86_64/bin/g++
COLLECT_LTO_WRAPPER=/app2/gcc/4.8.0-20120507-svn187053/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-20120507-svn187053/x86_64
--enable-languages=c,c++,fortran --disable-nls
--with-gmp=/app2/gcc/4.8.0-20120507-svn187053/x86_64/aux
--with-mpfr=/app2/gcc/4.8.0-20120507-svn187053/x86_64/aux
--with-mpc=/app2/gcc/4.8.0-20120507-svn187053/x86_64/aux
--with-ppl=/app2/gcc/4.8.0-20120507-svn187053/x86_64/aux
--with-cloog=/app2/gcc/4.8.0-20120507-svn187053/x86_64/aux
Thread model: posix
gcc version 4.8.0 20120502 (experimental) (GCC)
bad: g++ -Iboost_1_49_0/ -c foo.cpp -O2 -m64
bad: g++ -Iboost_1_49_0/ -c foo.cpp -O1 -m64
ok: g++ -Iboost_1_49_0/ -c foo.cpp -O0 -m64
ok: g++ -Iboost_1_49_0/ -c foo.cpp -O2 -m32
Mario.
next prev parent reply other threads:[~2012-05-08 7:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 7:10 [Bug c++/53226] New: " mario-baumann at web dot de
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 [this message]
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-okwSh2bQJE@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).