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, nobody@gcc.gnu.org, peturr02@ru.is Subject: Re: libstdc++/9701: filebuf::sputc, in_avail incorrect Date: Sun, 23 Feb 2003 17:17:00 -0000 [thread overview] Message-ID: <20030223171751.21815.qmail@sources.redhat.com> (raw) Synopsis: filebuf::sputc, in_avail incorrect State-Changed-From-To: open->analyzed State-Changed-By: paolo State-Changed-When: Sun Feb 23 17:17:50 2003 State-Changed-Why: The first part (about sputc) is fixed by the work for 9404 (in fact is not true anymore that pptr == epptr, since the latter points to the end of the buffer, 8192 chars wide, by default). The second part stands. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9701
next reply other threads:[~2003-02-23 17:17 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-23 17:17 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-18 8:09 paolo 2003-02-14 7:56 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=20030223171751.21815.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=nobody@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).