public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/9580: basic_filebuf<> with custom traits_type fails to link
Date: Thu, 13 Feb 2003 21:36:00 -0000	[thread overview]
Message-ID: <20030213213600.18826.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/9580; it has been noted by GNATS.

From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Paolo Carlini <pcarlini@unitus.it>
Cc: gcc-gnats@gcc.gnu.org, peturr02@ru.is, gcc-bugs@gcc.gnu.org
Subject: Re: libstdc++/9580: basic_filebuf<> with custom traits_type fails to link
Date: 13 Feb 2003 22:27:40 +0100

 Paolo Carlini <pcarlini@unitus.it> writes:
 
 | Gabriel Dos Reis wrote:
 | 
 | >This is something we should fix.  However I don't have necessary time
 | >next week to work on it. I'm sorry.
 | >
 | Well, so *I* will fix it ;)
 | 
 | Seriously, the PR is regression from 3.0.x, "due" to this checkin of
 | yours and
 
 Aha, I'm a silly boy :-(
 
 | Benjamin, apparently
 | (the problem is with std::basic_filebuf<char,
 | MyTraits>::_M_underflow_common(bool):
 | 
 | 2002-07-30  Benjamin Kosnik  <bkoz@redhat.com>
 |             Gabriel Dos Reis  <gdr@nerim.net>
 | 
 | ...
 | 
 |     * include/std/std_fstream.h: Declare _M_underflow_common
 |     specializations.
 |     * src/fstream.cc: New. Add _M_underflow_common specializations.
 |     * include/bits/fstream.tcc (filebuf::close): Use traits_type.
 |     (filebuf::_M_underflow_common(bool)): Remove generic version, as
 |     sys_ungetc and custom int_types don't get along.
 | 
 | ...
 | 
 | Can you please help me a bit understanding these Changelog entries?
 
 If I recall correctly, this change was made because of some
 differences in the way a narrow character stream based on
 char_traits<char> behaves and the way the general Traits may behave.
 At that point, I seem to recall that the goal was to have a general
 implementation  of that function plus the special case.  I'll have to
 go back and check my logs, unless Benjamin has a better recollection. 
 
 -- Gaby


             reply	other threads:[~2003-02-13 21:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 21:36 Gabriel Dos Reis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-17 20:10 paolo
2003-02-13 21:46 Paolo Carlini
2003-02-13 21:26 Paolo Carlini
2003-02-13 21:21 paolo
2003-02-13 21:16 Gabriel Dos Reis
2003-02-13 21:06 Paolo Carlini
2003-02-13 20:56 Gabriel Dos Reis
2003-02-13 20:11 paolo
2003-02-05 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=20030213213600.18826.qmail@sources.redhat.com \
    --to=gdr@integrable-solutions.net \
    --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: link
Be 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).