public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/19614] Excessive memory consumption with a class with large (200) virtual (pure?) function and derived classes Date: Fri, 21 Sep 2007 02:29:00 -0000 [thread overview] Message-ID: <20070921022905.30463.qmail@sourceware.org> (raw) In-Reply-To: <bug-19614-8484@http.gcc.gnu.org/bugzilla/> ------- Comment #14 from bangerth at dealii dot org 2007-09-21 02:29 ------- We are now again on par with gcc 3.3 in terms of memory use (3.3 uses 298 MB whereas 4.1 uses 280MB). This is a factor of 2 or 3 less than what we used to use. We are also about a factor of 2 faster than in the 3.3 and 3.4 times. I think we can close this one now. W. -- bangerth at dealii dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bangerth at dealii dot org Status|NEW |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19614
next prev parent reply other threads:[~2007-09-21 2:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19614-8484@http.gcc.gnu.org/bugzilla/> 2007-09-20 14:25 ` rguenth at gcc dot gnu dot org 2007-09-21 2:29 ` bangerth at dealii dot org [this message] 2005-01-24 20:58 [Bug c++/19614] New: Excessive memory consumption dmartin at cliftonlabs dot com 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=20070921022905.30463.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).