Date: Tue, 12 May 1992 15:42:36 +0200
From: Ove Ewerlid <ewerlid AT pinus DOT slu DOT se>
To: duperval AT ere DOT umontreal DOT ca (Duperval Laurent)
To: djgpp AT sun DOT soe DOT clarkson DOT edu (DJGPP Mailing List)
Subject: Gcc stops before compiling
References: <9205120258 DOT AA26918 AT eole DOT ERE DOT UMontreal DOT CA>
Mailer: VM 5.32 (beta) for GNU Emacs 18.57.6
Status: O



> I have this really weird problem which I'd like to try to fix.  I'm compiling
> some code which is fairly short.  But gcc compiles and then stops without
> creating a .o file.  gcc -E works fine so I know the problem isn't with cc.
							       ^^^^^	
How do you know this ...
The frontend in gcc called "gcc.exe" invokes cpp.exe, cc1.exe and as.exe when it produces an
object file.  The problem can still be in cc1.exe.

> The default behaviour of gcc is to compile and link and produce a
> file called a.out, deleting the .o file. To get a .o file use
> 
> gcc -c foo.c 

If it isn't this, that is the problem, you may want to test the "-Q" flag.
With this flag cc1.exe will report each function (to stdout) that it starts to
compile.  It will also give a summary of the wall clock time in each pass.
This may help you to pinpoint the problem.