🚀 go-pugleaf

This is a bug in gcc 2.2.2, gcc 2.2.1 I believe did not have this
problem.  The next release of gcc should not have it either.

> To: bug-gcc@prep.ai.mit.edu
> Date: Thu, 27 Aug 92 15:26:01 +0100
> Message-Id: <3379.714925561@xtel.co.uk>
> From: Alan Shepherd <a.shepherd@xtel.co.uk>

> Quite a while ago I sent a message reporting undefined assembler
> symbols such as "L495" appearing in .o files.  I didn't receive any
> acknowledgement or see any answer or patch in the newsgroup, although
> I did see someone else reporting the same thing.

> output from gcc -v

> Reading specs from /usr/local/lib/gcc-lib/sparc-sun-sunos4.1.1/2.2.2/specs
> gcc version 2.2.2

> The problem seems to arise when using the -g flag and can be evidenced
> by compiling the lates version of libg++.a.  I can't remember which
> particular file other than it is one of the ones in iostream, but I
> did report it before.