https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67968
--- Comment #5 from Dominik Vogt <vogt at linux dot vnet.ibm.com> --- Unfortunately I cannot reproduce this yet. Please try to identify the "faulty" source file and strip it down to the minimum. 1. Find out in which file the ICE occurs. 1.a Recompile GCC with debug information, e.g. with $ make CXXFLAGS="-g3 -O2" CFLAGS="$CXXFLAGS" GOCFLAGS="$CXXFLAGS" -j 7 all 1.b Use the commands from comment 4 to run the gccgo-5 command line manually. This whould still generate an ICE. 1.c Run the go1 command in gdb. Just add the option -wrapper gdb,--args at the end of the gccgo-5 command line. Then type "run" in the debugger. Gdb should automatically stop when the ICE occurs. From there, check the available information in the current stack frame and the higher ones and see if you can find the name of the current source file or the function name and possibly the line number in some structure. I know nothing about the Go frontent, so unfortunately you have to figure that out on your own. 2. Strip down the sources as much as possible. Now that you know which file generates the ICE, try to strip down the api module as much as possible. The first step is to get rid of all the other files in the package. Next, remove the imports in the faulty file and finally strip down the file as much as possible to make a standalone test case.
