From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28854 invoked by alias); 24 Aug 2002 20:56:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28835 invoked by uid 71); 24 Aug 2002 20:56:01 -0000 Resent-Date: 24 Aug 2002 20:56:01 -0000 Resent-Message-ID: <20020824205601.28834.qmail@sources.redhat.com> Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer) Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Resent-Reply-To: gcc-gnats@gcc.gnu.org, jlquinn@optonline.net Received: (qmail 24217 invoked by uid 61); 24 Aug 2002 20:51:05 -0000 Message-Id: <20020824205105.24216.qmail@sources.redhat.com> Date: Sat, 24 Aug 2002 18:06:00 -0000 From: jlquinn@optonline.net Reply-To: jlquinn@optonline.net To: gcc-gnats@gcc.gnu.org X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31) Subject: optimization/7713: Performance regression from gcc 2.95.3 X-SW-Source: 2002-08/txt/msg00525.txt.bz2 List-Id: >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: