public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/7076] [3.3/3.4 regression] iostreams very slow compared with earlier gcc versions
Date: Tue, 13 Jan 2004 04:16:00 -0000 [thread overview]
Message-ID: <20040113041651.7186.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020619054600.7076.morten@wtf.dk>
------- Additional Comments From ian at airs dot com 2004-01-13 04:16 -------
I just tried this test case on gcc 2.95.3 and current mainline. I find that
current mainline is slower than 2.95.3, but it is less than twice as slow (0.42
seconds for 2.95.3, 0.76 seconds for mainline). At this point I don't think
this counts as a significant gcc 3.4 regression.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7076
next prev parent reply other threads:[~2004-01-13 4:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020619054600.7076.morten@wtf.dk>
2003-06-01 20:10 ` [Bug libstdc++/7076] " pme@gcc.gnu.org
2003-06-01 20:11 ` pme@gcc.gnu.org
2003-06-09 18:21 ` [Bug libstdc++/7076] [3.3/3.4 regression] " giovannibajo@libero.it
2003-06-24 20:43 ` bkoz at gcc dot gnu dot org
2003-08-03 19:25 ` pinskia at physics dot uc dot edu
2003-10-16 9:44 ` mmitchel at gcc dot gnu dot org
2003-12-21 18:11 ` gdr at gcc dot gnu dot org
2003-12-23 19:30 ` pinskia at gcc dot gnu dot org
2004-01-11 0:43 ` pinskia at gcc dot gnu dot org
2004-01-13 4:16 ` ian at airs dot com [this message]
2004-01-13 16:10 ` bkoz at gcc dot gnu dot org
2004-01-13 19:46 ` paolo at gcc dot gnu dot org
2004-01-13 20:02 ` gdr at integrable-solutions dot net
2004-01-13 20:17 ` paolo at gcc dot gnu dot org
2004-01-13 20:27 ` gdr at integrable-solutions dot net
2004-01-13 20:37 ` paolo at gcc dot gnu dot org
2004-01-13 20:49 ` paolo at gcc dot gnu dot org
2004-01-13 21:28 ` gdr at integrable-solutions dot net
2004-01-13 23:17 ` bkoz at redhat dot com
2004-01-13 23:21 ` joe dot buck at synopsys dot com
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=20040113041651.7186.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).