public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/37991]  New: excessive memory consumption - possible hang
Date: Sat, 01 Nov 2008 21:29:00 -0000	[thread overview]
Message-ID: <bug-37991-9596@http.gcc.gnu.org/bugzilla/> (raw)

I just tried to compile the attached C++ source code with both
gcc 4.3.1 and gcc 4.4.0 snapshot 20081031.

gcc 431 took less than one second and consumed a trivial amount
of virtual memory.

gcc 440 snapshot 20081031 took over 90 seconds on an idle machine,
and consumed over 11 Gig of virtual memory before running out of
virtual memory.

In my opinion, 11 Gig of memory is an excessive amount of memory to use.
I suspect the compiler is looping without doing any productive work.

Preprocessed source code attached. Flag -O2 required.


-- 
           Summary: excessive memory consumption - possible hang
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dcb314 at hotmail dot com
  GCC host triplet: suse-linux-x86_64


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37991


             reply	other threads:[~2008-11-01 21:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-01 21:29 dcb314 at hotmail dot com [this message]
2008-11-01 21:30 ` [Bug c++/37991] " dcb314 at hotmail dot com
2008-11-02 10:43 ` [Bug tree-optimization/37991] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-11-02 11:00 ` rguenth at gcc dot gnu dot org
2008-11-02 11:28 ` rguenth at gcc dot gnu dot org
2008-11-02 12:05 ` rguenth at gcc dot gnu dot org
2008-11-02 13:37 ` rguenth at gcc dot gnu dot org
2008-11-02 13:37 ` rguenth at gcc dot gnu dot org
2008-11-02 20:55 ` dberlin at dberlin 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=bug-37991-9596@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).