🚀 go-pugleaf

I reported a gcc 1.30 preprocessor bug a couple of weeks ago
wherein a space in erroneously inserted into the middle of a
'&=' operator.  Yesterday, I found another example, with
space being dropped into the middle of a variable name.  This one
is half the size of the previous, and likely exhibits the same
bug.  Rather than burden the mailing list with a large uuencoded
file, I have made both files accessible via anonymous ftp to
cs.utah.edu:

ls -l ~ftp/pub/cccp*
-rw-r--r--  1 beebe       21444 Dec  1 17:50 /usr/spool/ftp/pub/cccp-bug-2.c.Z
-rw-r--r--  1 beebe       49957 Nov 21 18:18 /usr/spool/ftp/pub/cccp-bug.c.Z

I installed gcc 1.31 today and verified from the diffs between
1.30 and 1.31 cccp.c, and by rerunning the test, that the space
insertion bug remains.

Also, in the 1.31 distribution, several xm-*.h files still have
#include "config-*.h" statements; I applied sed on all of them to
change "config-" to "xm-":

grep '"config-" xm-*.h.ORIG
xm-3b1.h.ORIG:#include "config-m68k.h"
xm-gnx.h.ORIG:#include "config-ns32k.h"
xm-hp9k320.h.ORIG:#include "config-m68k.h"
xm-sunos4.h.ORIG:#include "config-sparc.h" 
xm-sunos4.h.ORIG:#include "config-m68k.h"
xm-vaxv.h.ORIG:#include "config-vax.h"
-------