public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/14078] Manipulators are slow
Date: Wed, 11 Feb 2004 12:09:00 -0000 [thread overview]
Message-ID: <20040211120855.21149.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040209093043.14078.peturr02@ru.is>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-02-11 12:08 -------
Subject: Bug 14078
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: paolo@gcc.gnu.org 2004-02-11 12:08:24
Modified files:
libstdc++-v3 : ChangeLog
libstdc++-v3/include/std: std_istream.h std_ostream.h
Added files:
libstdc++-v3/testsuite/performance/27_io:
fmtflags_manipulators.cc
Log message:
2004-02-10 Paolo Carlini <pcarlini@suse.de>
Petur Runolfsson <peturr02@ru.is>
PR libstdc++/14078
* include/std/std_istream.h (operator>>(__istream_type& (*)
(__istream_type&)), operator>>(__ios_type& (*)(__ios_type&)),
operator>>(ios_base& (*)(ios_base&))): Declare inline.
* include/std/std_ostream.h (operator<<(__ostream_type& (*)
(__ostream_type&)), operator<<(__ios_type& (*)(__ios_type&)),
operator<<(ios_base& (*) (ios_base&))): Likewise.
* testsuite/performance/27_io/fmtflags_manipulators.cc: New.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/ChangeLog.diff?cvsroot=gcc&r1=1.2325&r2=1.2326
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/include/std/std_istream.h.diff?cvsroot=gcc&r1=1.15&r2=1.16
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/include/std/std_ostream.h.diff?cvsroot=gcc&r1=1.14&r2=1.15
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/testsuite/performance/27_io/fmtflags_manipulators.cc.diff?cvsroot=gcc&r1=NONE&r2=1.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14078
next prev parent reply other threads:[~2004-02-11 12:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 9:30 [Bug libstdc++/14078] New: " peturr02 at ru dot is
2004-02-09 9:44 ` [Bug libstdc++/14078] " peturr02 at ru dot is
2004-02-09 9:55 ` falk dot hueffner at student dot uni-tuebingen dot de
2004-02-09 10:41 ` pcarlini at suse dot de
2004-02-09 17:09 ` peturr02 at ru dot is
2004-02-10 14:16 ` pcarlini at suse dot de
2004-02-10 14:22 ` giovannibajo at libero dot it
2004-02-10 15:22 ` peturr02 at ru dot is
2004-02-10 15:35 ` pcarlini at suse dot de
2004-02-10 15:55 ` peturr02 at ru dot is
2004-02-10 16:09 ` pcarlini at suse dot de
2004-02-10 17:03 ` gdr at integrable-solutions dot net
2004-02-10 17:08 ` pcarlini at suse dot de
2004-02-11 12:09 ` cvs-commit at gcc dot gnu dot org [this message]
2004-02-11 15:02 ` cvs-commit at gcc dot gnu dot org
2004-02-11 15:05 ` pcarlini at suse dot de
2004-07-30 19:21 ` cvs-commit at gcc dot gnu dot org
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=20040211120855.21149.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).