public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Pétur Runólfsson" <peturr02@ru.is> To: paolo@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: libstdc++/9169: filebuf output fails if codecvt<>::out returns noconv Date: Sun, 16 Feb 2003 17:46:00 -0000 [thread overview] Message-ID: <20030216174600.31700.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/9169; it has been noted by GNATS. From: =?iso-8859-1?Q?P=E9tur_Run=F3lfsson?= <peturr02@ru.is> To: <paolo@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <ncm@cantrip.org>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: RE: libstdc++/9169: filebuf output fails if codecvt<>::out returns noconv Date: Sun, 16 Feb 2003 17:40:23 -0000 > Humm. This behavior started when we implemented the=20 > resolution of DR19, upon your ;) libstdc++/9168! Not so, both bugs are in gcc-3.2.1. Petur
next reply other threads:[~2003-02-16 17:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-16 17:46 Pétur Runólfsson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-17 21:56 Paolo Carlini 2003-02-17 20:15 paolo 2003-02-16 19:26 Paolo Carlini 2003-02-16 16:36 Paolo Carlini 2003-02-16 16:10 paolo 2003-01-04 10:26 peturr02
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=20030216174600.31700.qmail@sources.redhat.com \ --to=peturr02@ru.is \ --cc=gcc-prs@gcc.gnu.org \ --cc=paolo@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).