Date:	Mon, 3 Feb 1997 18:13:59 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	"r. v. paasen" <R DOT L DOT F DOT v DOT Paasen AT stud DOT tue DOT nl>
cc:	djgpp AT delorie DOT com
Subject:	Re: gcc problem
In-Reply-To:	<32F4FFCB.6D80@stud.tue.nl>
Message-ID:	<Pine.SUN.3.91.970203180844.27257D-100000@is>
MIME-Version:	1.0

On Sun, 2 Feb 1997, r. v. paasen wrote:

> 1)   When optimizing with -O3, gcc doesn't respond with some files. The
> files are not extremely large. gcc works fine with files of 900 lines.
> With some files, (300 lines) gcc locks up. 300 lines is less than 900, so gcc
> should definitely not run out of memory compiling 300 lines, if it can
> compile 900 lines. What could be the problem?

This is a wrong assumption.  The amount of memory used up by GCC is not
proportional to the source file size, especially when it optimizes. 
That's because the optimizer needs to perform some flow analysis of the 
program, and the amount of memory required for this depends on the 
program structure, not its size.

Please try the solutions described in section 6.3 of the DJGPP FAQ list 
(v2/faq210b.zip from the same place you get DJGPP), and if they won't 
help, post the source file that causes GCC to hang.

- Raw text -