Re: libstdc++/2816

Re: libstdc++/2816

[pme]

The following reply was made to PR libstdc++/2816; it has been noted by GNATS.

From: pme@gcc.gnu.org
To: aubin.mahe@wanadoo.fr, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/2816
Date: 5 Jun 2001 21:39:47 -0000

 Synopsis: bad STL implementation on vector / iostream
 
 State-Changed-From-To: analyzed->closed
 State-Changed-By: pme
 State-Changed-When: Tue Jun  5 14:39:47 2001
 State-Changed-Why:
     This PR is for -v2, not -v3.  Also, multiple bug
     reports all at once are cumbersome, as noted.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2816&database=gcc

Re: libstdc++/2816

[bkoz]

The following reply was made to PR libstdc++/2816; it has been noted by GNATS.

From: bkoz@gcc.gnu.org
To: aubin.mahe@wanadoo.fr, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/2816
Date: 25 May 2001 05:11:28 -0000

 Synopsis: bad STL implementation on vector / iostream
 
 State-Changed-From-To: open->analyzed
 State-Changed-By: bkoz
 State-Changed-When: Thu May 24 22:11:28 2001
 State-Changed-Why:
     You'll need to break this down into three separate bug reports, one for each of vector, map, and set.
     
     Please.
     
     This is kind of hard to deal with in its current form.
     
     
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2816&database=gcc