This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: PR2345
- To: libstdc++ at gcc dot gnu dot org
- Subject: Re: PR2345
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- Date: Tue, 22 May 2001 04:03:20 -0500 (CDT)
- Cc: rittle at latour dot rsch dot comm dot mot dot com
- Organization: Networks and Infrastructure Lab (IL02/2240), Motorola Labs
- References: <20010518175944D.mitchell@codesourcery.com>
In article <20010520002639.A749@disaster.jaj.com> you write:
>On Fri, May 18, 2001 at 05:59:44PM -0700, Mark Mitchell wrote:
>> Since this PR is marked as high, we need to fix it. It looks like
>> Phil got started, but got stuck. Would one of you take a look at it?
This bug (PR2345) is identical to 2071 and a few other reports (1620
and random libstdc++ mailing list reports over the past few months).
[...]
> There were a couple other PR's dealing with blocking when reading from
> stdio via C++ streams, 2071 comes to mind. At least one patch has been
> posted (for 2071, but might help), but I can't test it until "hello world"
> works, and I've no clue why it's failing. Maybe Brad's patch of earlier
> today might help. I'll give that a try.
My patch for 2071 also fixes 2345 on i386-unknown-freebsd4.2.
See this proposed patch (so far no feedback):
http://gcc.gnu.org/ml/libstdc++/2001-05/msg00052.html
See this commentary on the portable solution space:
http://gcc.gnu.org/ml/libstdc++/2001-05/msg00050.html
See this analysis of portability problem:
http://gcc.gnu.org/ml/libstdc++/2001-05/msg00041.html
--
Loren J. Rittle
Senior Staff Software Engineer, Distributed Object Technology Lab
Networks and Infrastructure Research Lab (IL02/2240), Motorola Labs
rittle@rsch.comm.mot.com, KeyID: 2048/ADCE34A5, FDC0292446937F2A240BC07D42763672