public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@gcc.gnu.org, corsepiu@faw.uni-ulm.de, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/3983: basic_istringstream<unsigned xxx> causes segfault
Date: Tue, 02 Apr 2002 18:36:00 -0000	[thread overview]
Message-ID: <20020403023618.28403.qmail@sources.redhat.com> (raw)

Synopsis: basic_istringstream<unsigned xxx> causes segfault

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Tue Apr  2 18:36:17 2002
Responsible-Changed-Why:
    Mine.
State-Changed-From-To: analyzed->feedback
State-Changed-By: bkoz
State-Changed-When: Tue Apr  2 18:36:17 2002
State-Changed-Why:
    Fixed with:
    
    2002-04-02  Benjamin Kosnik  <bkoz@redhat.com>
    	
    	libstdc++/5268
    	* src/ios.cc: (ios_base::Init::_S_ios_destroy): Remove flush calls.
    	* testsuite/27_io/ios_init.cc (tests04): Add test.
    
    	libstdc++/3983
    	* include/bits/basic_ios.h (basic_ios::_M_get_fctype_ios): Remove.
    	(basic_ios::_M_ios_fctype): Consistently name to _M_fctype.
    	* include/bits/basic_ios.tcc: Same. Remove outdated comments.
    	* include/bits/istream.tcc: Use _M_fctype, make consistent with
    	ostream.
    	* testsuite/27_io/ios_init.cc (tests03): Add test.
    	

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3983


             reply	other threads:[~2002-04-03  2:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 18:36 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-03 12:36 bkoz
2002-03-11 11:12 pme
2001-08-10  6:16 corsepiu

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=20020403023618.28403.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=corsepiu@faw.uni-ulm.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --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: 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).