public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlo at alinoe dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/13351] [3.3 Regression] BIG slowdown in generated code (compared to 3.2) Date: Mon, 08 Dec 2003 15:33:00 -0000 [thread overview] Message-ID: <20031208153339.10991.qmail@sources.redhat.com> (raw) In-Reply-To: <20031208072839.13351.cline@parashift.com> ------- Additional Comments From carlo at alinoe dot com 2003-12-08 15:33 ------- Subject: Re: [3.3 Regression] 10x slower generated code (GCC 3.3 compared with GCC 3.2) Not the case on i686-pc-linux-gnu (athlon 900 Mhz) g++ 3.2 : 0.2116 ns/per g++ 3.2.1 : 0.32025 ns/per g++ 3.2.2 : 0.31925 ns/per g++ 3.2.3 : 0.3185 ns/per g++ 3.3 : doesn't compile g++ 3.3.1 : 0.102 ns/per g++ 3.3.2 : 0.1034 ns/per mainline: 0.0818462 ns/per So I'd say - it became 3 times FASTER, instead. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13351
next prev parent reply other threads:[~2003-12-08 15:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-08 7:28 [Bug c++/13351] New: 10x slower execution speed GCC 3.3 (compared with GCC 3.2) cline at parashift dot com 2003-12-08 7:43 ` [Bug c++/13351] [3.3 Regression] " pinskia at gcc dot gnu dot org 2003-12-08 10:38 ` [Bug c++/13351] [3.3 Regression] 10x slower generated code (GCC 3.3 compared " cline at parashift dot com 2003-12-08 10:42 ` cline at parashift dot com 2003-12-08 11:16 ` [Bug libstdc++/13351] " pinskia at gcc dot gnu dot org 2003-12-08 12:10 ` [Bug libstdc++/13351] [3.3 Regression] Generated code is noticeable slower (compared to 3.2) giovannibajo at libero dot it 2003-12-08 13:00 ` cline at parashift dot com 2003-12-08 13:09 ` [Bug libstdc++/13351] [3.3 Regression] BIG slowdown in generated code " giovannibajo at libero dot it 2003-12-08 13:31 ` falk at debian dot org 2003-12-08 15:33 ` carlo at alinoe dot com [this message] 2003-12-08 17:38 ` gdr at integrable-solutions dot net 2003-12-09 21:30 ` bkoz at gcc dot gnu dot org 2003-12-13 22:02 ` cline at parashift dot com 2003-12-23 10:01 ` pinskia 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=20031208153339.10991.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: 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).