Bizzare segmentation violation

[Tony Bryant]

I've a piece of C++ code here that causes an "Internal compiler error: 
segmentation violation" when complied with yesterday's mainline GCC. 

Strange thing is that 

"sh-elf-g++ -c mycode.cc"

doesn't work,

but

"sh-elf-g++ -E mycode.cc -o tmp/mycode.cc"
"sh-elf-g++ -c tmp/mycode.cc -o mycode.o"

works fine! It runs fine too.

This makes it pointless to submit a bug report. 

It looks like something happening in the preprocessing is corrupting 
something vital down the line. 

This program makes heavy use of STL, so there is very heavy use of nested 
includes. Am I hitting some sort of implicit limit in the preprocessor? 
Nesting depth or numbers of symbols or something?

Any guesses, places to start looking, or even wild theories would be much 
appreciated...

Regards,
Tony Bryant.