public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, michael.pronath@gmx.de, nobody@gcc.gnu.org Subject: Re: libstdc++/8636: global ostringstreams lose their data Date: Thu, 28 Nov 2002 08:06:00 -0000 [thread overview] Message-ID: <20021120124836.31101.qmail@sources.redhat.com> (raw) Synopsis: global ostringstreams lose their data State-Changed-From-To: open->feedback State-Changed-By: paolo State-Changed-When: Wed Nov 20 04:48:35 2002 State-Changed-Why: Cannot reproduce on x86-linux (glibc2.3.1) with gcc-3.2.1 and current 3.3 exp. Could possibly install gcc-2.3.1 and see if the problem it's still present for you? Thanks, Paolo. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8636
next reply other threads:[~2002-11-20 12:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-28 8:06 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-30 20:56 Michael Pronath 2002-11-30 20:01 Paolo Carlini 2002-11-25 14:42 michael.pronath
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021120124836.31101.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=michael.pronath@gmx.de \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).