public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david at doublewise dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53650] [4.7/4.8 Regression] large array causes huge memory use Date: Wed, 13 Jun 2012 18:45:00 -0000 [thread overview] Message-ID: <bug-53650-4-7ABYZExNo1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53650-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53650 David Stone <david at doublewise dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david at doublewise dot net --- Comment #2 from David Stone <david at doublewise dot net> 2012-06-13 18:44:18 UTC --- Turns out that contrary to my previous report, optimizations don't actually solve the memory use problem, they just slow it down significantly. Several hours into compilation, memory use was at ~2 GiB and still growing (very slowly). It seems that maybe it uses just as much memory, it just takes much, much longer to get there.
next prev parent reply other threads:[~2012-06-13 18:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-12 23:38 [Bug c++/53650] New: " david at doublewise dot net 2012-06-13 4:59 ` [Bug c++/53650] " hjl.tools at gmail dot com 2012-06-13 18:45 ` david at doublewise dot net [this message] 2012-06-14 6:19 ` [Bug c++/53650] [4.7/4.8 Regression] " jason at gcc dot gnu.org 2012-06-14 8:38 ` rguenth at gcc dot gnu.org 2012-06-17 19:55 ` david at doublewise dot net 2012-06-25 15:59 ` jason at gcc dot gnu.org 2012-09-06 14:48 ` rguenth at gcc dot gnu.org 2012-09-20 10:18 ` jakub at gcc dot gnu.org 2013-01-03 16:52 ` jason at gcc dot gnu.org 2013-01-03 16:54 ` [Bug c++/53650] [4.7 " jason at gcc dot gnu.org 2013-01-22 16:29 ` jason at gcc dot gnu.org 2013-01-22 16:34 ` jason at gcc dot gnu.org 2013-01-22 21:07 ` pluto at agmk dot net 2013-01-23 2:48 ` jason 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-53650-4-7ABYZExNo1@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: 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).