public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmartin at cliftonlabs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19614] New: Excessive memory consumption
Date: Mon, 24 Jan 2005 20:58:00 -0000 [thread overview]
Message-ID: <20050124205844.19614.dmartin@cliftonlabs.com> (raw)
Processing the attached file causes g++ to consume about 1.4G of virtual memory
on x86_64. The same file caused problems on x86 in an earlier release - see bug
#15320. Also, on my project's mailing list I have seen the implication that
similar issues exist on powerpc:
http://www.cliftonlabs.com/savant/list-archives/savant-users/2004-December/000013.html
Please let me know if there is anything I can do to help sort this out.
Here is the output of g++ -v:
Reading specs from /usr/lib/gcc/x86_64-linux/3.4.4/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4
--enable-shared --with-system-zlib --enable-nls --without-included-gettext
--program-suffix=-3.4 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt
--enable-clocale=gnu --enable-libstdcxx-debug --enable-java-gc=boehm
--enable-java-awt=gtk --disable-werror x86_64-linux
Thread model: posix
gcc version 3.4.4 20041218 (prerelease) (Debian 3.4.3-7)
--
Summary: Excessive memory consumption
Product: gcc
Version: 3.4.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dmartin at cliftonlabs dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19614
next reply other threads:[~2005-01-24 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 20:58 dmartin at cliftonlabs dot com [this message]
2005-01-24 21:00 ` [Bug c++/19614] " dmartin at cliftonlabs dot com
2005-01-24 21:07 ` pinskia at gcc dot gnu dot org
2005-01-25 0:07 ` pinskia at gcc dot gnu dot org
2005-01-25 4:26 ` [Bug c++/19614] Excessive memory consumption with a class with large (200) virtual (pure?) function and derived classes pinskia at gcc dot gnu dot org
2005-01-25 6:45 ` pinskia at gcc dot gnu dot org
2005-01-27 13:07 ` dmartin at cliftonlabs dot com
2005-01-27 13:24 ` pinskia at gcc dot gnu dot org
2005-01-27 13:43 ` dmartin at cliftonlabs dot com
2005-04-28 0:53 ` pinskia at gcc dot gnu dot org
2005-07-25 1:43 ` pinskia at gcc dot gnu dot org
2005-08-09 5:05 ` phython at gcc dot gnu dot org
2005-09-18 23:57 ` pinskia 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=20050124205844.19614.dmartin@cliftonlabs.com \
--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).