From mboxrd@z Thu Jan  1 00:00:00 1970
From: pme@gcc.gnu.org
To: pme@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2071
Date: Tue, 05 Jun 2001 13:16:00 -0000
Message-id: <20010605201601.4437.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-06/msg00140.html
List-Id: <gcc-prs.sourceware.org>

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

From: pme@gcc.gnu.org
To: Theodore.Papadopoulo@sophia.inria.fr, gcc-gnats@gcc.gnu.org,
  mark@codesourcery.com, nobody@gcc.gnu.org, pme@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/2071
Date: 5 Jun 2001 20:10:38 -0000

 Old Synopsis: cin bug on solaris 2.6
 New Synopsis: seeking on standard input
 
 Responsible-Changed-From-To: unassigned->pme
 Responsible-Changed-By: pme
 Responsible-Changed-When: Tue Jun  5 13:10:37 2001
 Responsible-Changed-Why:
     
     I am consolidating PRs 2345, 3014, and 1620, all of which
     were high-priority duplicates of this one (which was
     marked high priority before I think it got corrupted and
     restored).
 State-Changed-From-To: open->analyzed
 State-Changed-By: pme
 State-Changed-When: Tue Jun  5 13:10:37 2001
 State-Changed-Why:
     
     Still a problem using the 20010604 prerelease, tested with
     the code in the original 2071 bug report and Loren's tests
     posted in the most thoughtful analysis at
     
         http://gcc.gnu.org/ml/libstdc++/2001-05/msg00041.html
     
     I'm about to start a bootstrap on solaris 8 with his patch
     from the thread starting with
     
         http://gcc.gnu.org/ml/libstdc++/2001-05/msg00052.html
     
     Nobody ever responded to his request for commentary or
     stepped up with an alternative solution (unless I seriously
     missed a thread).  It means using YAoM (Yet Another
     os_defines.h Macro), but if it solves the problem for 3.0,
     then I vote we use it.
     
     This bug tends to kill any use of cin under solaris, so
     we need to find something...
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2071&database=gcc