This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: crash with too many stack variables
- To: SVN Kalyan <skalyan at synopsys dot COM>
- Subject: Re: crash with too many stack variables
- From: Daniel Berlin <dan at cgsoftware dot com>
- Date: Fri, 31 Aug 2001 17:15:26 -0400
- Cc: gcc-bugs at gcc dot gnu dot org
- References: <3B8FFA76.F58C70ED@synopsys.com>
SVN Kalyan <skalyan@synopsys.COM> writes:
> Hi,
>
> When you have too many local variables in a function (> 3000), with
> -O1 for optimization, gcc crash after a long-time; takes around 40
> minutes before it crashes.
Errr, need a test case.
>
> We made all these locals 'static' and and compiled -O0 option, it
> went through. But, -O failed even with this change. Does anybody have
> an idea as to what might be the problem. We are ready to bump any limits
> or any minor fixing to get this thing going.
Once again, need a testcase.
>
> A general question, gcc chokes when functions are too large or have
> too many statements or too deep a nesting level. Is there a place where
> I can find out all the currently applicable limits and is there a way to
> fix them ourselves.
Submit testcases, and there is a better chance at someone being able
to help figure out what's going wrong.
>
> Thanks
>
--
"I took a baby shower.
"-Steven Wright