Re: Internal compiler error (cygwin)

["Zack Weinberg" <zackw at stanford dot edu>]

On Thu, Mar 29, 2001 at 05:46:53PM +0200, Thomas Henlich wrote:
> I got an error message about 'Internal compiler error' using gcc 2.95.3-2
> on cygwin (1.1.8, Windows NT-4.0 i386)
> A preprocessed file *.i is not generated with "gcc -v -save-temps ..."
> so I'm unsure how to post a bug report.
...
> cpp0.exe: Internal compiler error in `collect_expansion', 
  ^^^^^^^^^
>	at /cygnus/netrel/src/gcc-2.95.3-2/gcc/cccp.c:6111
> Please submit a full bug report.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

This is a bug in the preprocessor, so naturally you do not get a
preprocessed file.

You should take your source code and shrink it down, until you have
one short source file which triggers the bug.  Then post it.  The
preprocessor spat out a bunch of errors before aborting -

> In file included from spvw.d:21:
> lispbibl.d:9545: warning: preprocessing directive not recognized within macro arg
> lispbibl.d:9545: warning: preprocessing directive not recognized within macro arg
> In file included from spvw.d:714:
> spvw_garcol.d:1786: unterminated macro call
> spvw_garcol.d:2553: unterminated macro call
> spvw_garcol.d:2554: unbalanced `#endif'

- the bug will probably go away if you fix all those errors.  (That
does not mean it is not a bug; only that you should be able to work
around it.)

There isn't an abort on line 6111 of cccp.c in my source tree, which
makes me wonder if your copy of the program has been modified from the
official 2.95.3.  Can any Cygwin hackers comment please?

I wonder why it says 'in file included from spvw.d' when the source
file is spvw.c...  That suggests memory corruption to me.

zw