This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/5882: g++ 2.95.2 craches with fatal signal 11 compiling very large function
- From: Jörg Eckart <eckart at icd dot de>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 16 Sep 2002 07:16:05 -0000
- Subject: Re: c++/5882: g++ 2.95.2 craches with fatal signal 11 compiling very large function
- Reply-to: Jörg Eckart <eckart at icd dot de>
The following reply was made to PR c++/5882; it has been noted by GNATS.
From: =?ISO-8859-1?Q?J=F6rg?= Eckart <eckart@icd.de>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/5882: g++ 2.95.2 craches with fatal signal 11 compiling very large function
Date: Mon, 16 Sep 2002 09:13:26 +0200
Hello,
nathan@gcc.gnu.org wrote:
> 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
>
>
we are working on a Sun-Blade-1000 with 4GB ram+20GB swap space. So far
as I remember, memory consumption of the compiler process was around
only 100MB. Meanwhile we modified our code generator essentially, so
that the function are generated much more smaller now. Nevertheless
should large functions be compiled properly or at least be refused with
an appropriate error message.
Best regards,
Jörg Eckart