🚀 go-pugleaf

In an ealier posting: 
>/usr/src/GNU/gcc-2.4.2/xgcc -B/usr/src/GNU/gcc-2.4.2/ `cat fflags` -c  -DIN_GCC
>  -g -O -I. -I.. -I/usr/src/GNU/gcc-2.4.2 -I/usr/src/GNU/gcc-2.4.2/config /usr/s
>rc/GNU/gcc-2.4.2/objc/sendmsg.c
>xgcc: Internal compiler error: program cc1 got fatal signal 4

Followed by: 
In article <9306030251.AA07581@mole.gnu.ai.mit.edu> rms@gnu.ai.mit.edu (Richard Stallman) writes:

>   The place to start is by reading the Bugs chapter of the GCC manual.
>   Please follow the instructions there.

May I suggest one neat idea?

Instead of making the compiler just say " Internal compiler error:
program cc1 got fatal signal 4", why don't we incorporate a few more
sentences so that the output would look like the following? This
should save RMS and others much time in trying to educate the C
programmers who try to report bugs, and yet fail to follow the proper
procedures.

Suggested message:

xgcc: Internal compiler error: program cc1 got fatal signal 4
      Please follow the instructions in the "Bugs" chapter of the GCC
      manual and report the remaining problem by a proper bug report.
      The format and contents of a proper bug report and the e-mail
      address is found in the  aforementioned manual chapter.

Chiaki Ishikawa