public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jlquinn@optonline.net To: gcc-gnats@gcc.gnu.org Subject: optimization/7713: Performance regression from gcc 2.95.3 Date: Sat, 24 Aug 2002 18:06:00 -0000 [thread overview] Message-ID: <20020824205105.24216.qmail@sources.redhat.com> (raw) >Number: 7713 >Category: optimization >Synopsis: Performance regression from gcc 2.95.3 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: pessimizes-code >Submitter-Id: net >Arrival-Date: Sat Aug 24 13:56:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: jlquinn@optonline.net >Release: gcc-3.2 >Organization: >Environment: powerpc-unknown-linux-gnu glibc 2.2.5 binutils 2.12.90.0.9 Debian Woody 240MHz 604e 1MB cache >Description: Running C benchmark found here: http://www.cwi.nl/~tromp/c4/fhour.html I was looking at runtimes from different compilers, gcc 2.95.4 (.3 plus Debian patches) and released gcc 3.2 included. If I compile with gcc 2.95 -O2, I get the following performance numbers from the program: 207.2 Kpos/sec, 208.7 Kpos/sec gcc 2.95 -O2 -mcpu=604e 214.5 Kpos/sec, 215.2 Kpos/sec gcc 3.2 -O2 197.9 201.2 gcc 3.2 -O2 -mcpu=604e 199.4 201.1 198.7 I've played with some other settings and have been unable to get 3.2 to match or beat 2.95's performance here. Note, using the 3.3 mainline of about July 23, I got about equivalent runtime performance on the same benchmark. >How-To-Repeat: Build with the same compile-time flags. Run as: c4 < input >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-24 20:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-24 18:06 jlquinn [this message] 2003-03-22 18:00 bangerth 2003-03-24 15:46 bangerth
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=20020824205105.24216.qmail@sources.redhat.com \ --to=jlquinn@optonline.net \ --cc=gcc-gnats@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).