🚀 go-pugleaf

This is a problem with gcc 2.2.2, gcc 2.2.1 does not have this
problem.  The next release of gcc should not have this problem.

> To: bug-gcc@prep.ai.mit.edu
> Date: Tue, 21 Jul 92 10:37:54 +0100
> Message-Id: <10444.711711474@xtel.co.uk>
> From: Alan Shepherd <a.shepherd@xtel.co.uk>

> The current version of gcc appears to have a bug in that assembler
> symbols (e.g. LBB01) appear in some .o files when compiled with the -g
> flag.

> gcc -v:

> gas@spitfire% gcc -v
> Reading specs from /usr/local/lib/gcc-lib/sparc-sun-sunos4.1.1/2.2.2/specs
> gcc version 2.2.2

> A suitable file to reproduce this problem is
> libg++-2.2/libg++/iostream/sbufvform.o. 


> Without -g, the problem does not appear.  

> I have mentioned this on the gnu.g++.lib.bug newsgroup when I
> mistakenly thought that the problem was with libg++ itself.  Sorry !