public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "coyote at coyotegulch dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/17050] New: Performance pessimisation as compared to GCC 3.4 Date: Mon, 16 Aug 2004 15:29:00 -0000 [thread overview] Message-ID: <20040816152907.17050.coyote@coyotegulch.com> (raw) The benchmark program attached hereto is representative of a regression I've seen in a couple of large programs. Compiled with GCC 3.4 and prior, this program runs in about 12 seconds on my test systems; using GCC 3.5, it takes more than 30 seconds to run. -- Summary: Performance pessimisation as compared to GCC 3.4 Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: coyote at coyotegulch dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: x86_64-unknown-linux GCC host triplet: x86_64-unknown-linux GCC target triplet: x86_64-unknown-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17050
next reply other threads:[~2004-08-16 15:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-16 15:29 coyote at coyotegulch dot com [this message] 2004-08-16 15:35 ` [Bug tree-optimization/17050] " coyote at coyotegulch dot com 2004-08-16 16:52 ` [Bug tree-optimization/17050] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-09-01 6:27 ` law at gcc dot gnu dot org 2004-09-03 22:09 ` steven at gcc dot gnu dot org 2004-09-03 22:19 ` steven at gcc dot gnu dot org 2004-09-08 17:50 ` pinskia at gcc dot gnu dot org 2004-11-26 22:33 ` [Bug tree-optimization/17050] [4.0 " dberlin at gcc dot gnu dot org 2004-11-26 22:48 ` pcarlini at suse dot de 2004-11-26 22:51 ` giovannibajo at libero dot it
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=20040816152907.17050.coyote@coyotegulch.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).