public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bitti@cs.tut.fi
To: gcc-gnats@gcc.gnu.org
Cc: bitti@cs.tut.fi
Subject: c++/2741: GCC bug: compiler takes almost a minute and 350 MB to compile this
Date: Fri, 04 May 2001 13:16:00 -0000	[thread overview]
Message-ID: <200105042015.f44KFua01892@mustikkakukko.cs.tut.fi> (raw)

>Number:         2741
>Category:       c++
>Synopsis:       compiler takes almost a minute and 350 MB to compile struct
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 04 13:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Matti Rintala
>Release:        3.0 20010428 (prerelease)
>Organization:
Tampere University of Technology
>Environment:
System: Linux mustikkakukko.cs.tut.fi 2.4.3 #12 Mon Apr 23 11:08:50 EEST 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc/configure --host=athlon-pc-linux-gnu --prefix=/usr/local/gcc-3-test --enable-shared --enable-threads --with-cpu=athlon --enable-cpp --enable-languages=c++
>Description:
	The compiler (g++) takes almost a minute and uses 350 MB of memory
        while compiling the following program with only the -c flag:

struct X
{
  int a[5000000];
};

        I tried this with two PCs running Linux. The CodeSourcery's online
        test compilates reported "virtual memory exhausted".

>How-To-Repeat:
        Compile the struct definition above with "g++ -c"
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2001-05-04 13:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200105042015.f44KFua01892@mustikkakukko.cs.tut.fi \
    --to=bitti@cs.tut.fi \
    --cc=gcc-gnats@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).