public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: eckart@icd.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/5882: g++ 2.95.2 craches with fatal signal 11 compiling very large function
Date: Sun, 15 Sep 2002 11:48:00 -0000	[thread overview]
Message-ID: <20020915184855.13707.qmail@sources.redhat.com> (raw)

Synopsis: g++ 2.95.2 craches with fatal signal 11 compiling very large function

State-Changed-From-To: open->feedback
State-Changed-By: nathan
State-Changed-When: Sun Sep 15 11:48:54 2002
State-Changed-Why:
    how much memory do you have? you have a 30,000 line main
    function. BTW, I've found that if you can make your
    machine generated code more table driven, you'll have more luc k.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5882


             reply	other threads:[~2002-09-15 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-15 11:48 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-28  0:26 neroden
2002-09-16  0:16 Jörg Eckart
2002-03-08  4:46 eckart

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=20020915184855.13707.qmail@sources.redhat.com \
    --to=nathan@gcc.gnu.org \
    --cc=eckart@icd.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).