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, paolo@gcc.gnu.org, peturr02@ru.is Subject: Re: libstdc++/9875: filebuf doesn't handle codecvt::encoding() > 1 Date: Sat, 01 Mar 2003 10:44:00 -0000 [thread overview] Message-ID: <20030301104416.22007.qmail@sources.redhat.com> (raw) Synopsis: filebuf doesn't handle codecvt::encoding() > 1 State-Changed-From-To: closed->analyzed State-Changed-By: paolo State-Changed-When: Sat Mar 1 10:44:16 2003 State-Changed-Why: Mistakenly closed ;) Anyway, I have a patch for it, quite simple indeed, which already passes all your tests. The underflow bits are still missing, however. Are you willing to provide some tests for it too? Thanks, Paolo. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9875
next reply other threads:[~2003-03-01 10:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-01 10:44 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-03 18:46 Pétur Runólfsson 2003-03-03 11:06 Paolo Carlini 2003-03-03 10:56 Pétur Runólfsson 2003-02-28 22:55 paolo 2003-02-27 10:36 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=20030301104416.22007.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=peturr02@ru.is \ /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).