Re: Too many if statements crash cc1

[Mike Stump <mrs at windriver dot com>]

> To: gcc@gcc.gnu.org
> Date: Tue, 06 Jun 2000 17:02:36 -0700
> From: " J S  Hammond" <jshammond@my-Deja.com>

First, wrong list, bugs in gcc should be reported to the bugs address,
not the gcc list.

> I am building a cross compiler for a custom processor using WinNT as
> the host machine.  This is for compiling only, we use our own tools
> for assembling and linking.  The gcc version is 2.95.

Ok.

> If I put more than 757 if statments in a single function cc1 crashes
> while compiling and returns a STATUS_ACCESS_VIOLATION as well as a
> core file.  It takes half as many if-else statements to cause this.
> I have tried these programs (and one with many more if statements)
> on the native gcc compiler and those compiled with no errors.
> Spreading the if statements out over multiple functions makes the
> compiler happy.

> Is there something that I can change in the cross compiler building
> that will fix this?

The answer to your question is yes.  But this would be perfectly
useless, to you I realize.

First, grab cygwin (see the FAQ) and give it a try.  If it works,
consider using it.  Also, you didn't state what compiler you used to
compile the cc1 that faults.  If you used a microsoft compiler, let me
say, I've seen problems with it that look kinda like this one, and I
solved them by recompiling with a cygwin.

Second, if that proves for naught, there is a process called
debugging, that can help you.  But, alas, that process is beyond the
scope of this list, and can be long and fairly involved.
Unfortunately I don't have a good pointer to a description of the
process.  That does seem a flaw, sorry.