public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/10063] [3.4 Regression] stdio_filebuf broken
@ 2003-05-23  9:11 paolo@gcc.gnu.org
  0 siblings, 0 replies; 6+ messages in thread
From: paolo@gcc.gnu.org @ 2003-05-23  9:11 UTC (permalink / raw)
  To: gcc-bugs

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10063


paolo@gcc.gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|paolo@gcc.gnu.org           |bkoz@gcc.gnu.org
             Status|ASSIGNED                    |NEW


------- Additional Comments From paolo@gcc.gnu.org  2003-05-23 08:59 -------
Benjamin, I'm tentatively assigning this to you as the guy currently working on
those issues.

Personally, I don't know what should we really do in order to be able to
intermix flawlessly the current stdio_filebuf - which, at variance with the old
situation ends up always issuing direct non blocking I/O syscalls, i.e., read,
write, lseek and so on - with stdio. Perhaps we should just hit the bullet and
declare that this is now possible only with stdio_sync_filebuf?

What do you think?

Paolo.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2003-12-10 18:41 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20030313193600.10063.peturr02@ru.is>
2003-07-01  9:49 ` [Bug libstdc++/10063] [3.4 Regression] stdio_filebuf broken peturr02 at ru dot is
2003-08-23  1:30 ` dhazeghi at yahoo dot com
2003-12-05  3:24 ` pinskia at gcc dot gnu dot org
2003-12-10 17:37 ` cvs-commit at gcc dot gnu dot org
2003-12-10 18:41 ` pinskia at gcc dot gnu dot org
2003-05-23  9:11 paolo@gcc.gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).