Date:	Wed, 8 Jul 1998 13:17:18 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Aleksey Kondratyev <akondra AT mv DOT ru>
cc:	djgpp AT delorie DOT com
Subject:	Re: internal g++ compiler error
In-Reply-To:	<6nv69h$pmi$1@simtel.ru>
Message-ID:	<Pine.SUN.3.91.980708131333.5810C-100000@is>
MIME-Version:	1.0

On Wed, 8 Jul 1998, Aleksey Kondratyev wrote:

> Could anybody explain what the internal compiler
> error 75 means processing C++ module. I moved
> to 2.8.1 version (from 2.8.0) and it complains on
> one my C++ module telling the above error (2.8.0
> compiled it perfectly). The module is rather large
> and  I failed to locate the dangerouse code in my
> source.

Use the -Q switch, and g++ should print the name of every function it 
compiles.  This way, you will know inside which function does it barf, 
and could further narrow down the problematic fragment using the
#if 0...#endif paradigm.

Btw, this is all described in the DJGPP FAQ list (section 6.3).

> BTW, pgcc (downloaded yesterday from www.goof.com)
> generates the same error.

Which means you should probably report it to the GCC/EGCS maintainers, 
after you find out which part of code causes it.

- Raw text -