public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: dita@cs.technion.ac.il, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/9111: gcc 3.0.4 slow run time reults Date: Tue, 31 Dec 2002 04:52:00 -0000 [thread overview] Message-ID: <20021231125236.9927.qmail@sources.redhat.com> (raw) Synopsis: gcc 3.0.4 slow run time reults State-Changed-From-To: open->feedback State-Changed-By: paolo State-Changed-When: Tue Dec 31 04:52:35 2002 State-Changed-Why: This is by and large a known issue (see libstdc++/7076 and some recent postings on the list). However, for the time being, could you possibly try: 1- Upgrading to gcc3.2.1 2- Putting std::ios::sync_with_stdio(false); at the beginning of your test. On i686-pc-linux-gnu, I'm getting the followin run times for HelloWorld2.cc (-O2 > /dev/null): 3.0.4: 8.190u 4.440s 0:12.74 99.1% 3.0.4 + sync(false): 2.360u 1.240s 0:03.63 99.1% 3.2.1: 4.760u 0.410s 0:05.21 99.2% 3.2.1 + sync(false): 1.320u 0.370s 0:01.70 99.4% Thanks, Paolo. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9111
next reply other threads:[~2002-12-31 12:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-31 4:52 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-31 4:06 dita
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=20021231125236.9927.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=dita@cs.technion.ac.il \ --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: 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).