public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belyshev at lubercy dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18687] New: [4.0 Regression] ~50% compile time regression Date: Sat, 27 Nov 2004 04:30:00 -0000 [thread overview] Message-ID: <20041127043006.18687.belyshev@lubercy.com> (raw) These two files taken from linux kernel (hashes.c) and zlib (infcodes.c) hashes.c: 3.4.4 4.0.0 delta -O0 0.045 0.049 9% -O1 0.067 0.144 115% -O2 0.108 0.177 64% infcodes.c: 3.4.4 4.0.0 delta -O0 0.080 0.086 7% -O1 0.120 0.223 86% -O2 0.196 0.295 51% -- Summary: [4.0 Regression] ~50% compile time regression Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: compile-time-hog Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: belyshev at lubercy dot com CC: gcc-bugs at gcc dot gnu dot org BugsThisDependsOn: 15678 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18687
next reply other threads:[~2004-11-27 4:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-27 4:30 belyshev at lubercy dot com [this message] 2004-11-27 4:31 ` [Bug tree-optimization/18687] " belyshev at lubercy dot com 2004-11-27 4:32 ` belyshev at lubercy dot com 2004-11-27 4:42 ` pinskia at gcc dot gnu dot org 2004-11-27 15:47 ` pinskia at gcc dot gnu dot org 2004-11-27 18:44 ` belyshev at lubercy dot com 2004-11-30 13:09 ` pinskia at gcc dot gnu dot org 2004-11-30 13:11 ` pinskia at gcc dot gnu dot org 2004-11-30 14:32 ` pinskia at gcc dot gnu dot org 2004-11-30 14:57 ` pinskia at gcc dot gnu dot org 2004-11-30 15:17 ` pinskia at gcc dot gnu dot org 2004-12-02 14:06 ` pinskia at gcc dot gnu dot org 2004-12-02 15:27 ` pinskia at gcc dot gnu dot org 2004-12-03 0:24 ` belyshev at lubercy 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=20041127043006.18687.belyshev@lubercy.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).