🚀 go-pugleaf

Compiler version: gcc-2.2.2

1) The protoize program seems to have a bug in its parser: identifiers
starting with "const" are not interpreted correctly. For example
"constfoobar" is transformed into "obar". As far as I can tell,
constfoobar is a perfectly valid ANSI C or C++ identifier (const
itself is not of course).

2) I have been unable to make the stage 2 g++ compiler on a Sony
NeWS1200. In fact, the config file news.h does not contain a line
for this system (MC68030 with MC68882), but the impossibility of
compilation remains even when this line is added. Symptom: the stage 2
compilation and installation works fine, and when a not completely
trivial program is compiled, we get the message "Internal compiler
error 10". The stage 1 compiler (compiled using cc) partially works
(it crashes on some libg++ tests).

3) In the file math-68881.h:

	a) Function pow, there are 2 asm statements

              __asm ("fmove%.d %#0x7fffffffffffffff,%0"         /* quiet NaN */

For some machines this gives an assmbler warning: quad to d_float
conversion loses significance. This disappears if fmove%.d is
replaced by fmove%.x. Is this a correct modification?

	b) Function hypot (line 291), I always get the warning:
float or double assigned to integer data type. I cannot understand where
an integer data type is present. This occurs whenever a program is
compiled and linked, for example during the construction of the
libg++ library.

	Sincerely yours,

H. Cohen

cohen@alioth.greco-prog.fr
cohen@geocub.greco-prog.fr